Issues Updating from 1703 to 1709

Hi AO,

         The problem here is could be and possibly, I am an engineer by training with a background in material testing.  There are no IFs or MAYBEs in a specification for an engineering part.

          I get the feeling that Microsoft plonk in a piece of code someone thinks should work and testing limited to a clean install enviorment.  I know it is not possible to test each upgrade against every possible variance in software installation but when it comes to drivers I would at least expect a specific report relating to that failure, or any other failure.  But that is not the case, no request for the logs or driver list.   Do you realise that I spent 9 hours playing with changes of the WiFi Card and rerunning the update simply on a maybe!  THIS IS BUMBLING ABOUT LOOKING FOR A POSSIBLE CAUSE AND NOT AN ANALITICAL APPROACH and that is what is wrong, you never get to prove the problem and make allowance for next time.

          I note the size of the install has been reduced slightly, what I also do not understand is the fact that used once UPDATE files are retained without a requested need (ie. for another PC).    MY CLEAN INSTALL ON A NEWLY MADE PARTITION PRODUCED FOR SPACE FROM OTHER PARTITIONS RESULTED IN 46GB OF OLD WINDOWS.

Was the problem I had just one of space for 1709 to store OLD WINDOWS  because I only had 50GB spare and the accumulation of OLD and the space for 1709 exceeded that?

If that is the case, this is the reason why we recommended you to post this issue in the Feedback Hub. By posting this issue there, our Support Engineers can see your issue and examine it to determine if there is an error in the update. If you've already posted the issue in the Feedback Hub, it is best to share your submission here so that other community member can see it.

Please take note that the disk space  is not the cause of the issue. If the issue is with the disk space, Windows Update will produce a different error code and error message. The partitions in your hard disk is also not the problem because you're able to install Windows 10 in a new partition. The issue that you're encountering with the update is already in the code of Windows 10 and the only one that can decipher the codes are the developers. This is why it is best to replace the whole system files of Windows 10 to resolve the issue.

Best regards.

Was the problem I had just one of space for 1709 to store OLD WINDOWS  because I only had 50GB spare and the accumulation of OLD and the space for 1709 exceeded that?

In that case we may be offered the option of adding a second drive during the update  OR  being told how much space would be required.   In that latter case, we are also allowed to use Disk Cleanup, including deleting Windows.old if necessary in order to proceed.  These procedures actually work.

BTW a novel suggestion I saw recently is to download and archive the file that the media creation tool generates.  Supposedly this option would have allowed a user to try doing an ISO Upgrade Repair from 1607 to 1703, assuming that was a better choice than doing one for the current 1709.  Is your OS Windows Home or Windows Pro?

C.f.

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-update-1709-boot-problems/155b318b-52fc-4d04-b445-f544056e7309?page=2#LastReply

FYI

Robert Aldwinckle

Hi RA,

          I Run Win 10 Pro on a 3 year old Dell with an i7 laptop processor

          I don't believe that Updates are that cleverly controlled.  When I updated to 1703 it failed, no reason just went belly up.  Having tried and failed a second time I looked back through the update history and found a failed update which I reinstalled and then 1703 installed without problem, this was many months ago when 1703 was first offered.  At the end of many attempts by UPDATE to install 1709 there was a progressive list of 1709 needs a restart messages in Update History.

          An Update / Upgrade install of 1709  on 1703 existing may well notify a too small partition but if a clean install on a newly formed partition manages to generate *48GB of OLD (where did it come from), on a new partition which now takes 33GB of space and includes Office 2010 Pro Plus and another 10 items of Software (No Data Files) how big can the OLD and Rollback Folders become from about *90GB Windows 1703 with about 90 software programs that I installed, not counting Ms items like Silverlight and Visual Studio etc ?

* REMEMBER:- No data files as everything normally found in USER has been redirected to another partition

The 40 GB file that you're seeing after clean installing Windows 10 in a new partition are the old Windows 10 files. Because of the unsuccessful attempts to install the version 1709 update, those old files were being accumulated and was saved in the new partition where the new copy of Windows 10 is installed. You can remove these old files by running disk clean up.

Thanks.