Windows Update Error 0xC1900101 - 0x4000D

R

rmirwin2

Contributor
Joined
Mar 10, 2019
Posts
16
Hello!

Moving to this thread from a BSOD thread after performing a restore from backup to get an earlier version of 1511 or 10586 to load without BSOD's.

After successfully installing all updates for version 10586, I attempted to update to 1803 via the ISO and have twice obtained this error. Attached are the logs.

This is an Asus Z97A with 3.1 USB. I'll update this post with the previous thread and information about the machine this afternoon.

I'll be peeling back drivers and retrying, but I could really use a hand to see what's at the bottom of this issue.

All help appreciated!

Rich
 

Attachments

Hello!

I'm finally getting back to this problem and posting additional information in view of the protocol here.

I originally posted the following thread in the BSOD area after an update of Windows 10 Pro on 12/26/18 left the computer with that problem and stuck at version 1511 build 10158.1176. Here's that link: BSOD - Windows 10 Stuck at 10586 - Microsoft Drivers Unsigned.

I haven't given up on continuing from that point, but it looked like that was going to be a hard slog to recover it.

So, I followed up on restoring a copy of a backup taken back in July of 2016. The machine does motion control, so there weren't many changes since then. I was hoping to be able resurrect that backup and then update to the current Windows 10 Pro environment.

The backup boots up fine so, after cleaning it up a bit (removing NVIDIA and a few other drivers) I went forward to update using the 1803 ISO. The zip files above show the results.

Here's the machine:
· OS - Windows 10
· x64 (64-bit)
· Originally installed OS on the system was W7
· Upgraded from Win 7
· 4 years old approx
· Was upgraded 2 years ago to 10.
· CPU 4970K
· None (Intel graphics but had Nvidia card installed/removed prior to problem)
· MotherBoard - Asus Z97A
· Power Supply - Corsair 600W
· Homebuilt desktop system

I've run the following this evening after updating the motherboard's bios:

SFC /scannow which reports
"Windows Resource Protection did not find any integrity violations."

DISM /online /cleanup-image /restorehealth
"The restore operation completed successfully.
The operation completed successfully."

SFCFIX.exe reports:
"
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-03-20 22:19:51.733
Microsoft Windows 10 Build 10586 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-03-20 22:20:09.605
----------------------EOF-----------------------"
 

Attachments

Hello softwaremaniac!

Thanks for the suggestion but I think this one's done!

I believe I have this update problem (1511 -> 1809) solved starting from the recovered (copied back from a 2016 WHS2011 backup) Windows system.
After removing all the add-on drivers, and performing DISM /online /cleanup-image /restorehealth followed by SFC /scannow repeatedly, no corruptions or errors continued to be found. I began to notice that when the install went to 100%, and after several reboots, eventually I caught a snapshot of "PAGE FAULT IN NONPAGED AREA What failed: TcRTime.sys"
Looking this up, this turned out to be part of the Beckhoff TwinCat3 system, which I thought I'd uninstalled.

Looking more at it, I found that my Beckhoff deinstallation had apparently failed to remove the application entirely and couldn't be removed by the Windows Installer. So, I broke out IObit Uninstaller and that cleanly remove it.

Voila! After a reboot, the Windows update from ISO went perfectly!

So, I went back to the original backup image from the drive we worked on in the BSOD thread. This is a copy of the original disk that had gotten stuck at 1511. That image still had BSOD'S. I went ahead on that one to use IObit Uninstaller to clean it up. Beckhoff was also incompletely removed there too. Then I ran some DISM and SFC's on the image as earlier. SFC reported corruptions it couldn't clear. On reboot, the BSOD's still remained and it was still necessary to boot with driver signing enforcement disabled. And the usual 18 Microsoft drivers were still reported as unsigned. No symptoms had changed.

However, I went ahead and tried the in-place update via the ISO. To my surprise, this went perfectly, and the machine woke up in build in 1809!

I have to conclude from all that that the Beckhoff drivers were likely the original problem. Not sure how that caused the BSOD symptoms and unsigned drivers, but they certainly hosed up the Windows Update.

Back to business.

Thanks to you all for your suggestions!!

Rich
 
Another observation.

It seems strange that I've successfully reinstalled the same version of TwinCat3 (build 4020) to the updated image where I had to remove to get Windows to update. No problems/warning/failures at this point. I did this to ensure the application (motion control) was working and viable and will migrate the application to the newest version of TwinCat3 (Build 4022.29) after I test it out.

Still, seems weird that if 4020 caused such grief it seems like Windows would have objected to it by now. Hopefully I'll have it off of this machine by the time of the next major update!

Thanks again!
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top