I'm running the current release of Parallels Desktop for Mac 12. It used to work ok, but now refuses to boot Windows 10 and will not let me kill the virtual machine. I've done a search and found some info but no solution. When I look at the package contents of the .pvm file, I see it references Apple SSD SM5 12E (disk0).hdd When I look at the virtual machine configuration, it shows it's trying to boot from APPLE SSD SM1024L (disk 0) and it won't let me edit anything because the VM is active. However, I can't stop the VM. The only option I can get to is to suspend the VM and that doesn't help me. Suggestions on how to clear this up?
Please select OK to the prompt in the screenshot. Type "Exit" in Shell> command. From Mac menu Actions > Stop: http://bit.ly/1OfR3td Open virtual machine configuration > Hardware > Boot Order > Advanced Settings > Uncheck Use EFI Boot option. Then, try running Windows virtual machine and keep us posted the result.
I wish it was so simple. The first thing I tried was to type exit. It took me to a different menu - I have been down every option of every sub-menu that I can get to and have not found a way to get it to exit the boot procedure. I realize I can probably trash the whole VM but I don't want to do that because I'm likely to run into issue with software that's loaded not wanting to be 're-installed' in the new VM that gets created. Too damn many software products decide you are trying to cheat your license when that happens. I'm not looking for the aggravation as I already wasted 2.5 hours with Microsoft and the license issue to run the VM to start with.
Just a followup - it doesn't work. I have received emails from Parallels support and will be using them to try and fix the issue.
Hi TomW8, basically, the error comes up on booting virtual machine that is converted from VMware (.VHDX) VHDX supports sector size of 4KB offering various benefits and aligns well with the industry moving towards 4KB physical sector size for HDDs. Please reboot your Mac and then try the steps mentioned in the previous post and let us know the results.
Well, I have never used VMware, so it didn't come from that. Today I updated parallels to the latest v12 build (new since I last tried to get it to run), turned off EFI boot (got the error) and then while being monitored by tech support turned on EFI boot and - it worked. Not sure what's different other than the latest parallels build as I had tried it all before without success, but tonight it worked. Problem now solved.
