Hey everyone, I'm facing a major issue with my Windows Server 2019 domain controller that seems to have malfunctioned after trying to apply the November updates. I'm running this on Hyper-V as a Gen 2 VM, and somehow, it messed up its component store. Here's what's happening:
- Apps won't open and are throwing errors like *'This application requires .NET Framework v4.0.30319'* even though .NET 4.8 is installed.
- The .NET Repair Tool and offline installers are both failing.
- Windows Update isn't working and keeps showing **0x8024a204**.
- System File Checker (SFC) detects corruption but can't fix it, and DISM claims the store is fixable but fails to repair.
- The CBS (Component-Based Servicing) logs indicate missing manifests and corrupted source files.
The trouble began sometime between November 1st and 14th when some updates were being applied. It seems like an update process got interrupted, leaving everything broken—.NET, Windows Update, and more. The only option I see currently is restoring from a backup taken before November 6th. Has anyone else encountered this? Is restoring the best way to handle this, or am I missing other potential solutions to avoid this in the future?
3 Answers
Before you consider restoring, I recommend rebuilding the DC from scratch. Migrating to a new VM might help ensure you don't face the same issues again, especially if the root cause of the failure is unclear. It's a more robust solution than relying on backups that might have the same underlying issues.
But why replace it? If it's just a minor corruption, a restore could do the trick! I shared a similar experience about the safeguards in recent updates that make restoring safe. It could work out.
I had a somewhat related issue last month where a server suddenly lost a registry key crucial for a specific .NET version, causing apps to fail. I copied the missing key from another server and fixed it easily. Check if something like that could be happening here!
You might want to consider nuking the current VM and setting up a new DC, then replicate AD from another server you have. It could save you a lot of future troubles compared to trying to fix this one.
Agreed, rebuilding seems to be the best call here. You can always restore from a backup in a separate, isolated environment if you want to investigate what went wrong. But for now, starting fresh may save a lot of headaches later.