Windows 10: Unable to upgrade from 1803 to 1903 - Error 0x8007001F - 0x2006

Hi All,

This is my first time posting on here, so apologies I have missed some information....

For the past couple of months my computer has been stuck on windows 10 Ver 1803 (Build 17134.706), and each time I have tried to update it, I am met with the following error message: "A current driver on your PC may be better than the driver we're trying to install. We'll keep trying to install."

It appears I have an almost identical problem to the one in this thread:
Can't Upgrade, Error 0x8007001F - 0x2006 and more, Stuck on 1709

I'm even met with the same update error once the update tries to install:
"The installation failed in the SAFE_OS phase with an error during REPLICATE_OC operation.

I have tried pretty much everything JakeWell tried in his post, but to no avail. However, later on in the post, he did manage to find the cause of his problem, and I believe I have the same issue. Many of the subkeys in the "Component Based Servicing" registry tree are either empty or completely missing. See below:





I have tried downloading an iso with the same version as my Win10 build and mounting the wim file using dism, and then exporting the missing subkeys, but when I try to import/merge them with my registry, I get the following error:





Any help with solving this issue would be much appreciated!

:)

 

Can't Upgrade, Error 0x8007001F - 0x2006 and more, Stuck on 1709

Hello, for the past year my brother's computer has been stuck on Windows 10 Ver. 1709 (Build 16299.371) and I haven't paid much attention to the issue until recently this month.

I've been trying to upgrade to 1803/1809 but been unable to due to Windows Update failing with this issue:
"A current driver on your PC may be better than the driver we're trying to install. We'll keep trying to install."





The problem is that all my drivers are up-to-date and the update that's trying to install:
"Feature Update to Windows 10, version 1803 x64 05-05B"

Always fail, with the installed attempts error in my update history being error 0x80240034 as shown below.





Windows Update isn't completely broken though as it installs other updates like definition updates to windows defender fine. Though only this one feature/cumulative update fails and I'm out of options on what to do.

I tried about everything I can to fix this issue ranging from uninstalling some of my drivers (audio, wifi, bluetooth) and updating them through Windows Update, downloading windows 10 official update assistance and media creation tool both failing. The main error being from the media creation tool (both upgrade and through iso) being error 0x8007001F - 0x2006 as shown below:





I tried sfc /scannow multiple times with no error/corruption found, DISM Online CleanupImage RestoreHealth which also completed 100% with no error/corruption found, and even chkdsk (at boot) which found nothing wrong with my drive.

I tried even using the WUMT (Windows Update MiniTool) to see if I can download and update the broken update but it also didn't work, giving me a failure to download: 0x80240022 error. Looking in the logs showed that when attempting to download the update, it kept on giving "404" errors.

Indeed I'm at a loss on what to do which is why I'm on here to ask for help.

Also lastly, I don't know why but the "Turn Windows features on or off" appears blank:





I already went into services and turned "Windows Module Installer" to automatic and start it up
but the features window still appeared blank after starting it. That and it reverts to manual after
every restart (though I read online that's normal and probably resets itself to manual by TiWorker? I personally don't know.)

The computer I'm using is an ASUS Desktop M11BB Computer that my brother brought online
back in 2017 which came with Windows 10 Pre-installed. I've updated my profile with the specs of
the computer in case you need to know whats in it. (I don't know all the specs but I believe the more important specs are enough).

I'm going to do everything to help upgrade windows to the newest version...hopefully.

 

Can't Upgrade, Error 0x8007001F - 0x2006 and more, Stuck on 1709

Hehehe...so it's been sometime but i'm here to happily report that...
I fixed it, yup I FIXED WINDOWS UPDATE WITHOUT DOING A CLEAN INSTALL/IN-PLACE UPGRADE!




WABAM! Window Update working again, up-to-date on Ver. 1809 finally!




I want to thank you ken for that link you first posted above for without it I wouldn't
have took the time to discover the problem after a lot of research!

So I found out why Windows Update was not working and I'll explain how I fixed it!

During my research after discovering the "get-packages" issue not working, I had a curious thought it
my mind that something was wrong in the registry as I searched online. This curiosity grew as I read both DISM.log/CBS.log files, live with notepad++ and it's "tail" function.

Looking at many threads online, I learned about the "Component Based Servicing" registry tree and took a look at it, thus leading to finding out this was the main problem of it all...




Many of the subkeys in the "Component Based Servicing" tree were both empty or completely missing (e.g PackageIndex, CapabilityIndex, Features on Demand, etc).

The following keys below were completely empty:

• DriverOperations*
• Packages
• Version

*Note: In the image, I already fixed the key which in-turn fixed the "A Current Driver may be better" problem. Fixing it caused WU to not report it but the error 0x800f0805 instead.

These keys were the reason I was unable to update, due to WU being unable to find important packages to loadup. I'll explain how I fixed all of these keys, first by explaining what repairing each key caused.

First off, repairing the "version" key caused the error message that CBS in dism.log throws:

to stop, now reporting that they successfully loaded the correct servicing pack version.

Second, repairing the DriverOperations key fixed the "Current Driver may be better" problem, as I said in the note above. Honestly I felt good when I found a connection to fixing the problem with that!

Now for the next two important keys, one that's missing and one that's empty...
I learned from reading a thread online that two important subkeys are required for WU to function (otherwise a repair install, system restore, etc is need) and they are "Packages" and "PackageIndex".

Both sub-keys are one of the major causes of WU not working for me, the dism command "get-packages" telling me that "no packages" were found being one of the reasons I looked up and discovered the registry tree for CBS!

It was not easy trying to find a way to repair this, but I had to download an iso with the same version as my Win10 Build 16299.371 that the updates installed (or slightly higher, like say 16299.402), mount the wim file with dism /mountwim command, load the SOFTWARE Hive within "X:\(MountDir)\Windows\System32\Config" and export the "Packages" and "PackageIndex" subkey (plus I exported the DriverOperations and Version Subkey from it, modifying them to import into my own registry with further modifications to match my version).

After importing both Packages and PackageIndex, I took the time to sort through almost every package key within them to remove any packages that weren't on my computer. (Probably didn't have to since I was upgrading but still).

I used the program "Everything" by VoidTools to search what packages were on my computer. (Basically by copying the package key name, then putting it into everything to see if it's installed or not.

It's better to show an example of what I mean then explain it:




Tedious as it was, It took no longer then two or so hours to sort through each key but
I believe it was worth it.

Since after I finished deleting those non-existence package keys, I then imported "CapabilityIndex"
and "Features on Demand" subkeys, then I restarted my computer and tried updating again and BAM
it started to download and install!




Everything downloaded, installed and my computer upgraded without a problem!
I never felt so happy that my research lead me to fixing this hopeless computer...not so hopeless now.

Anyways I want to thank y'all for helping, you guys suggestions were last resort suggestions but I stubbornly didn't want to clean-install this computer and well...I'm happy.

I took the time, energy, and patience to fix WU and upgrade. See y'all around, hopefully this may be helpful to those out there that may be experiencing this problem too...if you're experienced enough that is otherwise don't be afraid to ask for help!

 

Can't Upgrade, Error 0x8007001F - 0x2006 and more, Stuck on 1709

I'm back from doing all that research from that link you gave me Ken, thank you again for it.

I read and did everything that was in the link and been researching all the logs I have on my computer, checking each error and linking them to one common problem.

I'm still not sure but I think I have an idea what the main problem is and it has to do with the component store, mainly one or more packages not being valid/corrupted.

That and when I ran the following command in CMD:
Dism /online /Get-Features

This is the result:
"The specified package is not valid Windows package. Error: 800f0805"





This seems to be the issue, after reading through the CBS.log file, which had mention of a missing Foundation package, Optional Component Status not found, and that a missing matching version for the servicing stack is not found.

It pointing to this package of the servicing stack with the error:
C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.367_none_16d8803832210dee\

Not being found with error code 0x80070490 - ERROR_NOT_FOUND.
I like to upload all the logs that I read, as you guys may know more on what's wrong.
It contains the setupact logs, cbs, dism, etc. I also included the setupdiag results log and chkdsk results too!

I don't plan on taking any action to repair my computer just yet until I have an idea on what should be done.
From what I know, I think I may have to repair the package by replacing it completely with a fresh new one if possible but I'm not sure if that will fix everything.

If you need anything else, just ask me and i'll provide!
Also, I like to note that both DISM and SFC scan did not found any errors as shown below:









I took this pics before discovering the error above btw.
Thanks again for helping!