Need some help figuring out why Windows virtual will not install version 1709. Everything appears to install fine, but then when Windows reboots, it starts up, looks like it's trying to go to the new version, but then soon says "Stopping". I get a Parallels pop-up that says I can send in the error report. Then I boot up the virtual again and it starts up without the update applied. A few seconds after reboot, it starts trying to install update 1709 again, and process starts all over. I can't seem to stop or defer the update, as my admin must be forcing it to install. I've sent this error into support multiple times. I've also sent them an email to support. Please need help...!
Same here. I love how it says "go about your business, ignore me" but if you walk away, it gives you 30 minutes before it forces a reboot. It should prompt and wait. So, don't leave any files open.
Hi @zjgolf44 , please try resetting the virtual machine by clicking Actions > Reset and check if that works.
Hi, I have the same problem - but only with one VM - another one was updated to 1709 without any problems. I just now try to investigate what the difference is between both VMs - some services or apps or whatever. Hope for some good news to be publsihed soon. Dirk
Hello Dirk, I also have 2 VMs, one of which updated fine. However this does not help if I am stuck to a non-protected Windows 10 VM running a MySQL server that's fairly important for my company. All the best Andreas (...still frustrated and starting to get really annoyed...)
It appears that Parallels does not care to help us. It has been more than a month since their reply. Hopefully Dirk will have some info for us.
Hi @ChetanK , please try to perform SFC scan and check disk on your Windows virtual machine and check if there are any hard disk errors. Once it is done, reboot your Windows virtual machine and check if that fixes the issue.
Maybe the VM was 32bit Windows? I had similar problem in a real PC with Windows 10 32bit. The update didn't install well, at reboot the PC apparently was broken, but it was really ok, operating with the Windows' tools to try to get the boot working the system canceled the upgrade, restarted, but installing the update there was the same problem... I solved upgrading the PC to Windows 64bit with the Microsoft Update program (not free)... Maybe the "Fall update" is not compatible, at the moment, with 32bit systems, and I hope Microsoft could solve the problem soon. I don't know if for the Virtual Machine it is the same, however... Salvo
@Arun@Parallels Performed the SFC scan. No errors were found. The issue remains. When the Windows VM reboots after installing update for Windows 10 1709, Parallels crashes and the update in not successful.
Got the same problem. Windows started yelling at me that I have to upgrade. While upgrading, Parallels warned me that it rejected MBR change which was executed by the updater. After this the updater reverted the update. How do I properly update Windows now?
ValentinS1, do you have bootcamp based VM? I would suggest to boot into bootcamp and update windows, return to OS X and unregister your bootcamp VM and recreate it again. This will update bootloader code used by Parallels in case of bootcamp VM.
I have this issue too, have tried many fixes using cmd commands, nothing works and 1709 update does not install, vm crashes. I suspect the only answer will be to update from v10 to v13.
I have Parallels 12 and am having the same problem. Everything looks like the update is working, but then it is ineffectual. Microsoft is notifying me that 1607 is EOL this month.
This seems to be a Mac / Windows problem and not related to Parallels. Search for "BootCamp 1709" on the Internet to find more about this.
