Fixing “Windows could not connect to the System Event Notification Service” Error in Windows 10
Could not connect to the System Event explanation: Although logging into a Windows 10 computer may seem like a simple process, it’s actually not since the Windows operating system has built a mechanism in a way that any third party or malware intervention would not compromise access to the system. This mechanism is supported by numerous services, functions, and DLL files. And Microsoft has been taking this security to a whole new level with the introduction of Windows Hello.
Recently, a number of users reported getting the “Windows could not connect to the System Event Notification Service service. Please consult your system administrator” error when logging into their computers. While some users also reported that although they can log in, they encounter the same error message from the Notification area. There are several options you can check out to resolve the error. You have to check the status of several Windows Services and make sure that they are running. You also have to reset Winsock as well as run the System File Checker scan.
Option 1 – Check for certain Windows Services
- First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
- Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
- After that, you will see a list of services and from there, look for the following Windows Services:
- DHCP Client
- System Event Notification Service
- Windows Font Cache Service
- Now make sure that the Startup Type of each service is started and running.
Option 2 – Try resetting the Winsock drivers
- In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
- After opening Command Prompt, execute this command: netsh winsock reset
Note: If you are using IPv4, execute the “netsh int ipv4 reset” instead. On the other hand, if you are using IPv6, execute the “netsh int ipv6 reset”
- Now exit Command Prompt and see if the error is now fixed.
Option 3 – Try running System File Checker or SFC scan
You could also run System File Checker or SFC scan to fix the BSOD error. It is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.
- Tap Win + R to launch Run.
- Type in cmd in the field and tap Enter.
- After opening Command Prompt, type in sfc /scannow
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
- Windows Resource Protection did not find any integrity violations.
- Windows Resource Protection found corrupt files and successfully repaired them.
- Windows Resource Protection found corrupt files but was unable to fix some of them.
- Reboot your PC.
Congratulations, you have just fixed the Could not connect to the System Event error in Windows 10 all by yourself. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.
Now that’s how you fix the Could not connect to the System Event error in Windows 10 on a computer. On the other hand, if your computer is going through some system-related issues that have to get fixed, there is a one-click solution known as Restoro you could check out to resolve them.
This program is a useful tool that could repair corrupted registries and optimize your PC’s overall performance. Aside from that, it also cleans out your computer for any junk or corrupted files that help you eliminate any unwanted files from your system. This is basically a solution that’s within your grasp with just a click. It’s easy to use as it is user-friendly. For a complete set of instructions in downloading and using it, refer to the steps below
Perform a full system scan using Restoro. To do so, follow the instructions below.