We had the same issue this morning, on a 2022 Server Standard host and two 2016 vm's that wouldn't boot up. Renaming the VHDX fixed it.
VM's won't start since Windows Updates October 2023
Since the installation of the October 2023 updates, random VM's fail to start after a reboot of the HyperV server (2019 DCE).
The error is: *<VMName> failed to start.
Synthetic SCSI Controller (Instance ID ....): Failed to Power on with Error 'Incorrect function.'.
Attachment '<path to vhdx file>' failed to open because of error: 'Incorrect function.'.*
To solve the problem, I have to:
- Remove replication
- Rename the vhdx file from the settings, press apply
After this rename, the VM starts without a problem. Yesterday I had 2 VMs with the problem, today 6 VM's had the problem.
The strange thing is that everything works after I rename the vhdx file.
Is anything known about this - is there a solution?
Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
8 answers
Sort by: Most helpful
-
-
Karl Wester-Ebbinghaus 41 Reputation points MVP2023-10-22T16:50:22.6633333+00:00 Hi there is another discussion in answers forum going on please find the thread here and a workaround.
See https://techcommunity.microsoft.com/t5/azure-stack/starting-vms-may-fail-after-installation-of-10-2023-cu-when/m-p/3956844/highlight/true#M148 -
Isaac Oriokot 0 Reputation points
2023-11-16T12:54:47.7866667+00:00 We faced the same problem after installing (KB5031364) update on Windows server 2022. One of the VMs had failed to start and we were unable to uninstall the security update.
Fix.
Go to windows catalog
Download the update(21h2 or 22h2 depending on your environment)
install it, then uninstall it and restart.
Then block the faulty update.
The VM should be able to start.