Share via

GPClient effectively disables resume from hibernation

Frank Heimes 31 Reputation points
2021-05-26T07:35:05.043+00:00

This is a followup of https://learn.microsoft.com/en-us/answers/questions/368688/remote-desktop-hangs-on-connecting-after-return-fr.html

It turns out that not RDP but GPClient is the culprit.
I read about a corrupt user profile or corrupt WBEM repository.
I tested a script someone wrote to shutdown four services and delete the wbem folder.
That turned out to be effective, but only for the next login.

Since Windows is not a drag racing car that requires it's engine to be disassembled and repaired after each run, fixing the profile or wbem folder after each and every login is not acceptable.

And to top it all off - what I wrote in the precursor post is still correct: TeamViewer can always connect and login to that host after it resumed from hibernation within a second and it magically convinces GPClient to not stall the next login attempt for many minutes. So just by logging in and out using TeamViewer suddenly 'fixes' the profile and/or wbem?

Is there a way to fix GPClient's behavior or do I have to forego either hibernation or RDP for that host?

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
4,846 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,294 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Leila Kong 3,691 Reputation points
    2021-05-27T02:25:01.747+00:00

    Hello @Frank Heimes ,

    Thanks for your followup.

    1.What about RDP to other host or recreating profile?

    2.Can you try booting in the safe mode and then login? Did the problem still persist? Are there any logon scripts applied to this machine and the policy “Run logon scripts synchronously” is enabled? If so, please temporarily disable the policy or remove the logon scripts to check the result.
    https://social.technet.microsoft.com/Forums/en-US/04766dee-8cd4-4935-a401-5be9fb35da1e/logon-issue?forum=w7itpronetworking
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/b38cf1f7-2266-4846-be57-161b023af8eb/warning-showing-quotthe-winlogon-notification-subscriber-ltgpclientgt-is-taking-long-time-to?forum=winserverGP

    3.Can you check for Event ID 1074/1076 for the planned reboot of server?
    https://social.technet.microsoft.com/Forums/en-US/f112a043-72d0-413b-b1da-6d7981034b31/event-id-60056006-the-winlogon-notification-subscriber-ltgpclientgt-took-91-seconds-to-handle?forum=winservergen

    4.Did you disable IPv6 or is there any incorrect DNS settings on the client side?
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/ade979e7-b11e-4828-bfcc-bef42ee7015a/gpclient?forum=winserverGP

    Best regards,
    Leila

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments