I subscribed for a dedicated server and I'm currently using IPMI to access it. I cannot download files for now... And I cannot install any apps, since it won't boot Windows.
After Windows Update and reboot, Windows Server 2019 won't boot.
After disabling recoveryenabled with bcdedit, Windows Boot Manager stops at an error 0xc000000d and mentions that \windows\system32\config\system registry is missing or corrupted.
On repair mode, I checked that \windows\system32\config\system exists.
SFC /SCANNOW fails with "There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."
I believe that's because there's a 1Mb pending.xml file on \windows\winsxs.
After renaming pending.xml file, SFC returns that it found no integrity violations. I'm not sure if SFC /SCANNOW would fix anything since I'm on repair mode anyways...
I ran DISM to check installed packages and there are two packages that seem to be what's causing the problem:
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.3991.1 - Uninstall Pending
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4550.1 - Install Pending
I believe that Windows Update tried to uninstall a package while installing a new one, and messed with registry files...
Anyone having similar problem? It's the second time this is happening. And last time, I had to reinstall everything. I would like to avoid having to do that again...
After Windows Update and reboot, Windows Server 2019 won't boot.
After disabling recoveryenabled with bcdedit, Windows Boot Manager stops at an error 0xc000000d and mentions that \windows\system32\config\system registry is missing or corrupted.
On repair mode, I checked that \windows\system32\config\system exists.
SFC /SCANNOW fails with "There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."
I believe that's because there's a 1Mb pending.xml file on \windows\winsxs.
After renaming pending.xml file, SFC returns that it found no integrity violations. I'm not sure if SFC /SCANNOW would fix anything since I'm on repair mode anyways...
I ran DISM to check installed packages and there are two packages that seem to be what's causing the problem:
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.3991.1 - Uninstall Pending
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4550.1 - Install Pending
I believe that Windows Update tried to uninstall a package while installing a new one, and messed with registry files...
Anyone having similar problem? It's the second time this is happening. And last time, I had to reinstall everything. I would like to avoid having to do that again...
Last edited: