Forum Discussion
Server 2k19 Hyper-V VMs no longer start
I'm having some issues with VMs no longer starting. This started May 11th 2022. The last updates that I see installed around that timeframe are KB5001384 and the May 10 KB5013941. Tried to unin...
Hello samw5875,
The error 0x80073701 is ERROR_SXS_ASSEMBLY_MISSING, meaning some system files are missing, causing the Windows update installation failure. The 0x80073701 error appears due to missing system files. System files get corrupted or deleted due to various reasons.
However, you can follow the steps mentioned below to troubleshoot Hyper-V VMs no longer start issues,
Run Windows Built-in Troubleshooter:
The Error 0x80073701 can be solved using the built-in Windows Update Troubleshooter,
- Firstly, right-click the Start button and click Settings
- Then, In the left pane, select Troubleshoot.
- Now, In the right pane, click Additional troubleshooters.
- Lastly, select Windows Update and click Run the troubleshooter.
The Update troubleshooter should provide fixes and apply them automatically.
Flush the SoftwareDistribution Folder:
- Firstly, press the Windows logo + R keys to open the Run dialog
- Then, type in CMD and hit Enter to open the Command Prompt.
- Now, type the following command and press Enter,
net stop wuauserv
- Next, type in rd /s /q %systemroot%\SoftwareDistribution and press Enter to clear the Update cache folder.
- Lastly, type in net start wuauserv and press Enter.
Execute a System File Checker (SFC) Scan:
It replaces the corrupt, missing files and downloads them, causing a 0x80073701 error.
- Firstly, press the Windows logo + R keys to open the Run dialog
- Then, type in CMD and hit Enter to open the Command Prompt.
- Now, type the following command and press Enter,
SFC /Scannow
- Lastly, restart your server.
Execute DISM scan:
DISM is a command-line tool to fix corrupt system files,
- Firstly, press the Windows logo + R keys to open the Run dialog
- Then, type in CMD and hit Enter to open the Command Prompt.
- Now, type the following command and press Enter,
DISM /Online /Cleanup-image /StartComponentCleanup
- Then, type the below and hit Enter,
DISM /Online /Cleanup-Image /ScanHealth
- Next, type the following command and press Enter,
DISM /Online /Cleanup-Image /RestoreHealth
- Lastly, restart your server and check for the error.
Reset Windows Update Components:
- Firstly, press the Windows logo + R keys to open the Run dialog
- Then, type in CMD and hit Enter to open the Command Prompt.
- Now, type the following commands and press Enter on each command,
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
- Then, rename the SoftwareDistribution and Catroot2 folders, type the following command, and press Enter,
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
- Then, type the below command and hit Enter,
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
- Lastly, re-type the following commands and hit Enter on each command to restart stopped services.
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
After restarting Windows update components, you must check whether the issue persists.
I hope the above fixes help you to resolve the Hyper-V VMs no longer start on Server 2019 with error code 0x80073701 without facing any problem.
-----------------------
Regards,
Austin M
- Hi Austin_M
I have this exact same issue with a newly installed Hyper-V host and newly created VM. Did you find a solution?nothing that worked. Vms on that box weren't critical so the next step was going to export them to another host but haven't gone around this.
I tried tons of stuff including remove NICs, DSIM reports, reinstall roles nothing seemed to work 😞
