Icons Proudly American

24/7 Live chat
Cart Cart
0
Cart Cart
0

Fixed: “Windows could not connect to the System Event Notification Service” on Windows 7

Especially after a system update, you need to prepare for seeing new bugs and errors pop up on your screen. However, seeing the “Windows could not connect to the System Event Notification Service” error on Windows 7 can be devastating to deal with. You either aren’t able to log into your account or get bombarded with even more error popups after you manage to.

Let us calm you down a bit: this is not a hardware issue, so don’t go looking for a new computer just yet. Read our article to find out what this error is, what causes it, and how you can resolve it from the comfort of your home within just a few minutes.

Windows 7 professional

Causes of "Windows Could not Connect to the System Event Notification Service" Error?

Just like many other Windows issues, there isn't one definitive cause of this particular error.

Based on user reports and answers from the Microsoft team themselves, we've compiled a list of possible things that trigger the “Windows could not connect to the System Event Notification Service” popup.

  • A Windows update is causing the error. Many users have reported that the KB2952664 update, in particular, seems to break the System Event Notification Service service in Windows 7.
  • The SENS service is corrupted. It’s possible that the System Event Notification Service (SENS) itself is corrupted. You should suspect this if you often shut your computer down incorrectly.
  • The Windows Font Cache Service isn't working properly. In Windows 7, many services depend on the Font Cache Service. If something happens to it, it causes a domino effect and your computer may have issues with the SENS service as a result.
  • The DHCP client service is not running. It may be that your system is currently unable to address and manage IP addresses and DNS records, which leads to the SENS service malfunctioning.
  • Incorrect Winsock Catalog settings. Winsock is an advanced tool, and its settings are important. Users have reported that restoring the Winsock Catalog often helps with SENS errors.
  • Something is interfering with the SENS service. Some antivirus applications offer network and endpoint protection as part of their premium bundles. For example, Symantec Endpoint Protection is known to interfere with the SENS service in Windows 7, often causing errors.
  • Outdated video card drivers. Make sure to keep your drivers updated! An old, outdated driver can cause more issues than you realize.

Failed to connect

How to fix the “Windows could not connect to the System Event Notification Service” error

Now that we’ve taken a look at the causes, it’s time to properly address the error. If you can’t log into your usual user account, logging into an administrator account should give you access to the system. Every system has at least one administrator user, so try and get a hold of the account or its owner.

Now that you’re logged in as an administrator, it’s time to start troubleshooting!

Tip: While our methods were primarily written for Windows 7, this error is known to occur in older systems such as Windows Vista and even Windows XP. If you’re using one of those systems, give our methods a try! They might just do the trick.

Method 1: Restart and automate the System Event Notification Service

The first thing you should try is checking if the problematic service itself is running properly. You can do this by following the next steps.

  1. Press down the Windows + R keys on your keyboard at the same time to launch the Run utility.
  2. Type in “services.msc” and press OK. This will launch the Services window.

Services.msc

   3. Wait for all of your services to load, then locate and select the System Event Notification Service.

System Event Notification Service.

   4. Right-click on System Event Notification Service, then select Restart from the context menu. If Restart is unavailable, click Start instead.

system event notifications

   5. Next, right-click on System Event Notification Service again and choose Properties.

Properties.

   6. Make sure that the Startup type is set to Automatic, then click OK.

Startup type

   7. Restart your computer.

Now, you can test if the error has resolved.

Method 2: Restart and automate the Windows Font Cache Service

If restarting the System Event Notification Service itself didn’t work out, you should immediately follow up by making sure the Windows Font Cache Service is running properly.

    1. Press down the Windows + R keys on your keyboard at the same time to launch the Run utility.
    2. Type in “services.msc” and press OK. This will launch the Services window.

Services.msc

      3. Wait for all of your services to load, then locate and select the Windows Font Cache Service.

System Event Notification Service.

      4. Right-click on Windows Font Cache Service, then select Restart from the context menu. If Restart is unavailable, click Start instead.

      5. Next, right-click on Windows Font Cache Service again and choose Properties.

system event notication

      6. Make sure that the Startup type is set to Automatic, then click OK.

Startup type

      7. Restart your computer.

Attempt to use your accounts to see if the error still exists.

Method 3: Enable the DHCP service

There’s one last service users report having issues with. It’s the DHCP service, which often seems to become disabled for some reason. If you keep running into the same error, you should ensure that it’s running.

  1. Press down the Windows + R keys on your keyboard at the same time to launch the Run utility.
  2. Type in “services.msc” and press OK. This will launch the Services window.

Service

     3. Locate, then double-click on DHCP Client.

DHCP Client.

     4. Make sure you’re on the General tab.

general

     5. Change the Startup type to Automatic.

Automatic

    6. Ensure that the Service status states that the service is currently running. If it isn’t, you can click on the Start button to enable it.

 Service status

   7. Click on the OK button and restart your device.

After your computer boots up, check if you still have issues relating to the System Event Notification Service.

Method 4: Update your antivirus

Many users report that after updating their antivirus client to the latest version, issues with the System Event Notification Service seemed to stop. This is most likely due to the network and endpoint protection some antivirus apps offer.

Most of the time, you can update an antivirus app from its settings tab or a dedicated update tab. Many applications come with automated updates, or reminders to update your software as well.

Norton

Example: Norton Antivirus comes with a LiveUpdate feature.
Source: mnorth1984 from Norton Community

If you’re unsure of how to update your client, visit the suite’s website or look for tutorials online. Because every app is different, it’s impossible to make just one guide.

Method 5: Reset the Winsock Catalog

It’s possible that unintended changes to your Winsock Catalog caused issues with the System Event Notification Service. In this case, the best bet is resetting your Winsock Catalog.

To do this, we’ll be using the Command Prompt. If you’re not experienced with using commands, simply follow our steps and copy-paste any text written in this font. Those are commands, which can be inserted into the Command Prompt.

  1. Press down the Windows + R keys on your keyboard at the same time to launch the Run utility.
  2. Type in “cmd” then press the Ctrl + Shift + Enter keys on your keyboard. This will launch the elevated Command Prompt.

cmd

     3. Input the following command, then press Enter: netsh winsock reset

winsock

     4. Restart your computer and check if the error still exists.

Method 6: Uninstall the Windows KB2952664 Update

As we discussed in the “What causes the “Windows could not connect to the System Event Notification Service” error?” section, one of the most common causes is the KB2952664 update.

Other than the issue with the SENS service, the update was problematic for many users. It may cause significant performance drops when browsing the internet, freezing windows, and even a painfully slow shutdown.

If none of the methods above worked, we recommend that you uninstall this specific update. To do that, simply follow the next steps.

  1. Click on the Windows icon in the bottom left of your screen to open the Start Menu. Now, click on Control Panel.

Windows icon

    2. Change the View by mode to Category.

View by

     3. Under Programs, click on the Uninstall a program link.

Uninstall a program

    4. Click on the View installed updates link at the left side of the window.

View installed updates

    5. Locate the KB2952664 update, then right-click on it and select Uninstall. This will remove the problematic update from your computer.

    6. Restart your device and check if the error still occurs.

We hope that through our guides, you were able to get rid of the “Windows could not connect to the System Event Notification Service” error on Windows 7.

If you’re in need of information about other Microsoft Windows issues, need help with troubleshooting, or want to learn more about your operating system, check out our other articles here.

However, if you’re looking for a software company you can trust for its integrity and honest business practices, look no further than SoftwareKeep. We are a Microsoft Certified Partner and a BBB Accredited Business that cares about bringing our customers a reliable, satisfying experience on the software products they need. We will be with you before, during, and after all the sales.

That’s our 360 Degree SoftwareKeep Guarantee. So, what are you waiting for? Call us Today on +1 877 315 1713 or email sales@softwarekeep.com. As well, you can reach us via Live Chat.

Icons Subscribe now and get a Mystery
Mystery Offer from SoftwareKeep

Cart Cart
0