Forum Discussion
Windows Server 2022 Hyper-V guest state not saved on host reboot
This was driving me insane until I found your post. I spent hours checking my setting and doubting my abilities but in the end I feel vindicated that it wasn't "my issue".
On my Hyper-V host I have 3 Windows Server 2022, 1 PfSense (based on BSD) and 1 Open VPN Access Server (Ubuntu). PfSense was the culprit. After removing the integration service named "Backup (volume shadow copy)" the automatic stop actions started working.
The weird part for me is that it was only happening on 1 out of the 3 Windows Server 2022 VMs. I suspect it had to do with the order in which the VMs were being processed.
Thank you!
Hi!
Happy to hear you resolved the issue and regained your peace of mind!🙂
I've experienced similar behavior, in my case it was OPNsense. I've had servers where it worked too, and maybe you're onto something here. If FreeBSD is the last one "out the door," the others may have time to shut down properly. Put a lot of time into this but, as you, could not solve it.
I went as far as creating my own solution before I found out that it was FreeBSD causing this issue. I totally customized the shutdown and startup PowerShell procedure to handle what Hyper-V should do.
As figured. A much easier solution is just to disable the VSS service.
Recently, I tested again with the latest FreeBSD 14.2 (and Server 2022 and 2025), and unfortunately, the behavior is not fixed. So until it is, we'd better disable that integrated service.