Answered by:

Could not connect to System Event Notification Service

Question

I get the error: Windows could not connect to the System Event Notification Service service.

Regular users are unable to log on to the machine but Administrators are. The Event Viewer does not have any useful information. I performed a system restore to a previously working day but the error came back eventually. I have ran the command netsh winsock
reset many times to no avail. When I log in to the machine as Admin I can see that the service is started and it is set to Automatic yet the error persists. This has occurred on 2 Dell machines of different models. I had to completely reinstall the first one
to get the user back working but this is not really a solution.

Answers

I reinstalled Symantec Endpoint Protection from the computer and it now appears to be working. But I am skeptical and intend to keep a close eye. If anyone has any experience with this feel free to still chime in.

All replies

I reinstalled Symantec Endpoint Protection from the computer and it now appears to be working. But I am skeptical and intend to keep a close eye. If anyone has any experience with this feel free to still chime in.

Method 1: Perform a clean boot.
A clean boot helps to verify if any third party application service or startup item is causing this issue. For your information, please review this KB article to put the computer in clean boot:

I was having this issue in Win 8.1. The mention of the font cache made me realize that I had CCleaner running at startup and the tick box for cleaning the font cache was checked. I removed it and the problem has disappeared.

My network connection suddenly stopped working on windows 7. I could see is connected and enabled however red cross on the connection. The network has been set up as DHCP. After running above command and restarting the PC it started working. Thank you

I know this is an old thread, but we have a user facing this same problem.

Only an admin level account can sign in. Limited user accounts can not. To get this user on we need to sign on with admin account, run netsh winsock reset, log off and they can log on. However that is only good for one logon. EVERY
SINGLE TIME the computer is rebooted, an admin account MUST be logged on first, the command run, and then limited user accounts can run.

I'd almost want to set it as a logoff script in local computer policy, however it needs to run as an admin so when the limited user shuts down it wont run (nor would it run on improper shutdowns). We are not sure what to do, besides tell them to NEVER shut
down (only do sleep or hibernate). It is a laptop if that matters.