Fall creators update: PC doesn't restart

TTSVids105 · 19 Oct 2017

...and a dialog box pops up saying "Windows 10 installation has failed". Upgrading via the MCT on a 1703 PC.

Caledon Ken · 19 Oct 2017

Hi TTSVids105

Is your PC dead right now or did it fall back?

If dead, from the power on boot and as soon as you see spinning dots hold power button until it shuts off. Repeat a second time.

On third time the Advance Start up Options should be available. Follow through to Go back to previous build.

Boot to Advanced Startup Options in Windows 10

If you are dead in the water I know you have a backup of your data, right?

If not create this disk and get your data off.

Windows 10 Recovery Tools - Bootable Rescue Disk

Once data is off and you are sure you have everything my recommendation is clean install. I would download fresh Media creation tool and download media to ensure it is not corrupt.

Clean Install Windows 10

In future have an Image before trying this so you can restore.

Backup and Restore with Macrium Reflect

Ken

TTSVids105 · 19 Oct 2017

It falls back, not even rebooting to the next part of setup

Update: And it happened again! Does win+x -> restart work and let's setup continue? But if it doesn't it looks like I'm going to be stuck on 1703 while everyone else is on shiny new 1709. For now going to hold off until I find a solution

Caledon Ken · 19 Oct 2017

That is a smart idea.

If you want to experiment further use Macrium Reflect to image current system.

Backup and Restore with Macrium Reflect

I would also use the Windows software Create Recovery Drive. This should let you install current version from a clean install.

Back up your data off machine and you could try clean install. Yes more work.

If all else fails do a restore from Macrium.

Obviously there is some risk in upgrading. You would be surprised at how many people don't have FCU. Letting MS get it ready for your machine is a safe call.

Ken

TTSVids105 · 19 Oct 2017

Just wondering... Does the win+x -> restart thing I mentioned earlier work? P.S When I installed 1607 and 1703, it restarted, letting setup continue. Maybe a specific issue pertaining to 1709's installer.

Caledon Ken · 19 Oct 2017

Not sure what you mean, WIN+x gives you a menu. On that menu you can restart but this is not the same as restart during an upgrade where code has been installed.

With the update, achieve by executing setup from USB, please disconnect all non essential devices, ensure Secure boot and fast boot are disabled in BIOS. (Have your data backed up)

TTSVids105 · 20 Oct 2017

This could help solve my predicament. I honestly forgot about the Rufus (*Update Forgot about the MCTs ability to create Setup USB sticks) method and launching setup there. Thumbs up to you! (doesn't appear in mobile view)

TTSVids105 · 20 Oct 2017

Guess WHAT? My PC didn't restart again. Was expecting setup to go through, and it didn't. Same dialog, same problem. I tried the USB thing you said, but it still happens. I try to check the Setup logs, but event log keeps stopping. After running Get-WindowsIpdateLog in PowerShell and looking at the log file generated, it seems that the setup tried to "send the shutdown notification" to my PC, and was unable to "persist operation handle value" with an error code of 0x80070013, and exited with the dialog, and the error code 0x240001.

Having Avast installed, if it causes installation problems.

Caledon Ken · 20 Oct 2017

I've seen threads where people believe AV's are the issue. Did you make BIOS settings.

If you feel comfortable around the PC and it appears you do I think I would do a clean install. Yes more work but a great base to move forward on.

Here is an informative thread.

https://docs.microsoft.com/en-gb/win...dy_UpgradeTips

Ken

TTSVids105 · 20 Oct 2017

Caledon Ken said:

With the update, achieve by executing setup from USB, please disconnect all non essential devices, ensure Secure boot and fast boot are disabled in BIOS. (Have your data backed up)

Do you mean "boot from USB"?

Caledon Ken said:

Did you make BIOS settings.

Will try tomorrow. If it doesn't work I'll call it a day

Caledon Ken said:

Here is an informative thread.

https://docs.microsoft.com/en-gb/win...dy_UpgradeTips

I went through the document and searched the setupact and err logs. Nothing on the error codes I mentioned above appear in both logs. Just wondering... Does anyone else have this issue?

Update: Reading the logs again produced two error codes:

Code:

0x80004005

as the error code, and

Code:

0x50015

as the result.

The error code seems to be Win32, which I cannot seem to lay my finger on which specific error it is. The result code I CAN, though: it happened during phase 5, and there was an error creating a file.

And it seems like it's a CRC error keeping me from updating. Oh well, time for a new hard disk it seems.