... I've been fortunate to not have encountered any problems at all so far with any of the Betas that other people have reported about... until now. And actually, I haven't seen anyone report this yet. I just backed up my VM (good thing) and installed the new Beta... Prompted to install new Parallels Tools, so I did so. First thing (video driver) it pops up a display with 3 it has found, two with the same version number that match the new beta build (but the paths to the driver are different, such as /winnt and one in something like /win2000.xp.2003) The third was an older version... The default selected was /winnt, so I left it at that and continued the install (keep in mind I use XP.) It began the normal installation process in windows (showing two folders moving files back and forth.) Froze during this, I waited a few minutes then i got a nice BSOD. Now when I boot, windows begins loading, and then when it switches to goto the login screen it is all black. I'm assuming you can see windows loading because at that point windows is utilizing basic video drivers, at the time it switches to the login screen is when it uses the installed video drivers. I'm imagining that if i restore it with my backed up VM and select the /win2000.xp.2003 driver it will be OK, but ... you shouldnt have it show three options for the drivers, selecting the wrong one by default. And if you are going to, be sure to NOTIFY the people of which to choose (especially if it will not be the default selected value.) Not trying to sound bitter, because I absolutely love this software. I just dont want to see something so silly like this that can cause major problems make it into a release build.
Upon re-instating my saved VM I found out what the problem was... If you just let the VM sit for a few seconds (before installing updated Parallels tools) it will prompt to search for a new Video driver. This happened to happen just after I pressed the "Install Parallels Tools" button, and took focus over that application (which I did not even see run,) and I assumed I was using part of that installation. If this can happen so easily, maybe Parallels should think about hiding the driver files in such a way that the windows automatic configuration cannot locate them.
If you are still having issues with this, consider rebooting into safe mode and installing the tools. I had this issue, and couldn't resolve it until I did that.
