Solved Windows could not connect to the system event notification service

Hi i have a couple of users on our network who are receiving the following error on startup "Windows could not connect to the system event notification service service. Please contact your system administrator" When this error is receive i always notice the startup time take an extra 2-4 minutes before it even gets to the login screen. Once logged in the users gets the error after a minute it can automatically go back to the login screen or if you press OK it also goes back. On second attempt it will log in with no errors.

So far form everything i have researched and tried nothing seem to fix the issue. This is what i have checked and done. Oh and these 3 machines that are getting this error are on Windows 7. We get no event viewer message or error about the issue.

-Made sure the services are running and started and set to automatic - mainly the Windows Event log, COM+ etc everything is started as it should be
-Rebuild WMI repository (which did fix issue for a 3 days then returned)
-Netsh catalogue reset and winsock reset
-Tried Hotfix - KB2590550
-Made sure network drivers were updated and the latest
-SFC /scannow
-HDD healthcheck done - is OK


Anything anyone else can suggest would be great or if someone has been able to fix this issue permanantly please let me know???


Thanks

Steve

Have you tried this: Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2 ?

Hi writhziden, that kb fix did not resolve the issue. Any more ideas anyone???

I would reckon the syslog/applog won't show up anything if the very service that logs fails to run. Have you checked the dependencies for it (COM+ Event System as one)? Go to Services list and go to Properties for the service and it'll have a Dependencies tab.

A couple more questions: When you ran SFC /scannow, did the log say anything? Also, does your network deploy any startup scripts for workstations?

You could run a couple Procmon boot logs, one to record a boot where it presents the error message and the failed login, and one that experiences a successful login. When you open up Procmon, go to Options then select Boot Logging. It'll prompt stating it's ready to log activity during next boot. You may wanna also go ahead and check the Generate profiling events option. Restart and it'll start logging as soon as Windows starts. It will not stop until the system shuts down again for whatever reason, or until you manually open up Procmon again. Save with All events for each log once you open Procmon up at the earliest chance.

Note that these logs will be big. You will have to archive em and upload them to a third party filesharing site.

Hey everyone,

My computer recently suffered this issue as well, but thankfully came across this other forum with the solution 'Failed to connect to a windows service' problem? - TechSpot OpenBoards Fixed my problem right away, so kudos to 'Mark' who posted this solution

'Try this...

Start computer in safe mode.

logon on to administrator.

Click the start button

Search "cmd.exe"

Select it and then "ctrl - shift - enter" to allow elevation request

Type in - "netsh winsock reset" press enter

Then Restart your computer'


Elva

As stated above i have tried this and for most people this isnt a fix the issue will return.

Hi,

Are you able to post any updates or answer any of the questions I asked in my previous post? Thanks.

yes all dependence are started its sort of like it just taking a while to start as by the time you look everything that should be started and running is.

When i ran the SFC /Scannow it came back with something about did not find any integrity violations from memory the standard message when it doesnt error.

I did run the boot logging on a successfully and errored login but then was told not a good idea to post them to the world.

Just today i uninstalled Forefront Client Security and i dont receive the error. i have tired delaying the service that runs FCS but this hasnt changed anything. We cant really uninstall this for all users so are looking into why this is happening now.....

You're right about the procmon logs. I apologize. I didn't bother to think it through we're dealing with a business environment here.

EDIT: realized you already tried that hotfix. My bad.

DOUBLE EDIT: Ugh, I forgot Forefront was Microsoft-based. Just ignore everything I say.

Yer thats ok it took a while to look through them but it got us looking into the Forefront Client anyways so thanks. Getting close now

found this which is a very simalar issue - Black screen at start up \ boot up - LONG boot times

this resolve my issue - Login Issues/Slow Boot caused by Forefront

Thanks very much for the update. I knew there had to be a bug involved but the most prominent hotfixes didn't seem to do the trick. Glad to see someone pointed you to the correct one.

The bug looks like it dealt with Forefront attempting aggressively to scan networked files in a manner that was causing login stalling. Obviously the workaround was designed to reduce or even eliminate attempts at doing so.