Windows could not connect to the System Event Notification Service service. Please consult your system administrator
Having an issue with Windows 7 computers. We have a windows 2003 domain, and the computers are joined to that domain. I get this error on multiple computers, anything from HP workstation to dell laptop. I have a lenovo laptop with a fresh install of windows 7. no 3rd party apps / drivers installed yet. I can login as a local admin, no issues. I can login as a domain admin, no issues When i login as a user, i get Windows could not connect to the System Event Notification Service service. Please consult your system administrator. and takes me back to the login screen. i can log back in as a domain admin fine. If i make the user a local admin on the laptop, it logs me in, but i get the same error message pop up, and it looks like aero basic.
May 9th, 2010 9:53pm

Also, it dosnt matter if I use x86 / x64 version of windows 7 or Pro / Ultimate / Enterprise version of windows 7 All have the same issue.
Free Windows Admin Tool Kit Click here and download it now
May 10th, 2010 12:54am

Hi, This issue can be caused by security programs. I suggest testing it in Clean Boot mode first. If it still does not work, temporarily disable any security programs. In addition, according to the following thread, running command netsh winsock reset will resolve it. Click the Start button, type CMD, right click on CMD and choose Run as administrator. Type in the above command and press Enter. The detailed information is as below: http://social.msdn.microsoft.com/Forums/en-US/windowscompatibility/thread/983e0736-57ef-4c6a-bb10-cfb2712dde24 Vivian Xing - MSFT
May 11th, 2010 2:27am

Hi The laptop i'm using to test this on is a fresh install of windows (ie, windows installed, and then joined to domain, no software/drivers loaded) I am in the same boat as the last person to post on that forum. "Unbelievable, this actually worked for me. Rebooting didn't help, winsock reset did nothing, but just waiting a couple minutes let me log in successfully, even after a failed logon. No idea if it'll help the rest of you, but it worked for me. If it fails to log in, I click OK, wait a couple minutes, and it logs in fine." Netsh command didint do anything, but leaving the laptop on the login screen untill hdd light stops flashing, and then loggin in does work. so I guess my next question is, What is it waiting for?? some service taking too long to start? could it be related to mapped drives? we use roaming profiles and several other mapped network drives. if i log in straight away after reboot, i get an error saying "cannot connect to all drives" but it disapears after a few seconds and the drives are connected. if i wait at the login screen, and then login, i dont get this error.
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2010 5:52pm

Hi, Thank you for your update. How about disconnect the mapped drive and try again?Vivian Xing - MSFT
May 17th, 2010 3:46am

Hi, I ran the netsh routine and that made the computer totally unaccessable. I can not longer log in at all.. I just am out of my mind with this issue as I have 10 new computers from HP, all with the same problem and no fix in site. I did not purchase the computers to look at! any other suggestions?? thank you GaryGary Hemmer
Free Windows Admin Tool Kit Click here and download it now
January 10th, 2011 7:30am

I just spoke to a caller that had this issue. I had him remove the power cord and battery for 10 seconds and then reconnect and try again. They were able to get logged in without any error.
April 27th, 2012 4:40pm

I had a similar issue. I was able to log on the PC as local admin. I fixed the issue by putting the PC in an active OU (One you are actively using). We have new PCs placed in Mismanaged account until it is moved for the services needed Hope this helps.
Free Windows Admin Tool Kit Click here and download it now
September 6th, 2012 11:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics