Windows 10 10586 (1511) upgrade fails / error 0x8007002C - 0x4000D

It seems DISM can't locate the source files it needs. I think there is a fix for this but I don't know the answer. Maybe someone else on the forum can advise you?

You can uninstall the driver software from the Programs menu but this may not remove the driver files from your PC.

The fix for that is mounting a DVD containing the Win10 ISO. I have that, except that I do not know which one I have to mount. The one back from build 10240 or Build 10586 (they one they currently offer on their site)

I would expect you should use the ISO for your current Windows version.

I've just had a read through your logs provided, it seems to be a specific Network driver which is failing to update (Incompatible or outdated).

"SYSTEM\CurrentControlSet\Control\Network\{6bdd1fc5-810f-11d0-bec7-08002be2092f}\{652def3d-35e7-4159-b8a0-084dcde0ea3e}"

Do you have the Motherboard model? We may be able to find compatible drivers (Realtek or Intel) dependant on what is on board.

In the mean time, Some ideas that may help.

• Uninstall the Network drivers to at least try and get the installation back on track.
• It may even require you to add your device specific driver to the installation media (If a compatible version can be found).
• If possible remove / Disable the network adaptor until you resolve the issue.
• Remove the Registry keys that are being referenced with errors in the logs.

That makes sense!

I've namely had problems with the LAN network driver before.
At some point, I had BSOD's back in Windows 7, whenever trying to shut down the computer, if during its on-time it had gone into sleeping mode at least once. (DRIVER_POWER_STATE_FAILURE) Analysing crash dumps related the problem to files called something like Rt64.dll, which is indeed from the network adapter. I fixed that by updating the Realtek PcI GBE Family controller driver from realtek website and that fixed the issue. However afterwards I had found a program on my computer which contains the stock drivers from the motherboard (eMachines ET1870, quite an old motherboard back from 2011) and since realtek wrote on their page that newer isn't always better and it's recommended to use the driver version that came with the motherboard, I downgraded back to the original version, which probably wasn't a good idea. (Did so after upgrade to win10)
I was already having a feeling that driver would cause issues in win10, because sometimes my PC wouldn't go into sleep mode naturally at all... And that was whenever my printer was powered on (perhaps that's the link with all those printer error messages?)
Yesterday I updated that driver again, after the failed 1511 upgrade attempts though. I'm not at home for the rest of the week but I'll re-attempt the upgrade friday evening.

PS: any idea why the 1511 update doesn't appear in Windows Update, limiting me to the media tool? Any chance that might be related?

have you fixed this problem already?
I seem to get the errors on the same inf keys you do but the rest of my error log looks different....

Volle said:

have you fixed this problem already?
I seem to get the errors on the same inf keys you do but the rest of my error log looks different....

No, haven't had the time to continue and I still won't have any until 2nd week of february.

Hey,

i fixed it right after posting here so here's what i did. There's a TL;DR down below but i'll explain it in detail first.

I had problems upgrading from windows 10 to windows 10 1511 TH2 back in November '15. After countless failed tries from within windows update i decided to use the Media Creation Tool to create a thumb drive (since i didn't want to download the update for another 20x while trying to update).
After build 10586 was release i gave it another try which made no difference at all.

Today i managed to upgrade from win 10 -> build 10586, from win 8.1 -> build 10586 and from win 7 SP1 -> build 10586 with a thumb drive at work from various machines. but those machines were windows only machines, my personal machines at home are all dual boot machines (windows & linux)

So here's how i fixed it on my computer:
My mainboard is an Asus X79-deluxe, all drivers and the bios were up2date before trying it.

When i tried to install the november update it went like this:
Installation was started -> Reboot -> Some console windows was popping up but closed again before you could read anything -> reboot -> infinite circling dots ( i once let it run for 6hrs, no change) -> Reset -> Message "Update failed, restoring old OS" -> Reboot -> infinite circling dots -> Reset -> Working -> Windows 10 (like before).
Back in windows i sometimes got an error message which was saying that an error occurred on BOOT during FIRST_BOOT and an error code (which i sadly can't remember).

I have 2 HDDs with the following partition layout in this machine:
sda: [*windows boot][windows]
sdb: ->[*linux boot (syslinux)][linux]
-> is the hard drive that gets booted by bios
* are "active" partitions which have the boot flag set

I've setup my bios to boot from sdb. When i read the message about an error during boot i setup my bios to directly boot from sda, which didn't help. I read (on reddit or another forum, can't remember) from other Asus users which had a similar problem which fixed it by shutting down the machine whenever it did reboot on its own. This also didn't fix my problem. Some people said we'd have to wait for Asus to release a bios update...

Yesterday, after i created the thumb drive with the Media Creation Tool, i unplugged sdb (with all the linux stuff) and setup my bios to boot from sda. I launched the update from withing windows (run setup.exe from the thumb drive) and everything went completely fine. After windows was updated i shutdown my machine again, plugged sdb back in and setup my bios to boot from sdb again. So this was easy but i never had thought that it mattered that my linux drive was attached (since i didn't boot from it...).


My 2nd machine is my Notebook (Lenovo T550 with nvidia gtx 940m) which has only one hard drive.
My partition layout is like this:
sda: -> [*linux boot][linux][windows boot][windows]

When i tried to update to 10586 from windows update it just failed (giving the error log from my last post). When i started the update from the thumb drive it failed with a message that i didn't have enough space on disk (i had 110GB free on my windows drive so this error message was obviously wrong). When i searched the error messages

Code:

Failed to get inf path SYSTEM\CurrentControlSet\Control\Network\{4d36e975-e325-11ce-bfc1-08002be10318}\{58474950-424f-0058-cfe8-aba2187557f2}
Failed to add net component 80070002
Failed to open inf key SYSTEM\CurrentControlSet\Control\Network\{6bdd1fc5-810f-11d0-bec7-08002be2092f}\{652def3d-35e7-4159-b8a0-084dcde0ea3e}

I found some posts about an xbox controller (i deleted the registry entries, which didn't help). I found another post which was talking about some bluetooth / network drivers which are broken (i deleted some more registry entries which also didn't help).
I used sfc /scannow from an elevated command prompt which found some error which it fixed but it didn't help with the update problem....
I tried to fix my boot partition from the booted thumb drive (my version is in german so i don't know the menu entries i used to get to the command prompt withing windows setup) with bootrec /fixmbr and bootrec /fixboot where one of the commands did succeed and the other failed. This also didn't help.
I tried to run the setup via booting the thumb drive directly but this failed almost instantly with an message that you can only do a clean install and no update via this method.
I updated my bios which also didn't help.

So i booted back to linux and set the boot/"active" flag of my 3rd partition ([windows boot]) and removed the one from the first partition ([linux boot]) with fdisk option a.

I rebooted and the machine did boot directly into windows (as expected). I did start the update from the thumb drive and everything went fine. The installation didn't give any errors. To fix my boot order i rebooted to the thumb drive with the windows update again and went to the command prompt.
In there i set the boot/"active" flag to my first partition ([linux boot]) via diskpart.
Description: http://superuser.com/questions/59691...-with-diskpart

Code:

DISKPART (to open the partition utility),
LIST DISK (disk number(s) will be shown),
SELECT DISK n (where n is the number of the disk - probably 0),
LIST PARTITION (partition number(s) will be shown),
SELECT PARTITION n (where n is the number of the Primary partition you wish to make Active),
ACTIVE (the selected partition on the selected disk will be made Active),
EXIT (to exit DiskPart),
EXIT (to exit the Command Prompt),

After this my machine did boot to linux again.
Problem solved.

What you have to remember is that i installed windows 10 after i installed linux on this machine. The windows 10 setup did create a new boot partition in the free space after my linux partition. If i remember correct previous windows versions did use partition 1 as boot partition even if partition 1 was already used so you might have to reinstall your linux boot partition after you did the above (or it might not work at all).

TL;DR:
1) Use the media creation tool to create a thumb drive and run the update from there
2) Unplug your linux boot drives
3) Set the boot/"active" flag of your windows boot partition

I hope this wall of text is for use for anyone out there :P