Starting Win7 hangs at 60 (%)

Discussion in 'Windows Virtual Machine' started by Th.S, Sep 21, 2011.

  1. Th.S

    Th.S Bit poster

    Messages:
    2
    we use a MacBook Pro with 8 GB RAM and a MacBookAir 2 GB RAM both with Max OSX 10.6.8 and a Win7 guest, 32-bit.
    During start/booting Windows, they often "hangs" at the counter 60 (=60%).
    I didn´t find any reason for it.

    Does anybody know what´s going on there and/ore how to debug/fix it ?
     
  2. Is it possible it is looking for something that was not disconnected properly? Such as a external drive? You could look at Windows error logs to get some ideal possibly of what could the problem. A driver error could be a problem too. Have you tried reinstalling Parallels tools? I have read others who had issues that were solved by reinstalling tools. I have a Macbook Air with 2Gb myself running Win 7 32 Bit with no boot issues. I do have a 10.7 Lion though which is different.
     
  3. MGhostSoft

    MGhostSoft Junior Member

    Messages:
    15
    If you are using Parallels 6 and recovering from a suspended VM, then please be patient. When you started it, it will go to 60% quickly, and then stay there for 1~3 minutes. When you open Activity Monitor, you will see that the Data read/sec on disk is pretty high. After that, your VM will be recovered.

    When I first use Parallels 6, I thought it would never gonna response too.
     
  4. Th.S

    Th.S Bit poster

    Messages:
    2
    @MGhostSoft,

    you described exactly my problem.

    ... but what is the reason for it ?

    after
    !?!
     
  5. MGhostSoft

    MGhostSoft Junior Member

    Messages:
    15
    I guess the reason might be Parallels 6 fails to estimate an accurate process for it. But in most cases it will finally boot up. Parallels 7 fixed this problem - the process from 0% to 100% goes smoothly.
     
  6. I will explain

    So when Windows goes into suspend. It stores data of previous session. When you come out of suspend it reads that data to restore your last session. Its suppose to work faster then booting but I tend to think not in your case. Maybe something is corrupt. Try shutting down or doing a restart even try to do a file check on next reboot by going into your drive tools in Windows and select check disk it will tell you that it will perform this on next reboot.
     

Share This Page