Windows is stuck on the logging off screen everytime I try to run parallels

I am running parallels desktop 9 on yosemite. I have quit parallels in the activity monitor and rebooted my computer multiple times. Everytime I try to start parallels it is stuck on the logging off screen within windows. I am using windows 7. I know its old but I only use windows for one application and I dont care.

 

@2nice79, please try to start Windows with Selective startup:

1. Click on Start -> type "msconfig" in the search field and press the Enter key.
2. In the General tab -> Select "Selective startup"
3. In the "System configuration" window go to "Startup" tab and uncheck all applications, except 'parallels'-word contained then click "Apply".
4. After the previous step, open the "Services" tab and enable the option "Hide all Microsoft services" -> and then disable all the non-microsoft services, except 'parallels'-word contained.
4. Click on "Apply" and "OK" -> restart your virtual machine and check the issue.

 

My Windows 7 VM also hangs up on the "Shutting Down" and "Configuring" screens every time I either restart or shut down Windows I had to use the Parallels VM "Stop" action to shut Windows down. This always results in a startup boot-up screen the next time the Windows VM is started. I have kept us with all of the important and most all of the optional Windows 7 updates.

I applied the changes you suggested above and the VM did a restart when requested.

When I tried to do a "Shut Down" using the Windows Start button, the VM still hangs up for over 10 minutes in the "Shutting Down" page, and eventually shuts down. Is this a separate issue from a restart?

How do I find out which of the "Selective Startup" and/or "Services" is causing this issue? I am on Parallels 10 and do not recall having this problem on earlier versions, but I have also added programs since V10. I do not recall if the problem happened coincident with V10 or after.

What info and/or screenshots do you need to point me in the right direction toward a solution?

 

@icarus51 thank you for the reply and additional information.
Please generate problem report using this article and reply us back with the 8-digit report ID number