Nice of you to have put an incomplete fix in the other thread and then locked it. I had rebooted my machine a dozen times trying to resolve things before I figured out what is going on. Reboots do NOT fix the problem.
The problem is that many of us couldn't do anything when the service was running amok. The systems wouldn't run well enough before crashing to get a browser up.
The solution is to disable the service (you can run the command "services.exe"). You may need to bring the system up in safe mode to throttle the misbehavior (it seems to still run amok in safe mode, b