Windows 10 won't start after 13.10 upgrade

[AlexZ1]

I have updated Parallels Desktop to version 13.10 and now my Windows 10 won't boot - i am stuck looking at 'windows logo'.

 

[Alfena@Parallels]

Hello @AlexZ1 , Please go to Actions > reset and check if it works.
Thanks

 

[AlexZ1]

Alfena@Parallels, of course i have done that. Windows just goes to the 'automatic recovery' after a couple of reboots, that's all. Seems like some driver incompatibility. As i couldn't wait on you guys, i downgraded to 13.0 and it works.

 

[Brano]

I am facing the same issue. Have you found any solution?
Thanks.

 

[JohnF13]

I have updated Parallels Desktop to version 13.10 and now my Windows 10 won't boot - i am stuck looking at 'windows logo'.

Disable Parallel's "nested virtualization" and/or rollback to Parallels 13.0

 

[PaulChristopher@Parallels]

I am facing the same issue. Have you found any solution?
Thanks.

Hi @Brano, are you able to boot your virtual machine into the safe mode?

 

[dennyf1]

Its probably an issue of windows won't boot, which can resolve with either Startup repair option Or using cmd, you better check this article https://youprogrammer.com/windows-10-wont-boot/ for further steps.

 

[MarceloL4]

Its probably an issue of windows won't boot, which can resolve with either Startup repair option Or using cmd, you better check this article https://youprogrammer.com/windows-10-wont-boot/ for further steps.

That article takes you to a picture...doesn't display an article.

 

[PaulChristopher@Parallels]

That article takes you to a picture...doesn't display an article.

Hi @MarceloL4, can you please send us a Technical Data collected (Help menu > Send Technical Data...)? https://kb.parallels.com/116783 This will help us significantly, please reply me back with the report ID number.

 

[MarceloL4]

I already did! The very same day I posted my original post.
I don't remember getting any report ID back....if you want to look for the report....it would've been submitted the date of my original post. That being said....I don't think this issue should've occurred. A space reclamation command that effectively destroys your virtual machine? C'mon....