I left this forum last autumn ( fall) when there were a lot of loud complaints about the Parallels 3 updater. I stuck with my version 5608 because it worked and I didn't want to get involved with what seemed like a slow company response. Parallels has dutifully invited me to update every so often and I have declined. Today, for the first time in months, I though I'd risk it and chose to update to 5626. Result: Parallels froze, followed by the rest of my mac. peter
> Were you able to upgrade to 5626? Did Mac restart help? Mac restart helped me to get back to a peaceful life, Parallels build 5608 included. Completely freezing my mac is a serious assault on my peace of mind and so I did not try again ( I tried back before xmas with the same result). I have decided to steer clear of parallels updates and upgrades for a few more months in the hope that you will produce an updater that will behave like all the other updaters. For example, I upgraded Techtool Pro ( major upgrade) and Cyberduck (minor update) today and I hardly noticed. Is there something intrinsic to emulators that Parallels bites me every time I try to upgrade it? Or is it something to do with the robustness of your code? peter
Hello peterlemer, Please try to uninstall Parallels Desktop old build according the article: http://kb.parallels.com/en/4790 and after that please download the Parallels Desktop 5626. Please note uninstallation/reinstallation doe not effect on Virtual Machine
The default update didn't work. I am not interested in workarounds. This is not the first time I've had to nurse Parallels into performing as advertised. When I reach the point of being unable to run the present version I will either play your game of fiddling about or will switch platforms. I simply don't have the time to beta test this software. peter
