I've been using this Windows 11 VM on Parallels for macOS Apple Silicon for three years now. After the latest Windows Updates today, I started getting this blue screen upon boot: The image above is available at this address, in case it does not show in-line properly: https://ibb.co/FwPZwRF Now the odd thing is, I reverted to an old version of this VM backed up on an external thumb drive (kept offline), and it too, is showing the same BSOD! I would have thought Windows Update broke something, but what is going on? This is super odd! Anybody else seeing this problem all out of the blue (quite literally)?
Verified that this happens only after the latest Windows updates. Discard the red herring about it happening to offline VMs. Somehow replacing the .pvm file/folder wasn't enough to replace the VM as Parallels managed to keep a link to the renamed, broken .pvm file/folder (interesting feature there) - and booted that one up, instead of the restored backup. Updating the backup through Windows Update consistently reproduces the issue. The issue also reproduces consistently across different Apple Silicon hardware. Am I the only user seeing this?
These are the last updates that seem to work fine: https://ibb.co/b3PXsTk Installing these updates renders the device unbootable (and also unable to enter safe mode): https://ibb.co/tXKLrs4 Does this seem like a Microsoft issue, then?
Same issue here, wonder how this can be fixed? Has anyone been able to boot into any kind of recovery mode to revert?
I've just solved this problem by repairing with a Windows 11 installation ISO. It can be downloaded by interrupting the new installation process described here (Running a complete Windows 11 for Arm installation process with OOBE on Mac computers with M-series chips (parallels.com)). The ISO file can be found in Downloads folder. I mounted it to CD/DVD in Configuration and changed the boot order to start from CD/DVD. There is then a repair option.
Parallels deleted my account after I reported this issue directly to their support and they said they'd need to look at it. Has this happened to anyone else before?
AFAIK this issue hasn't been fixed yet. Anyone else running into it, or has Microsoft pulled the errant update (assuming it was their fault)?