Windows 10 won't start after 13.10 upgrade

Discussion in 'Installation and Configuration' started by AlexZ1, Oct 11, 2017.

  1. AlexZ1

    AlexZ1 Bit Poster

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

    Alfena@Parallels Kilo Poster

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

    AlexZ1 Bit Poster

    Messages:
    10
    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.
     
  4. Brano

    Brano Bit Poster

    Messages:
    1
    I am facing the same issue. Have you found any solution?
    Thanks.
     
  5. JohnF13

    JohnF13 Bit Poster

    Messages:
    24
    Disable Parallel's "nested virtualization" and/or rollback to Parallels 13.0
     
  6. PaulChris@Parallels

    PaulChris@Parallels Product Expert Parallels Support

    Messages:
    3,141
    Hi @Brano, are you able to boot your virtual machine into the safe mode?
     
  7. dennyf1

    dennyf1 Bit Poster

    Messages:
    1
  8. MarceloL4

    MarceloL4 Bit Poster

    Messages:
    4
    That article takes you to a picture...doesn't display an article. :(
     
  9. PaulChris@Parallels

    PaulChris@Parallels Product Expert Parallels Support

    Messages:
    3,141
    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.
     
  10. MarceloL4

    MarceloL4 Bit Poster

    Messages:
    4
    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....
     

Share This Page