By: Steffen
2012 R2: same error. Just wait 10 Minutes…Same error every windows version…
View ArticleBy: Graceson Mathew C
My probKilling the svhost process worked for me as well,step 1 : get the command prompt though different user or using psexec type : sc queryex sens step 2 :find the PID.Step 3 : run taskkill /PID
View ArticleBy: jahs1980
The other posted techniques did not resolve my issue. I had Windows Server 2012 that did not shut down and/or reboot. I have a USB 3.0 connected external drive where connectivity to it became unstable....
View ArticleBy: tulsianiprashantshant
Hey Guys,does anyone found the solution from Microsoft… am facing the same issue with Windows 2008 R2 with Exchange 2010 running… Hard Reboot works but that’s a workaround not the solution… does...
View ArticleBy: Prabhat
Thanks a lot, Graham. Your method just worked absolutely fine without rebooting the server. Thanks, again.
View ArticleBy: jpxdude
How does one solve this problem with Windows 2008 Standard? RDSM doesn’t exist, as it still uses Terminal Services! Plagued with this issue for a while now, and won’t go away. Have attempted command...
View ArticleBy: zack
This is a privacy issue. Microsoft doesn’t need to know everytime to shut down your computer. Call your Congressman is the solution for the illegal activity by M$.
View ArticleBy: ziwarfani
below method worked for me too. thanks,Start Remote Desktop Services Manager Identify the user ID in the Users tab In the Processes tab sort by ID Go down to the user ID and end the winlogon.exe...
View ArticleBy: Tmac
Well not it’s 2016 and just got this error, luckily server is in AWS so a hard shutdown and restart fixed the issue. it is a terminal server and i got this error when logging out of my session via my...
View ArticleClik here to view.
By: Syed
I’ve got this error yesterday. I wanted to restart my Cluster Node, then this Message did appear. I was waiting for like 30mins and watched the server with ping “IP-Adress” -t . Then after 34mins i was...
View ArticleBy: Danny9
For me, I disable the service “Windows Search”, and this solved my problem of “Please wait for the System Event Notification Service”, it shut down without hang now.
View ArticleBy: c
****************Didn’t Work***************As soon as we did this and try to access we server went blank and rebooted(Which fixed the issue) Logs indicated we had a freaking server crash……… I wont...
View ArticleBy: Cincolo
Did you figure out the cause of this? It just happened to my customer’s server last night. Is it still happening? How did you disable the Windows Search when the screen was stuck on the message, or did...
View ArticleBy: Remote Server: Please wait for the System Event Notification Service -...
[…] advised in the comments in this link, there’s a problem with SENS. I couldn’t run sc queryex successfully, so I took the […]
View Article