Windows could not connect to the system event notification service

[RanSy]

So recently I had hardware issues, and through warranty I had several replacements done. Mobo, Video cards, ram sticks, and the power supply.

After all that was fixed and replaced my computer seemed to have ran fine for a few days, and it still technically is except for this problem.

The problem is when I log in into windows normally it takes a while for Windows to boot up. I get a "Please wait" screen, then after a long 4 minute log in once inside windows I get the"Windows could not connect to the system event notification service", and the toolbar is grey all old school windows like.

The problem is the exact same as the issues found here except I am using Windows 7 64 bit.

http://social.technet.microsoft.com.../thread/cb3f49be-a228-4fbb-a665-9d2def157f56/

http://social.technet.microsoft.com.../thread/08f725f1-fd8a-4417-8d01-de37253c70cd/

In services the service is called System event notification, it says that the service is running fine. Even when i try to restart it, it makes no difference at all.

As for in event viewer. Im not to sure what to look for in there.

Ive looked at several familiar threads, I did the sfc /scannow twice, i did a windows start up repair, I disabled all non-windows services, and even just tried restarting the service in services.

I'm not really sure what to do next. I'm tempted to just to do a clean install. However I am cautious on doing so, in case its some kind of hardware problem...

Anyway do any of you have any recommendations or other possible solutions I havent tried yet?

Thanks in advance.

 

[Saltgrass]

Through your post, I seemed to have missed your actual problem. Is it the system notification service in your title?

What are the particulars of the Event Viewer Error messages about that occurrence?

 

[RanSy]

Sorry about that. Somewhat stressed from this. Anyway I fixed my OP, everything I added to OP is in this message.

The problem is when I log in into windows normally it takes a while for Windows to boot up. I get a "Please wait" screen, then after a long 4 minute log in once inside windows I get the"Windows could not connect to the system event notification service", and the toolbar is grey all old school windows like.

The problem is the exact same as the issues found here except I am using Windows 7 64 bit.

http://social.technet.microsoft.com.../thread/cb3f49be-a228-4fbb-a665-9d2def157f56/

Failed to connect to a windows service

In services the service is called System event notification, it says that the service is running fine. Even when i try to restart it, it makes no difference at all.

As for in event viewer. Im not to sure what to look for in there.

 

[RanSy]

Bump of justice.

 

[Saltgrass]

In the Event Viewer, look for Errors, or perhaps even info, around the time you boot your system. That would be the best way to tie particular errors to the problem.

You can highlight each error and expand it to see if any text is included describing a problem. From the other threads you linked, some services may be involved. Or maybe even some anti-virus is blocking the communications.

Check the Action center (white flag) and see if anything is being mentioned there.

 

[RanSy]

Well this time it took even longer to log in. After "Please wait..." it left me with a "Preparing your desktop..." screen. In which once i logged in my background was black, toolbar still grey and had an error message saying "Location is not availble. It could not find my system profile. C:\\Windows\system32\config\systemprofile\Desktop refers to a location that is unavailble. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the internet on your network, and then try again. If it still cannot be located, the information might have been moved to a different location".

Also the failed to connect to windows service popped up as well.

While replacing parts on my computer, the technician who came through warranty may have unplugged my disk temporarily.

Is it possible that this is what is causing the issue? That the HDD is not connected properly? I have gotten this issue twice now (all within 24 hours). Though it is not consistent as my system event problem.

So I rebooted since I cannot do anything when that happens. Went into safe mode and checked event viewer.

In event viewer I have 18 errors of ID 7001 Service Control Manager- "The network list service, service depnds on he network location awareness service which failed to start because of the following error: the dependency service or group failed to start.

I also have 6 ID 10005 DCOM errors. "DCOM got error "1084" attempting to start the service WSearch with arguments""in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030}

I also had a few winlogin warnings that failed to handle a critical notification event.

Lastly the whiteflag thing didnt have anything useful to tell me. Nothing new in there.

 

[Bumpkin]

Try running system file checker.
In the search box enter CMD, right click on cmd.exe and select Run as Administrator. Enter sfc /scannow at the prompt. It will check and try to repair system files.

 

[RanSy]

I've done sfc /scannow, and have found no issues. I've done it twice and did a mandatory check when i booted up my PC once. I did all the scans within 3 hour time period.

 

[Bumpkin]

This is getting above my pay grade, but while waiting for help from a more experienced poster, try this.

Go to Component Services > Services (Local) and find the services that event viewer lists. They should be started or automatic. Right click on the service and select Properties > Dependencies. Be sure all the dependencies for that service are started or automatic.

 

[RanSy]

Just booted up my PC to do what you mentioned above, havent done it yet, and my PC randomly booted normally.

Now I'm even more confused.

 

[RanSy]

I'm wondering if maybe my OS just got a tad corrupted or something. Possibly a repair install is in order.

I still have no real idea though. I'm just throwing up ideas.

 

[Saltgrass]

The message about dependencies seems to be correct in what it says. If you do not know, the Services.msc panel is where you can check the properties of services. One of the tabs shows the dependencies for that service. If one of those is not running the service cannot start up.

The network list service, service depnds on he network location awareness service which failed to start because of the following error: the dependency service or group failed to start

Look at the dependencies for the Network List service. You will see network location awareness listed as a dependency, along with Remote Procedure Call, and other items under those headings. If you can track back the dependencies until you find something not running or can't be started, and figure out why, you might find the answer.


For instance, the message says the Network location awareness failed to start. Is it running or stopped? Can you start it or do you get some kind of message. This service depends on Network Store interface Service, Remote Procedure Call and TCP/IP Protocol Driver. Are they all started or able to start, and so on. The TCP/IP protocol driver has a different symbol, so it might be a driver and not a service

Also, make sure and check the WSearch, service (Windows Search I think) to see what is happening with it.

Let us know if you run into a problem or need to know what should or should no be currently running and we can check our systems to compare. I will be back tomorrow...

 

[Saltgrass]

I have gone through and checked the dependencies on your services. From what I see, they should all be running. All are set to Automatic Start except for Network List Service, which is set to manual. WSearch is set to Automatic (Delayed) start.

TCP/IP starts at boot and NSI proxy is started by the SYSTEM.

If you haven't tried reinstalling yet, it might be the best choice, as you mention. I saw threads that seem to mention a virus or even some update or software install may be involved, but no way to tell. If you reinstall and see these components, then you can watch them to make sure the problem does not reoccur.

 

[RanSy]

Ah, well the day before this problem occured I did my monthly set of virus scans. Also didd boot time scans once the problem happened as well. So im sure its not a virus, but I think I will try a repair install, if that doesnt solve it ill probably nuke the drive and do a clean install.

 

[RanSy]

So I did this method found here.

https://support.soluto.com/entries/...o-the-system-event-notification-service-error

And it actually has fixed my problem (at least temporarily). I did a few boot ups. And it seems to be functioning fine.

Tomorrow I will post information on if the problem has returned or not.

If so. Hopefully this thread will help others in the future.

Keep you posted!

 

[RanSy]

Well, this fix only helped temporarily.

Once the problem returned I did a clean install, however after applying a few windows updates the problem has yet again return.

This is no longer a software issue for my case. I am now left to call my warranty service.

Just got done contacting them. All they had to say was to not update windows...in other words theyre not going to help.

Any ideas on how to solve this problem of mine is appreciated...thanks...