System Event Notification Service error
Some of our staff are receiving the following error message, which locks them out of their PC's for up to several hours.
"System Event Notification Service service
Please consult your System Administrator"
We have had this error in the past with a very few machines, but after the couple of hours or so, it let them in and the error didn't happen again.
I'm wondering if this is coming in on the heals of the MS patch for Meltdown & Spectre, or any MS update.
"System Event Notification Service service
Please consult your System Administrator"
We have had this error in the past with a very few machines, but after the couple of hours or so, it let them in and the error didn't happen again.
I'm wondering if this is coming in on the heals of the MS patch for Meltdown & Spectre, or any MS update.
Sean Plemons Kelly, CISSP
Have you looked in the Event Logs to see if it produced anything there?
ASKER
There were no significant event log errors
1. FailureName \Driver\WUDFRd
2. The Windows Audio service hung on starting.
I found a fix (netsh winsock reset catalog) that has been used by many people that has worked, but I always create a restore point before applying any fixes I've never run before.
Do you know how to create a restore point as a standard user, or do I have to log out and in as an administrator? All our users are standard users. It would be nice not to have to log in and out if there is a command I can run instead.
Thanks.
1. FailureName \Driver\WUDFRd
2. The Windows Audio service hung on starting.
I found a fix (netsh winsock reset catalog) that has been used by many people that has worked, but I always create a restore point before applying any fixes I've never run before.
Do you know how to create a restore point as a standard user, or do I have to log out and in as an administrator? All our users are standard users. It would be nice not to have to log in and out if there is a command I can run instead.
Thanks.
ASKER
Good morning.
I haven't received a reply to my last comment and my situation gets worse. We are getting more and more staff with this kind of error, and the only solution right now is to let users leave their PC's on, so they don't have to wait 20 or more minutes to get into the network every morning.
I tried running the "netsh winsock reset catalog" on one of the PC's, but it didn't work. I've been frantically looking for any solution. Has anyone run across this error before?
Thank you.
I haven't received a reply to my last comment and my situation gets worse. We are getting more and more staff with this kind of error, and the only solution right now is to let users leave their PC's on, so they don't have to wait 20 or more minutes to get into the network every morning.
I tried running the "netsh winsock reset catalog" on one of the PC's, but it didn't work. I've been frantically looking for any solution. Has anyone run across this error before?
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I tried one of the solutions in the TechNet post - the one that suggested reinstalling Symantec Endpoint antivirus. It has worked on the first PC, so I'm hoping it works for the rest.
Thank you for the post.
Thank you for the post.
Author stated that the solution worked.