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. Anonymous
    2018-02-01T15:02:18+00:00

    This is how I managed to resolve the problem

    go to c:\windows\panther

    look for latest compatdata xml file

    Open with edge

    Scroll down until you see something like

    <DriverPackages>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem8.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem18.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem17.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem5.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem11.inf"/>

    <DriverPackage HasSignedBinaries="False" BlockMigration="True" Inf="oem15.inf"/>

    <DriverPackage HasSignedBinaries="False" BlockMigration="True" Inf="oem14.inf"/>

    I looked for the blockmigration=True

    found and deleted oem15inf and oem14.inf

    Update then ran without problem

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-04T18:55:28+00:00

    Microsoft needs to WITHDRAW this update, fix it, and re-send it. You just DON'T send out something that crashes or stalls computers, esp when the fix is to "reset" the pc wiping out all software. Seriously? I mean...seriously? There's probably nothing of substance in this "feature" update, anyway.

    This.... a thousand times this.   I was reading the various solutions.... solutions ranging from 5 hour installs to solutions with entirely too many manual tweaks and manual entry to a complete system wipes.  WTH?  In what universe is ANY of this even remotely acceptable. 

    Withdrawing this steaming dung heap that is trying to be pawned off as a update until it is actually functional is the only acceptable solution. 

    An option to reject the update would be appreciated.  

    Failing that, I am kind of OK letting the update repeatedly fail until Microsoft can be bothered to get its act together.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-12-26T14:49:52+00:00

    Andrew -

    My old printer stopped working at a previous Windows update, but I managed to get it working again - for a while.  First thing, try to reinstall your existing printer software, if you kept the original installation disc.  If that doesn't work or the disc is missing, try looking for the relevant software online on the manufacturer's website.  If you can't find the software for your model printer, try installing the other (later) packages available: you might just find one that does work for your printer even though it's for a different model.  I kept my ancient 32bit printer working with my 64bit W10 PC for a while that way. 

    However, with the 1709 update, my PC is insistent that there's no compatible printer software available now, so I've finally had to buy a new one (after 10 years).  I did manage to recycle my old printer to someone using Windows 7; just hope they can still find the ink for it.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-12-26T01:55:22+00:00

    Hello Andrew,

    Just like what David Haz said, it is best that you reply to the thread that you've created to avoid confusion. This will help you get better assistance from our Community.

    Best regards.

    Thank you for the second word of advice to go over to the other thread.  My reason for posting over here is that Microsoft seems to reply to this thread.. but not the other thread I created...

    I will stay over in the other thread because "heaven forbid" that I would cause confusion...

    The Fall Update 1709 seems to be a problem for many..  I hope I will get guidance from Microsoft on how to proceed....

    I am starting to lose faith in Microsoft..  (I have been with Microsoft since MS-Dos....)

    Hope to see you on the other thread..

    Andrew

    Was this answer helpful?

    0 comments No comments