Parallels Error after updating from 11828 to 11990

Discussion in 'Windows Virtual Machine' started by JuergenB, Dec 7, 2010.

  1. Schr

    Schr Junior Member

    Messages:
    15
    I was actually able to revert to build 11828 after uninstalling Parallels. It's only been a few hours now, but everything now appears to be fixed. I'll let you guys know if I notice anything amiss.
     
  2. phimon48qb

    phimon48qb Bit poster

    Messages:
    1
    Had the same problem. I restored a VM file from TimeMachine, removed Kaspersky AV and so far I only get random sound loss and network failures if I try to create a VPN Connection.

    I guess you really can't fake what you don't have. I've been at this a long time with P4, P5, and P6. Brand new iMac Quad core. Runs like the wind and XP runs well BUT I have yet not to have a problem with it every few days. The latest upgrade is a disaster.
     
  3. Hans Balen

    Hans Balen Member

    Messages:
    64
  4. jscheller

    jscheller Bit poster

    Messages:
    1
    Ditto for me. Continuous problems with three separate VMs running Windows XP. I made backups before the parallels upgrade (got bitten before). Tried restoring these multiple times, going through the Parallels Tools install. I've spent more time backing up and restoring VM's in the last week than doing any productive work.

    One of the older VMs simply says it's corrupt and won't open no matter what I do. Thankfully I can use the mounter to still get to the files from the finder. Two of the VM's are clean XP builds I did in early January, so it's not like these are crufty old VMs with tons of legacy junk floating around. No virus software or anything that would tweak the Tools install on either of those.

    The others complain about the audio controller not being able to be installed when Parallels Tools installs and updates, but if I boot the VM into safe mode, then run the installer it seems to work except various apps (notably Microsoft Visual Studio) choke and die as soon as they launch, and then subsequently the VM's won't boot.

    Will try to track down a 11828 installer somewhere to roll back now and see if I can duplicate some of the success other members here have had.

    Agree whole-heartedly with others observing that 11990 is whacked and should be avoided...
     

Share This Page