Computer Problems After Last Upgrade: Is it time for roll back?

Last week I downloaded and install my most recent updates for W7. After that everything went fine until I tried to log on the next day and got this:

Windows could not connect to the System Event Notification Service service
Please consult your system administrator

Underneath that, I get a red X to click but when I do I get a W7 background devoid of any icons or promps and no keys work. Not even my power button works. All I can do is pull the plug and reboot. So far, the reboot always works and after that everything functions again as normal. Is it time for roll back? Or are there other options?

 

There go two possible solutions:

-- Press Windows Key + R, type in services.msc, press Enter.

-- On the "Services" window, check the statuses of "System Event Notification Service", "Remote Procedure Call" and "COM+ Event System Service", set any or all of them to Automatic if they already are not.

-- Reboot your computer.

If this does not work, follow the instructions below after restarting:

-- Open the Start Menu, go to All Programs then Accesories.

-- Right-Click on Command Prompt, click "Run as administrator".

-- On the Command Prompt, input:

Code:

cd C:\Windows\System32\

-- Once there, input:

Code:

netsh

-- After this, the prompt will change to "netsh", input:

Code:

winsock reset

-- Close the Command Prompt.

-- Restart your computer.

Credit for the second solution goes to the creator of this article at TechMalaya.

These solutions may not work, if they do not work for you, then rollback will probably be the most viable solution, this error message has many possible causes.

 

Interesting. I noticed Windows defender would not update after the last defender patch. Rolled back, then let it apply again. Killed defender again. Rolled back and now waiting to see if a new update comes out. Definitions update fine, but the core dies when I patch with the last Defender update.

 

Okay, thanks. I've already done solution one and so far the results don't look promising. The reboot was sluggish and my wireless seemed to hang forever before it engaged. In any event, I'll have to give it time before my final judgment on whether the first solution was successful--since the initial problem didn't show up until the next day.

 

Anytime.

While reading through sites about your problem, I noticed the sluggish rebooting and the wireless hanging forever issues, it seems that this problem is indeed becoming more widespread.

Okay, I will be around to read the updates on your situation.

 

Okay, just reboot from overnight and no issues were apparent. I'll try another reboot from a shut down shortly and keep my fingers crossed. For the moment, solution 1 is holding.

EDIT: Day 2 and the problem has returned. Instituting solution 2 today. Stay tuned!