Upgraded to V13 and have error message when Parallels starts

N

nickbirkett

Bit poster
I upgraded to V13 yesterday. Now, every time I start or stop my Parallels, I get a pop up error message (see screen shot) claiming that tools can not be installed until I restart. I restart Windows several times and also restarted the computer but the error keeps coming. A Google search wasn't helpful.
Thoughts? Solutions?Screen Shot 2018-03-05 at 9.28.53 PM.png
 
nickbirkett said:
I upgraded to V13 yesterday. Now, every time I start or stop my Parallels, I get a pop up error message (see screen shot) claiming that tools can not be installed until I restart. I restart Windows several times and also restarted the computer but the error keeps coming. A Google search wasn't helpful.
Thoughts? Solutions?View attachment 13722
Click to expand...
Create a new empty virtual machine and copy the HDD file to it then check the results. You can refer to the article for creating empty VM and copy the HDD file instead of "drag and drop".
 
Interesting suggestion. The creation is quite complex process. I'll give it a try tomorrow (I have meetings tonight).
A question: can you change the VM 'type'? I have Windows 10 on the VM. But, when I went through the first few steps of the process to create a new VM, I discovered that the VM type is still listed as Windows 8 (I replaced the actual OS with Windows 10 about 2 years ago).
 
Thank you for your advice. I followed the essence of your suggestion: created a new VM on another drive, copied the HDD from my current and then did some tidy-up configuration. The newly created VM is working fine. I deleted the bad copy.
However, the instructions in the Knowledge Ware link weren't really that helpful. Some of the screens didn't match what I saw, the HDD in the package couldn't be accessed (the 'open' button wasn't active) but when I went one more level down, the HDD had '0 bytes' and when I copied to the new VM, it wouldn't boot.
But, I am now working smoothly. The help is appreciated.
 
nickbirkett said:
Thank you for your advice. I followed the essence of your suggestion: created a new VM on another drive, copied the HDD from my current and then did some tidy-up configuration. The newly created VM is working fine. I deleted the bad copy.
However, the instructions in the Knowledge Ware link weren't really that helpful. Some of the screens didn't match what I saw, the HDD in the package couldn't be accessed (the 'open' button wasn't active) but when I went one more level down, the HDD had '0 bytes' and when I copied to the new VM, it wouldn't boot.
But, I am now working smoothly. The help is appreciated.
Click to expand...
We are glad that the issue is resolved. Feel free to reach out.
 
You must log in or register to reply here.
Back
Top