Parallels Wizard Freezes

Discussion in 'Installation and Configuration of Parallels Desktop' started by TBayIT, Mar 2, 2014.

  1. TBayIT

    TBayIT Bit poster

    Messages:
    3
    I just upgraded to Parallels 9 from 8 (on latest version of Mavericks). All my VMs are working fine but when I go to the Parallels Wizard to add a new VM as soon as I click on anything I get the spinning disk and it is unresponsive - making it impossible to add a new VM or import any old ones. Have to use 'Force Quit' to stop it.
     
  2. Manojkumar@Parallels

    Manojkumar@Parallels Parallels Support

    Messages:
    122
    Hi TbayIT,

    Please try to reinstall Parallels Desktop and see if it helps:
    * uninstall with http://kb.parallels.com/116992
    * reinstall from http://www.parallels.com/directdownload/pd9

    Thanks,
    Manoj
     
  3. TBayIT

    TBayIT Bit poster

    Messages:
    3
    This didn't work, the entire window that comes up when I go to File -> New locks up like this even after reinstalling. I can still use my existing VMs with no problems but I would like to install some new ones. Not sure what to do.
     
  4. Maheesh@Parallels

    Maheesh@Parallels Parallels Support Parallels Support

    Messages:
    377
    Hi TBayIT,

    Please uninstall Parallels Desktop 9 completely from your Mac by following the steps as given below :

    Launch Terminal application from Applications/Utilities

    Paste the commands into Terminal (one by one; hit return after pasting each command)

    sudo –s

    (type your Mac user password (your Mac user should have Administrator's privileges) and hit return. You will not see characters while typing)

    killall -KILL prl_vm_app


    killall -KILL prl_client_app


    killall -KILL prl_disp_service


    kill -KILL `ps -A -opid,command | fgrep '/bin/bash /Applications/Parallels Desktop.app/Contents/MacOS/watchdog' | awk '{print $1}'`


    ps -A -opid,comm | fgrep '/Applications/Parallels Desktop.app/Contents/MacOS' | awk '{print $1}' | while read pid; do kill -KILL $pid; done


    kextunload -b com.parallels.kext.netbridge


    kextstat | fgrep 'com.parallels.' | fgrep -v 'com.parallels.virtualsound' | awk '{print $6}' | while read i; do kextunload -b $i; done


    rm -rf /System/Library/Extensions/prl*


    rm -rf '/Applications/Parallels Desktop.app'


    Then re-download Parallels Desktop 9 from : www.parallels.com/directdownload/pd9

    Install Parallels Desktop 9 from the downloaded link and then check if you are able to create a new Virtual Machine.

    Thanks,
    Maheeshwar
     
  5. TBayIT

    TBayIT Bit poster

    Messages:
    3
    Unfortunately this still didn't work, the Wizard keeps locking up.

    Interesting, I also tried to install version 8 and the Wizard works fine so it is an issue with 9. I suppose if I had to I could install version 8, then setup my new VMs then upgrade back to 9.
     
    Last edited: Apr 8, 2014
  6. Maheesh@Parallels

    Maheesh@Parallels Parallels Support Parallels Support

    Messages:
    377
    Hello TBayIT,

    Please check your private message.

    Thanks,
    Maheeshwar
     
  7. EtienneB

    EtienneB Bit poster

    Messages:
    3
    I have got the same problem. I got the ever spinning ball went I want to create a new machine and the wizards comes forward.
    I followed through all steps listed above. But that didn't help.
    Thanks for a solution.
    Etienne
     
  8. Abdul@Parallels

    Abdul@Parallels Parallels Support

    Messages:
    553
    Hi Etienne,

    Please generate a Problem Report ID as suggested at http://kb.parallels.com/9058 and reply us the Problem Report ID.
     
  9. EtienneB

    EtienneB Bit poster

    Messages:
    3
    Only the alternative method worked, as the main programme stopped responding as soon as I click "Install windows or ...."
    The code is: 43164206

    Best,
    Etienne
     
  10. EtienneB

    EtienneB Bit poster

    Messages:
    3
    I noticed that it works again. The only thing I did was create a new VM by deploying a template. And now it also works again with starting from scratch. Somehow the template deployment fixed something.
     

Share This Page