Thank you for this! I have McAfee so I will attempt to fix this now. The only problem is that after repeated restarts on my PC, it has now rendered all of my services unstartable.

I went into Safe Mode and tried to run Malwarebytes and Mcafee. I get an error messages trying to run Mal, and McAfee won't start at all.

I tried doing a system restore, but it keeps telling me the PC isn't protected and to restart and try again. This doesn't work. I have gone to last known good config, but this just brings me back to the 'not right' version of my XP desktop that I had after the many reboots (didn't read this article until after several).So, I'm not sure how I can do this fix when I can't even open McAfee grrrr.

Virtualbox-iso: A system shutdown is in progress.(1115) virtualbox-iso: A system shutdown is in progress.(1115) virtualbox-iso: A system shutdown is in progress.(1115) virtualbox-iso: The interface is unknown.(1717) virtualbox-iso: /bin/sh: Read-only file system virtualbox-iso: Machine successfully restarted, moving on.

I had the exact same thing as JM and followed your instructions as well as those by the removal tool with the result of the worm not being found.Something that may help in troubleshooting the issue is that my computer has not done the automated shutdown as previously described in postings. This could be due to the removal tool instructions of disconnecting from the network and shutting off the System Restore.

I strongly believe it is the System RestoreThe reason for my theory is due to the fact that the first time I tried running the removal tool, I did not perform those steps before running and the shutdown occurred while the tool was running. Finally, I have restored my network connection with no shutdown occurring.Any other suggestions? My 11-year old daughter had the same problem. After reading online, I'd tried a number of the 'solutions' to no avail. We also downloaded used Antimalware and SystemCare, ran scans, still the message about shutdown was appearing regularly. Then it occurred to me to ask her if she remembered when it started to happen, and she said that it was right after we'd downloaded and installed AVG. I uninstalled AVG and selected the option to removed Quarantined items (the program calls it something else, not Quarantined, but I can't remember the term they use).

Several days later now, and the problem has not repeated itself. Hulu an evil plot to destroy the world case analysis. I never used the shutdown -a solution, although I suppose that command would stop a shutdown. I'm no expert, but cause-effect tells me this could actually be a problem with AVG's download and software. Hope it helps someone else!

Question:Executing remote (Sysinternals) command.pskill machine winlogon.can budge a server that is stuck rebooting, but how/why does this work? How do you know which service to kill?To recreate (e.g.):You run Windows Update, allow a reboot, and.NOTHING! RDP gets cut off but the server does not reboot.

Just about every other service seems to stay up.Further Background:I've faced this problem on VMs hosted around the planet for some years, and used various sc.exe and shutdown commands to learn the state of and attempt remote reboot of servers in such a state, with limited success. Most datacentres don't offer any way to see the true console or power off/on such machines. What's happening is that the WinLogon service, the service that handles the logged in environment for RDP and local logins, is getting hung on shutdown for some reason. Could be some weird locking is going on that's preventing something critical from shutting down, or maybe the registry is still open somewhere. When you kill the winlogon service, it breaks the logjam so the reboot can move apace.This will leave Event Log traces! In the Application Log, right before the reboot there will probably be some events describing why the machine couldn't go down just then.The reason shutdown /m machine /r /f /t: 0 fails on you with that particular error message is that if the reboot has progressed past a certain point, it'll reject further reboot requests.

The pskill method works because it isn't asking the machine to reboot, it's just knocking loose the process that's gumming up the reboot-in-progress.