Current Status of Windows 10 October 2018 Update version 1809

midgo said:

No joy.
I disconnected all 7 hard drives and only had the keyboard and mouse and the C: drive on.
I used a USB stick with the windows ISO on it and tried a setup from that.
Same result.
It installs to about 59% then stops and shows the Windows installation failed message.
Attachment 227630
No error codes are show.
I am not sure what to do now???
Any ideas guys...

Before going any further, maybe you should verify the size of your system reserved partition; it should be between 300-450MB. Also, I would verify the integrity of the .iso file by checking the SHA1 value. You will find all the explanations on how to do that in following article:

Here’s What You Can Do if Windows 10 Upgrade Fails:

https://www.groovypost.com/howto/wha...upgrade-fails/

IronZorg89 said:

Before going any further, maybe you should verify the size of your system reserved partition; it should be between 300-450MB. Also, I would verify the integrity of the .iso file by checking the SHA1 value. You will find all the explanations on how to do that in following article:

Here’s What You Can Do if Windows 10 Upgrade Fails:

https://www.groovypost.com/howto/wha...upgrade-fails/

I am in the same boat as midgo. I have tried upgrading to 1809 with both a thumb drive and a DVD that I made with an .iso at a different time than the thumb drive. My reserved partition is 450mb. I have tried every suggestion that I could find on the internet over the last 5 days. I have given up. Mine gets to about 96% then every time the install fails. No reason given. I have a homebuilt AMD PC that was originally Windows 7. All updates up until 1809 have installed without a hitch. I'm just going to wait for the April 2019 update and see if that will work. If not I'll stay on 1803. Life is too short to constantly battle issues with Microsoft.

SetupDiag works! After attending to all the quick fixes recommended by MS, I moved on to the next step SetupDiag to solve all the upgrade failures to 1809. SetupDiag identified a blocking issue. It took a while to figure out a fix for the problem but ultimately the solution was simple. I then used the Update Assistant and 1809 downloaded and installed with no issues and I've had no problems since. And I am just a plodder.

Caledon Ken said:

Did you guys run this exec that zbook posted? Does it reveal anything?

I have the log file of the last failed attempt here if any wizard can interpret the results.
File 2019_03_18_07_23_11_3_006f0018.xml seems to show a couple of false .inf files???

https://www.mediafire.com/file/ib18lb8gl7gmce8/Logs.zip/file

Plodder said:

SetupDiag works! After attending to all the quick fixes recommended by MS, I moved on to the next step SetupDiag to solve all the upgrade failures to 1809. SetupDiag identified a blocking issue. It took a while to figure out a fix for the problem but ultimately the solution was simple. I then used the Update Assistant and 1809 downloaded and installed with no issues and I've had no problems since. And I am just a plodder.

Do you have your logs handy so that I can compare with mine???
What was this blocking issue of which you speak???

midgo said:

I have the log file of the last failed attempt here if any wizard can interpret the results.
File 2019_03_18_07_23_11_3_006f0018.xml seems to show a couple of false .inf files???

https://www.mediafire.com/file/ib18lb8gl7gmce8/Logs.zip/file

The setupdiag results displayed:
SetupDiag was unable to match to any known failure signatures.

Troubleshooting Windows upgrade failures can take a lot of time.
That should be compared to performing a reset save files, custom install, and clean install.

For troubleshooting you can open a new thread using share links from one drive, drop box, or google drive with:
0xC1420121, 0x50014 or 0xC1900108

Code:

0XC1900108
MOSETUP_E_REPORTING
An error has occured and the result value must be consolidated for telemetry purposes.

MSG_INSTALLUI_SWITCH_TO_ERROR_PAGE
phase: SP_EXECUTION_UNINSTALL
operation: SP_EXECUTION_OP_REGISTER_SYNC_PROCESS

An alternative option is Microsoft free support for failed Windows upgrades.

Often the best option for a possibly very time consuming troubleshooting process is to perform one of the earlier options (reset save files, custom install, and clean install) and then reinstall applications and drivers.

ram1220 said:

I am in the same boat as midgo. I have tried upgrading to 1809 with both a thumb drive and a DVD that I made with an .iso at a different time than the thumb drive. My reserved partition is 450mb. I have tried every suggestion that I could find on the internet over the last 5 days. I have given up. Mine gets to about 96% then every time the install fails. No reason given. I have a homebuilt AMD PC that was originally Windows 7. All updates up until 1809 have installed without a hitch. I'm just going to wait for the April 2019 update and see if that will work. If not I'll stay on 1803. Life is too short to constantly battle issues with Microsoft.

It is a choice you can only make for a short period of time. I will agree that you can wait until 19H1, which will knock at our doors in a couple of weeks or so.... If things are not working for the better after that, you won't have any choice other than trying to find a solution, for you cannot stay on an old version of Windows 10. That will put your computer at risk for all the reasons we know.

With that being said, have you tried the SetupDiag, which seems to have worked for @Plodder (post #1583) or even some other steps from the article I have referenced to in post #1580. Honestly, if I were in shoes, I would try to find a solution right now in your spare time so that the transition to 19H1 can be as smooth as possible.

My logs revealed an error:
Error: Found AdvancedInstaller Generic failure.
Executable: iissetup.exe
Exit Code: 13
Phase: 38
Mode: Install (first install)
Component: Microsoft-Windows-IIS-DefaultDocument, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86
Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.

As zbook points out, your logs unfortunately, do not show any blocking match. Have you been through all these MS suggestions Resolve Windows 10 upgrade errors - Windows IT Pro | Microsoft Docs.

Caledon Ken said:

Did you guys run this exec that zbook posted? Does it reveal anything?

This is what I get. I have no idea what to do to fix it though. Any ideas? Only thing I see weird is that I am using ESET Nod 32 antivirus and not Windows Defender as the report says.



SetupDiag was unable to match to any known failure signatures.
System Information:
Machine Name = BOB-PC
Manufacturer = Gigabyte Technology Co., Ltd.
Model = To be filled by O.E.M.
HostOSArchitecture = x64
FirmwareType = UEFI
BiosReleaseDate = 20160406000000.000000+000
BiosVendor = F2
BiosVersion = F2
HostOSVersion = 10.0.17134
HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
TargetOSBuildString = 10.0.17763.345 (rs5_release_svc_prod2.190213-1831)
HostOSLanguageId = 1033
HostOSEdition = Professional
RegisteredAV = Windows Defender,Windows Defender,Windows Defender,
FilterDrivers =
UpgradeStartTime = 3/13/2019 10:14:22 PM
UpgradeEndTime = 3/13/2019 10:14:38 PM
UpgradeElapsedTime = 00:00:16
CV = axelgdJrQ0yBbx3/
ReportId = 82DD3C30-D6F9-4FB5-94E9-3B896CFC20C2