PS: The OP tried that and posted in his #8 post (It failed). If I was the OP and had 4 systems that I was maintaining, I probably would not worry about it. There is an issue with that system, it may stay at 1709 for ever until its no longer supported. Then he should worry and maybe try A clean install.
I guess you didn't read far enough. I determined that computer #4 failed to upgrade, four times using the built in WU tool and then once with a manual install with the Media Creation tool. This is a computer that had no issues updating to every other iteration of Win 10, including 1709 last year.
I have done the quick fixes and tried installing after a clean boot. Still the same, 1803 fails to install and reverts to the previous version of Windows.Microsoft has made something that should be seamless to the user, a source of frustration for some usersIt's not even a consistent thing, some upgrades are no problems, others that upgraded with no problems in the past will fail with no obvious reason. My guess is it's due to the millions of different configurations, programs, and hardware in place on the windows based computers around the world.
Here's a link that covers some basic Quick fixes a you might try Quick fixes - Windows IT Pro | Microsoft Docs
I have 5 computers in my household, only one had difficulty upgrading to 1803, that was resolved by performing a 'clean boot' then installing the upgrade. Following the directions exactly I found it was easily done and easy to undo. https://support.microsoft.com/en-us/...oot-in-windows
Scroll down to the heading How to perform a clean boot in Windows and under the subheading Use the following steps to perform a clean boot select Windows 10 to open that menu for instructions on performing a clean boot, and how to undo that action.
That link was from the Resolve Windows 10 upgrade errors about 3/4 of the way down the page at Resolve Windows 10 upgrade errors: Technical information for IT Pros s IT Blog
I've read your post's, I know your computers are nearly identical, but something's preventing the last device from upgrading. Maybe something here will get that last one to 1803.
Good luck
I got a more specific error when trying to update manually, 0xC1900101-0x4001E. Its beyond frustrating as this computer (like my others) had no issues with previous upgrades. 1709 was installed fine and afaict there has been absolutely no changes to the computer since then. If its a driver issue, there are no new drivers to install as this computer was originally a Win 7 machine and the manufacturers site has drivers from 2012.
From the 3rd link in my postFarther down the page from that same link (near the bottom I found this)Result Codes: A result code of 0xC1900101 is generic and indicates that a rollback occurred. In most cases, the cause is a driver compatibility issue. To troubleshoot a failed upgrade that has returned a result code of 0xC1900101, analyze the extend code to determine the Windows Setup phase, and see the Resolution procedures section later in this topic.This all I have, you may not feel like pursuing this any farther due to time and effort versus return. As mentioned the 0xC1900101 is a generic error, but from the first quote it is likely related to a driver compatibility issue. There might be any one of numerous drivers causing the upgrade to fail, and may not be worth the effort to track it down.
0xC1900101 – 0x4001E Installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation. This is a generic error that occurs during the OOBE phase of setup. See the 0xC1900101 section of this guide and review general troubleshooting procedures described in that section.
edit: I looked at your system specs, went to the HP site, your model HP Pavilion p6608f desktop only shows Win 7 as the supported operating system. You're running W10 on three other machines so obviously it will run on that model, you might check drivers on one that's upgraded with this one. It's a tedious PIA but a 'stare and compare' might show something.
I would like to try the method dalchina posted as I read that others had success with it.
Still no 1803 on two computers - Windows 10 Forums
I am unclear as to how to copy the files from the "good" computer to the "bad" and also how to export the "good" registry keys. I could just delete and hope for the best but that seems risky. I tried to right click the C:\Windows\Provisioning files and pasting them to a notepad but it doesn't work.
As for just staying on 1709, sure that's fine but at some point support for it ends.
To export a registry key highlight it, click 'file' on the menu bar, choose 'export', the times I've done this I export the key to the desktop. You can do whatever is easiest, desktop, create a folder, my documents, etc...
To restore it do the opposite and 'import' the key.
I apologize for not reading every post I guess I missed some
I had the same issue with one of my units
the solution was to repair with DISM the current 1709 and then 1803 installed with no issues
From an Admin CMD prompt
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
Dism /Online /Cleanup-Image /StartComponentCleanup
SFC /scannow
start the setup.exe from within windows this solved my issue and saved me from a clean install on a very complicated business computer.
I'm in the process of doing this though I previously did a DISM command as suggested in the Quick Fixes link. Question about the last step. Where do I find this setup.exe within Windows? Or do you mean on the USB drive where I have the 1803 update?
Weirdly I thought I might have had success in my last try as I got the Windows Privacy setup screen, but behind it was the failure message.
setup.exe as derived from your downloaded iso.
If you mount the iso, then open the drive letter created and run setup.exe
If you've created a bootable USB drive, then of course that one.
This tutorial contains a great resource on logs and analysing upgrade failure. Dig through the links.
Upgrade to Windows 10 | Windows 10 Tutorials
(Yes I know it says upgrade to Win 10 - it's about the upgrade procedure)
Quote
