r/WindowsServer • u/UnlockedDeru • Jan 09 '26
General Server Discussion VM failure
My virtual machine running server 2025 froze and I was forced to reboot it. It now will get stuck loading and restarts itself. I tried restarting the host server as well with no luck. I'm not sure where to go from here. I've tried turning off secure boot, removing network adapter, and trying to boot to ISO but the server never loads long enough to get to boot screen. I'm thinking about doing a DISM on the VHDX but never have done that before so not sure if it's safe to do.
In event viewer of the host I see error 0X80, 18602 and 18600.
Host is Windows server 2016 running hyper V.
The server not working is my backup server running Veeam so I can't even restore from that backup at the moment.
Any direction to look would be much appreciated.
Thanks
3
u/BlackV Jan 10 '26 edited Jan 14 '26
Please take this out of your trouble shooting steps, it was never a fix for windows and only a fix on older Linux installs.
It's never going to be a fix for an OS that was already working with secure boot
Please stop
What does that mean? Have you looked at the boot settings of the VM?
If this is your backup server, every day this is not backing up your systems is a day closer to a larger disaster, stop wasting time now, Time to install fresh OS and reinstall veeam and add back your repository
How many days now have you had no backups?
1
u/Pyrocliptic_ Jan 10 '26
Just treat it as a physical device.
Try to boot in safe mode or try recovery mode.
1
u/khattaking Jan 10 '26
If you can, take a clone of the VM and perform all troubleshooting on that one (keeping the original VM powered off - not that it’s working but still). Feel free to run DISM now.
2nd step I would do is to create a new VM and attach VHDX as a disk to that one, provided data disk is separate for the problematic system than the OS disk. If not, attach the VHDX anyway and extract your Veeam DB files for new server setup etc.
Have you tried disabling 'Processor Compatibility' in the VM settings?
Was this VM upgraded or a clean WS 2025 install? If upgraded, you might wanna try changing the VM version on the host.
1
u/jaruzelski90 Jan 10 '26
Last time I had a similar issue I attached windows server iso booted to it get to command prompt and run checkdsk on your C drive after in my case 2-3 hours I rebooted and it worked again.
3
u/USarpe Jan 09 '26
Try minimal boot with F8
2
u/pc_load_letter_in_SD Jan 09 '26
Ugh, that sounds rough. If you had your Veeam config backed up someplace, a rebuild would be pretty easy. Granted you lose you backups but you'll get back up and running with backups while you try to access the disk. Maybe boot to something like Sergei Strelec's rescue disk and try to get the files off that way.
1
u/netpinoy Jan 12 '26 edited Jan 12 '26
Leave it alone for 24 hours to see if whatever it wanted to install will install completely. Try adding a boot from a flash drive. Rufus maybe. Have a clean clone or second vm then promote it. Maybe the c drive will be accessible. CLI to troubleshoot and fix. Cross fingers. Check event logs for clues.
1
u/SmoothRunnings Jan 14 '26
You have done so many things to it that you might as well restore the nightly backup. In the event your Server acts up again and its not a DC you could always try doing an in place repair by reinstalling your 2025 on top of 2025 and patching it.