Dear Krzysztof Kamiński,
This behavior may indicate a failed update or corruption in the boot configuration. To begin troubleshooting, we recommend booting the VM into Recovery Mode using installation media or by interrupting the boot sequence three times. Once in recovery, you can attempt a system restore, uninstall recent updates, or run the following command to revert pending actions:
powershell
dism.exe /image:C:\ /cleanup-image /revertpendingactions
If the issue persists, check whether Secure Boot is enabled for Generation 2 VMs—disabling it temporarily may help. Also, ensure that Hyper-V Integration Services are up to date, as outdated components can interfere with startup after updates.
I hope this helps. Just kindly tick Accept Answer that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Best regards,
Domic Vo