Windows 10 Update Error 0xe0000100

[Devastator0]

All,

Back in November I updated my Windows 10 install to 1909 (previously was 1809) and since then, with both the November 2019 and December 2019 monthly updates, they are now failing with the error code of 0xe0000100. I've tried running the following in an elevated command prompt:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

but that hasn't had an effect. I've run a chkdsk /F /R on my OS drive and also a SFC /scannow but none of these things seem to fix the issue. I'm kind of at my wits end with the problem and not sure what else to try to fix this issue so I ask the TPU community for any help/advice. I would rather not have to do a format and re-install of my OS at this point in time if it can be avoided.

If you need any further information or think more specific data can help, please let me know as I'll be watching this thread.

Cheers to anyone who replies/provides some advice for me!

 

[biffzinker]

Have you tried: dism /online /cleanup-image /scanhealth in a command prompt/PowerShell?

You can switch out /scanhealth for restorehealth if corruption is found.

 

[Devastator0]

Have you tried: dism /online /cleanup-image /scanhealth in a command prompt/PowerShell?

You can switch out /scanhealth for restorehealth if corruption is found.

Ok, so I did this and this was the result:

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.418

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.418

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>

Checked for updates after doing that but when performing the reboot after installing updates, I got a message again saying that updates cannot be completed, undoing changes.

 

[eidairaman1]

Check with askwoody.com

 

[btarunr]

Ok, so I did this and this was the result:

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.418

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.418

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>

Checked for updates after doing that but when performing the reboot after installing updates, I got a message again saying that updates cannot be completed, undoing changes.

I once had a power-loss when the system was updating (the screen with the "don't turn off your computer" message), and then got this error. Nothing fixed this (SFC, BITS prune, DISM rebuild, Microsoft's rubbish Windows Update troubleshooter, nothing). Manual update installation don't work, either.

In the end I had to re-install.

 

[biffzinker]

So you had corruption in the WinSxS if it reported back the component store is repairable otherwise if nothing is found it reports something similar to no errors found.

If something is still corrupted that the Windows update service depends on then the restore switch with DISM is probably not going to work since it retrieves files over the internet from Microsoft's servers to fix the corrupted system files.

Might be quicker to do a backup what you need, and do a clean/reinstall of Windows.

It's always been a 50/50 split if I've managed a complete repair of Windows vs a reinstall.

 

[Devastator0]

So you had corruption in the WinSxS if it reported back the component store is repairable otherwise if nothing is found it reports something similar to no errors found.

If something is still corrupted that the Windows update service depends on then the restore switch with DISM is probably not going to work since it retrieves files over the internet from Microsoft's servers to fix the corrupted system files.

Might be quicker to do a backup what you need, and do a clean/reinstall of Windows.

It's always been a 50/50 split if I've managed a complete repair of Windows vs a reinstall.

Damn, that is unfortunate. Looks like I have a bit of work ahead of me (I have hardware to build a new rig) but my hope was that I could repair my current O/S install and then clone the drives to the new ones I got.

 

[biffzinker]

So you had corruption in the WinSxS if it reported back the component store is repairable otherwise if nothing is found it reports something similar to no errors found.

Here's what it reports when no corruption is found.

PS C:\WINDOWS\system32> Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.535

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>

 

[Devastator0]

Here's what it reports when no corruption is found.

PS C:\WINDOWS\system32> Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.535

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\WINDOWS\system32>

Yeah, see, so I ran that same command again just now and I got the same message (i.e. No corruption detected), but the updates still fail with the same error message.