VM will not boot after update to Parallels 14

L

Lotus54

Bit poster
I've been running Parallels for a long time. I had an older version (I can't find now what it was) and everything worked fine.
After doing the 'update' to 14, the VM will not boot. It says there is not OS on the boot drive. I cannot shut down the VM either, so I can't modify any settings.

I changed my permissions on the boot file so everyone had read/write access (along with me as a user and administrators also).
Still will not boot.
help!

NSAYok6.jpg
 
Last edited:
Lotus54 said:
I've been running Parallels for a long time. I had an older version (I can't find now what it was) and everything worked fine.
After doing the 'update' to 14, the VM will not boot. It says there is not OS on the boot drive. I cannot shut down the VM either, so I can't modify any settings.

I changed my permissions on the boot file so everyone had read/write access (along with me as a user and administrators also).
Still will not boot.
help!

NSAYok6.jpg
Click to expand...
Hi Lotus54. Please provide the screenshot of the error message along with the virtual machine file size.
 
I posted the error message in my original post.
the size is 34.88GB

I tested another virtual hd- it initially started, but after the 'upgrade' to operate with Parallels 14 it did the same thing.
it appears it *may* be a permissions issue, but I have read & write all all users in the 'info' on the virtual machine.

I can mount the VM and it most certainly still has the OS files on there.
 
Lotus54 said:
I posted the error message in my original post.
the size is 34.88GB

I tested another virtual hd- it initially started, but after the 'upgrade' to operate with Parallels 14 it did the same thing.
it appears it *may* be a permissions issue, but I have read & write all all users in the 'info' on the virtual machine.

I can mount the VM and it most certainly still has the OS files on there.
Click to expand...
Hi @Lotus54, it might occur due to the incorrect Host permission. Can you please shut down Windows virtual machine properly, quit Parallels Desktop 14 for Mac, reboot your Mac into Recovery mode, run First Aid, restart your Mac back to the normal mode and then start Parallels Desktop to check if that works.
 
I had this same issue and went through the various recommended steps of modifying access rights and editing the XML file, all to no avail, although I did not try the suggestion above regarding Recovery mode and First Aid. What finally worked for me was to use Parallels Control Center to clone the non-booting VM. The cloned VM booted properly, presumably because the act of copying the original created a new VM that MacOS allowed Parallels to have write access to. I then deleted the original VM. I have been a very happy Parallels user for over 8 years and recommend the product to those I think might have an interest. But I encountered this issue a few months ago when attempting to upgrade Parallels on my work Mac and reverted back to the prior version because the recommended solutions were not working for me. I simply couldn't afford to be without my Windows VM at work for any period of time. So a few months later I decided to upgrade the home Mac to Parallels Desktop 14 and ran into the same issue, finally resolving it as described above. I will make another attempt with the office Mac, knowing that a solution is possible. I state all this as a possible aid to others who experience the 'Hard Disk 1' issue, but also to express my mild disappointment with the Parallels technical team. But having said all that, I still compliment them on a great product.
 
RobertV14 said:
I had this same issue and went through the various recommended steps of modifying access rights and editing the XML file, all to no avail, although I did not try the suggestion above regarding Recovery mode and First Aid. What finally worked for me was to use Parallels Control Center to clone the non-booting VM. The cloned VM booted properly, presumably because the act of copying the original created a new VM that MacOS allowed Parallels to have write access to. I then deleted the original VM. I have been a very happy Parallels user for over 8 years and recommend the product to those I think might have an interest. But I encountered this issue a few months ago when attempting to upgrade Parallels on my work Mac and reverted back to the prior version because the recommended solutions were not working for me. I simply couldn't afford to be without my Windows VM at work for any period of time. So a few months later I decided to upgrade the home Mac to Parallels Desktop 14 and ran into the same issue, finally resolving it as described above. I will make another attempt with the office Mac, knowing that a solution is possible. I state all this as a possible aid to others who experience the 'Hard Disk 1' issue, but also to express my mild disappointment with the Parallels technical team. But having said all that, I still compliment them on a great product.
Click to expand...
Hi @RobertV14 , Thank you for the feedback we certainly understand your concern. In future if you are experiencing any issues with Parallels Desktop 14 please share us a technical report ID by following steps in this article so that we can investigate the issue with our team to give you a correct solution.
 
You must log in or register to reply here.
Back
Top