Fix: Windows Could Not Connect To The System Event Notification Service

Several customers have reported receiving the Windows Could Not Connect to the System Event Notification Service issue when attempting to connect to their Windows PCs. The problem is most commonly seen in Windows Vista and Windows 7. This article explores the error Windows could not connect to the system event notification service in detail along with the fixes.

Also, you can click here to check out what to do when Windows 10 is very slow and unresponsive.

Table of Contents

What Causes The Error Message?

We investigated this problem after reviewing several user reports. Various probable culprits can produce this error message based on what they reported and the measures they employed to fix the issue:

Corrupt SENS Service

This is known to occur on older Windows versions (Windows 7, Vista, XP) due to poor shutdown procedures.

Windows cannot connect to the SENS local server if the service damages.

An Issue With A Windows Update (KB2952664)

The problem appears due to a Windows update (KB2952664), which has the potential to damage the SEN’s component on Windows 7 and Windows Vista.

Several customers have been successful in resolving the problem by deleting it.

The Windows Font Cache Service Is Broken

This is a well-known Windows 7 bug. Because many other services use the Font Cache Service, disabling it might lead to some issues. In this situation, simply restarting the service should cure the problem.

Disabling DHCP Client Service

Windows will be unable to register and update IP addresses and DNS records if the DHCP client service is disabled.

This interferes with the operation of the SENS service.

4 Methods to Fix The Error

Other users have found the procedures listed below to help resolve the issue. You may not need to try all of them; work your way down the list until you find one that meets your requirements.

Check Your Computer’s SENS Settings

The cause of the problem can be a misconfigured System Event Notification Service (SENS).

To change the setting, follow these steps:

Hold the Windows logo key and R on your keyboard to open the Run box.
Type services.msc and hit Enter in the run box.
Select Restart from the context menu of the System Event Notification Service. Click Start instead of Restart if Restart is grey.
Right-click System Event Notification Service and choose Properties this time.
Select Automatic as the Startup type. Then click OK > Apply.

Check to check if the error resolves by restarting your computer. If the difficulty persists, you can try a new strategy.

Update Symantec Endpoint Protection

If you’re using Symantec Endpoint Protection, you should upgrade to the current version of the client. Several Symantec Endpoint Protection users who were experiencing this issue stated that the problem was addressed once they upgraded to the newest build or reloaded the client.

Whether this scenario applies to you, try uninstalling Symantec Endpoint Protection to see if the problem message disappears. If it does, try installing the most recent version or reinstalling the most recent build to see if the problem resolves. This could be the reason for the error- Windows Could Not Connect to the System Event Notification Service.

Check Out: How To Update Minecraft On Windows 10

Use An Elevated Command Prompt

If the problem is due to a poor Windows update or an improper machine shutdown, modification of two registry keys is causing the problem.

Several users who were having trouble resolving the same problem were able to repair it by resetting a couple of registry keys to their default settings. We’ll show you a batch file that will make these modifications for you automatically if you execute it from an elevated Command prompt.

Note: only Windows 7 confirms to operate with this strategy.

This is what you must do:

1. Press the Windows key + R, which will open the Run dialogue box. To open an elevated Command Prompt, type “cmd” and hit Ctrl + Shift + Enter. To grant administrator privileges, click Yes when requested by the UAC (User Account Control).
2. To restore the registry keys to their default values, paste the following command into the elevated Command Prompt and hit Enter:

REG ADD “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows” /v LoadAppInit_DLLs /t REG_DWORD /d 00000000 /f

REG ADD “HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows” /v LoadAppInit_DLLs /t REG_DWORD /d 00000000 /f

3. Restart your machine after the process is complete to determine if the problem resolves.

Check Out: Antimalware Services Executable Error | Unique Fixes

Restart The Windows Font Cache Service

Several customers have reported that restarting the Windows Font Cache Service fixed the problem. Users suspect that because this service interacts directly with the SENS service, it crashes or remains in a limbo state, causing widespread system instability. The SENS service will also undergo an impact.

Restarting the Windows Font Cache Service usually solves the problem. The following is a step-by-step guide on how to do it:

To launch the Run dialogue box, press the Windows key + R. To open the Services panel type “services.msc” and press Enter.
Scroll down the Local list of services in the services panel until you find the Windows Font Cache service. Double-click it after you see it to expand the menu options.
Select the General tab in the Windows Font Cache Service Properties. Wait a few seconds after pressing the Stop button, and if the Service status is set to Running.
To re-enable the service, press the Start button and wait for the procedure to finish.
Retry using the SENS service to see if it’s still available.

Conclusion

The error Windows Could Not Connect to the System Event Notification Service is problematic as we do not have a clear picture of what to do to fix this error. But I hope you know what to do now, don’t you? Fix all your errors right away.

Tony Polanco

Tony, computing writer at Automaticable, covers laptops, tablets, Windows, iOS. Off-duty, he indulges in comics, gaming, speculative fiction, and excessive Twitter use. Non-nerdy side includes rocking out at concerts and hitting NYC bars.