Windows 10 1709 (Fall Creators Update) failed update

Anonymous
2017-10-18T21:43:39+00:00

I checked for updates on my HP x2 612 laptop today and it started downloading the Fall Creators Update - Windows 10 1709.

It got through the download and finished the install and prompted me to reboot the computer.

The computer rebooted and is now stuck in an endless loop with the message "Windows could not complete the installation.  To install Windows on this computer, restart the installation" and an OK button.  Clicking the OK button just restarts the computer and brings back the message.

I am unable to boot into Safe Mode as I get a message that Windows cannot install in Safe Mode with an OK button that brings up the original message after a reboot.

The 2 year old laptop came with Windows 7 and was updated to Windows 10 1703.  The laptop does not have a restore partition.  There is no data on the laptop that needs to be recovered.  Clean machine without anti-virus software ever except Windows Defender and no HP software. 

Windows does not load, so it is limited what programs I can run.

I am able to get to a cmd prompt from the Troubleshooting area of the BIOS, but do not know how to roll back to the previous Windows build from there or if it is even possible.

Unless somebody has a workaround to either install the upgrade or roll it back to the previous build it looks as if this Windows update has bricked my laptop.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2017-11-01T14:16:59+00:00

In my case there was insufficient space in the system partition and I had to delete language folders from the system partition to free up space.

I used the following fix from Microsoft (https://support.microsoft.com/en-us/help/3086249/-we-couldn-t-update-system-reserved-partition-error-installing-windows)

The description is for fixing issues with installing Windows 10 on a Windows 7 or 8 computer but the worked for me installing the Fall Creators Update on a Windows 10 computer.

NOTE:

In my case I have a GPT partition.  The fix has you mount the system partition and give it a drive letter of "Y" and then open File Explorer to delete the language folders. 

I was unable to find the "Y" drive in File Explorer so I had to navigate to each language folder through the command prompt, delete the files in the language folder (del *.*) and then delete the folder (rd <folder name>)

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

73 additional answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2018-02-03T01:07:36+00:00

    Another place I thought to look was the registry...  A...  there they were.. all three files I had deleted had links in the registry...

    So ..  trying once again....

    oem files deleted

    Registry updated..

    Temp update files purged

    Trouble shoot fix...

    Use the "https://www.microsoft.com/en-gb/software-download/windows10" site

    fingers crossed.....

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-02T23:29:45+00:00

    Wow. How hard is this?! This is just not good enough.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-02T19:34:33+00:00

    Given you mention of looking on the total system...  I looked for oem43.*  and found a security file.. I deleted it.. and the other oem files...  I looked for them in files..  and packages...  Cleaned up all the update areas....

    and rebooted...

    and then started the update again....

    MUCH TO MY SURPRISE....  the compatdata file for the new update....  it still had the blocking oem files...  I wonder were it is still finding references to them???

    Oh well... I will let it continue to see if it will ignore them if they are not around...

    the journey continues...  sigh...

    Was this answer helpful?

    0 comments No comments