Issues Updating from 1703 to 1709

Great news. When it continued to be hopeless, you managed finally to smash right through the immovable object. So, put on some band-aids, if necessary, & best make a Windows system image backup in duplicate. 😊.

Good luck, & keep us informed.

Hi All,

          I now have 16299.309 installed.   I disconnected  network locations and deleted all extra AV (Malwarebyte and SuperAnti bla bla), downloaded and ran  wu170509 .diagcab which is the Update Troubleshooter, and I do not know if it differs from the one in the Control Panel, and allowed it to do what it wanted.   I ran SFC & DISM, which did not show and problems, downloaded the "latest" image from Microsoft to run a full Upgrade Install and guess what, even after allowing the inclusion of Updates as part of the initial process I have ended up with the build before the one I am trying to Upgrade.  I wanted 16229.309 and what I got is 16299.125.  There is no information as to what the build is prior to download with the Media Selection Tool so on top of the struggle to get the B Update installed I have probably wasted time yet again on a pointless exercise because of material Microsoft seem to lazy to keep updated.

          Having blown my safety valve over obsolete images I took a few sips of my Hobgoblin and downloaded the KB4088776 Update directly and ran it.  I cannot believe that it has actually installed so I now have build 16299.309 installed!

         As info for PCR,  I did not change the Virtual Memory location or add it to C:\

MANY THANKS TO ALL FOR YOUR ASSISTANCE.

Hi RA,

      Only way I could get a working Login was by F8 and using System Restore to get me back to a working entry.  I needed to rework all the necessary changes and for some reason the Uninstall for both Malwarebytes and SuperAnti etc where not there. this also was the case with a couple of other bits of software I had deleted and needed a reinstall to allow removal.    Windows little failures are driving me nuts.

      The on screen keyboard does not appear on my laptop.

Well, keep us informed as to the end result. You are right, that is all that matters. Maybe show us a DiskPart & BCDEdit when the dust settles. Good luck.

HI PCR, 

   Out of all the permutations I used it is a problem to get straight exactly what the sequence was.  Yes, I installed 1709 on the HDD but in the end I did a Clean Install on the SSD of 1709, there is just too much history to repeat as the between steps.

        1709 was installed on the 0 drive which was the SSD and the original Win 10 1703 (and 1709 from which the clone below originated) in that location moved to the Optical Drive location .  I had cloned 1709 to the SSD but despite modifying the registry it was still recognised as a usb drive for GKW reason, I certainly do not.   To cure this problem I changed the partition size and formatted the drive and installed Win 10 Pro 1709 SAVING NOTHING. 

        The more you dig around this I am sure the more confused you will become as I have enough problem keeping trace of the convolutions:  All that matters is that my current 1709 version on the SSD in the 0 Drive location is a Clean Install to that drive in that location as I have repeatedly stated.