none
Windows 8.1 - Windows Couldn't connect to the System Event Notification Service service RRS feed

  • Question

  • I have an issue that has been bothering me for a while on new 8.1 computers. Standard users are not able to log into the computer on the first try consistently. They receive the error message: Group Policy client service failed the sign-in access is denied. They are stuck at the logon screen.

    If an administrator logs in (local or domain), they can log in but get a black desktop with two error messages. The first is Location is Not available - C:\Windows\system32\config\systemprofile\Desktop is unavailable. The second error message is a popup balloon. It states "Failed to Connect to a Windows service. Windows couldn't connect to the System Event Notification Service service."

    When a standard user attempts to log in, event viewer records three warnings. They are listed in order from oldest to newest

    The winlogon notification subscriber <Profiles> was unavailable to handle a critical notification event. -Logged 9:14:44

    The winlogon notification subscriber <GPClient> failed a critical notification event. - Logged 9:14:44

    The winlogon notification subscriber <Profiles> was unavailable to handle a notification event. - Logged 9:14:49

    After a reboot, users still have the issue. I noticed that the user profile services and system event notification service are not running though their startup type is automatic. They start after a minute or two.

    Monday, April 13, 2015 1:17 PM

Answers

  • Hi Joseph__Moody,

    Based on your description ,I assume it is a domain environment .First of all ,I would suggest you to try to update all the machine .

    "I have an issue that has been bothering me for a while on new 8.1 computers"
    Do you mean all the Windows 8.1 machine share the same symptom or just a specific one ?Did the machine work correctly before ?When did the issue start to occur ?Have you installed any third party software before ?Can we operate the machine when we login with an administrator account ?

    If the issue occurred with the specific machine :
    "The first is Location is Not available - C:\Windows\system32\config\systemprofile\Desktop is unavailable."
    Please try the following suggestions if we can operate the machine when we login with the administrator account :
    Open Windows Explorer and navigate to: C:\Windows\system32\config\systemprofile and verify if it has the Desktop folder there.If the folder doesn`t exit, we can copy from C:\users\Default\Desktop location(This folder is hidden by default).
    We also can try the following suggestions to have a troubleshoot :
    1.Run "sfc /scannow"or "dism /online /cleanup-image /restorehealth" to check the health of the system files.
    2.Perform a full scan with an antivirus software.
    3."They start after a minute or two."
    I suspect there is a third party service confilct here. Please perform a clean boot to verify whether there is a third party conflict here .
    How to perform a clean boot in Windows
    https://support.microsoft.com/en-us/kb/929135

    If the issue occurred with multiple machines in the domian ,I would suggest you to check whether you have configured any logon scripts and logon group policy .We can remove the machine from the domain to have  a troubleshoot .

    If the issue occurred recently ,we can perform a system restore to recover the machine to a previous normal point.
    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by Joseph__Moody Thursday, April 16, 2015 1:43 PM
    Tuesday, April 14, 2015 8:54 AM
    Moderator
  • I think I found the solution. There was a video driver update for the Intel HD Graphics 4400 that addressed this problem. So far - we've been good. Thank you for your help in resolving this!

    If my answer helped you, check out my blog: Deploy Happiness

    • Marked as answer by Joseph__Moody Thursday, April 16, 2015 1:43 PM
    Thursday, April 16, 2015 1:43 PM

All replies

  • Hi Joseph__Moody,

    Based on your description ,I assume it is a domain environment .First of all ,I would suggest you to try to update all the machine .

    "I have an issue that has been bothering me for a while on new 8.1 computers"
    Do you mean all the Windows 8.1 machine share the same symptom or just a specific one ?Did the machine work correctly before ?When did the issue start to occur ?Have you installed any third party software before ?Can we operate the machine when we login with an administrator account ?

    If the issue occurred with the specific machine :
    "The first is Location is Not available - C:\Windows\system32\config\systemprofile\Desktop is unavailable."
    Please try the following suggestions if we can operate the machine when we login with the administrator account :
    Open Windows Explorer and navigate to: C:\Windows\system32\config\systemprofile and verify if it has the Desktop folder there.If the folder doesn`t exit, we can copy from C:\users\Default\Desktop location(This folder is hidden by default).
    We also can try the following suggestions to have a troubleshoot :
    1.Run "sfc /scannow"or "dism /online /cleanup-image /restorehealth" to check the health of the system files.
    2.Perform a full scan with an antivirus software.
    3."They start after a minute or two."
    I suspect there is a third party service confilct here. Please perform a clean boot to verify whether there is a third party conflict here .
    How to perform a clean boot in Windows
    https://support.microsoft.com/en-us/kb/929135

    If the issue occurred with multiple machines in the domian ,I would suggest you to check whether you have configured any logon scripts and logon group policy .We can remove the machine from the domain to have  a troubleshoot .

    If the issue occurred recently ,we can perform a system restore to recover the machine to a previous normal point.
    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by Joseph__Moody Thursday, April 16, 2015 1:43 PM
    Tuesday, April 14, 2015 8:54 AM
    Moderator
  • I think I found the solution. There was a video driver update for the Intel HD Graphics 4400 that addressed this problem. So far - we've been good. Thank you for your help in resolving this!

    If my answer helped you, check out my blog: Deploy Happiness

    • Marked as answer by Joseph__Moody Thursday, April 16, 2015 1:43 PM
    Thursday, April 16, 2015 1:43 PM
  • I have a similar problem that manifested on the 28th of May.  I am getting the same error messages as Joseph exactly and they are intermittent; I am able to successfully log on as an Administrator (there are no standard user accounts) 4 or so out of 5 times.  1 out of 5 I get the error message.  I ran sfc /scannow as well as did all patch tuesday updates today.  SFC reported some files it could not repair.  I scanned the SFC log for error as per here and below are the results that couldn't be repaired:

    Also here are some links to the event viewer logs for 3 times Windows manifested the error; as you can see there's some weird problem with my network driver however the problem manifests all the time not just with the error message.  Also there are a bunch of services that terminate unexpectedly on boot and this only happens with the error.

    I do have Comodo Firewall installed which I've heard is very aggressive and can cause problems.

    Any ideas?  Thanks!

    https://www.dropbox.com/l/bcRfO7pqThnsLPgavhVxRn

    https://www.dropbox.com/l/Bv3HSojmlCyryHbEL778Tn

    https://www.dropbox.com/l/SLPLOaGY21oqf94eEHOpon

    2015-06-10 16:42:36, Info                  CSI    000004ba [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:42:36, Info                  CSI    000004bc [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:42:37, Info                  CSI    000004be [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:42:37, Info                  CSI    000004bf [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
    2015-06-10 16:42:37, Info                  CSI    000004c1 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:42:37, Info                  CSI    000004c2 [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"

    2015-06-10 16:43:39, Info                  CSI    000005a9 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:43:40, Info                  CSI    000005ab [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:43:40, Info                  CSI    000005ac [SR] This component was referenced by [l:166{83}]"Package_2709_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-6825_neutral_GDR"

    2015-06-10 16:46:54, Info                  CSI    000008fd [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:46:54, Info                  CSI    000008ff [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:46:54, Info                  CSI    00000901 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:46:54, Info                  CSI    00000903 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:46:54, Info                  CSI    00000904 [SR] This component was referenced by [l:166{83}]"Package_2709_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-6825_neutral_GDR"
    2015-06-10 16:46:54, Info                  CSI    00000906 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:46:54, Info                  CSI    00000907 [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
    2015-06-10 16:46:54, Info                  CSI    00000909 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-06-10 16:46:54, Info                  CSI    0000090a [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
    Thursday, June 11, 2015 12:08 AM