Auto open and auto exit error Tony-Bologne and BillInSoBe reported a problem back on December 3rd, and I haven't seen anyone post a resolution for it yet, so I'm recapping and adding my observations. The problem is that all my machines are stuck in an auto open/auto exit loop. That means the machine starts automatically whenever I open the .pvs file, and shuts down Parallels automatically whenever it is stopped. This works until you need to admin your virtual hardware or change machine settings. Tony apparently is fast enough to click one of the properties just before his machine actually starts up, but I've tried and I haven't been able to do it. The problem is that this is not a VM-specific error--it's internal to the beta. I've checked all of my .pvs files, and they all appear to have these flags disabled: Start auto = 0 AutoShutdown = 0 In a related issue, whenever I start Parallels from the App icon it immediately launches the new VM wizard. If I stop that process, Parallels shuts down. This can be worked around if I continue through the new VM wizard and then shut it down after it tries to boot. But that's a kludge and pretty user hostile, and still doesn't allow me to edit my existing VMs--it only gets Parallels running in a state that I can view Parallel's preferences, play with the new dummy machine's settings, etc. If you're having this same issue and try this workaround, I recommend choosing a Linux OS so that you avoid the need to enter a Windows product key for what amounts to a temporary VM. The reason I can't edit existing VM's from this point is that the "Open..." option in the File menu doesn't give me a file browser: it starts the new VM wizard again. So I have to open my existing VMs from the file system. To repeat, I never chose the auto start or auto exit options for any of my machines, and they don't appear to have these settings enabled in their settings files--this is an error internal to the Parallels beta. Editing the .pvs files with a text editor does not alter this behavior So if my VM config files aren't set to auto start or auto exit, why are they behaving as if they are, and how can I make it stop?