question

FrankHeimes-6803 avatar image
1 Vote"
FrankHeimes-6803 asked DA-3393 edited

Remote Desktop hangs on connecting after return from hibernate

I'm running Windows 10 Enterprise LTSC 1809 on an Intel NUC.
In the evening, I put it to hibernation and the next morning I wake it up by pressing the power button.

I can access it via RDP (from the same Windows version), which works most of the time.
However, sometimes the RDP session gets stuck at the "connecting" wait screen for at least several minutes, after which I lose patience.

TeamViewer is also installed and in this situation I can open a TeamViewer session within seconds.
TeamViewer ALWAYS works if RDP has any problems whatsoever.
After opening and closing a TeamViewer session, another attempt to use RDP ususally works within a few seconds.

Please spare me with all the "advice" (scan disk, hack some registry, reinstall windows, ...) I've already read on the internet a thousand times.

What I'd like to know is whether there is any way to make the 1-Bit feedback of RDP ("works", "doesn't work") somewhat more verbose?
Just like the verbose boot flag that tells what windows is doing right now while booting.
Is there any RDP diagnostic logging that can be enabled (on either side of the communication peers)?

remote-desktop-serviceswindows-10-networkremote-desktop-client
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LeilaKong-MSFT avatar image
0 Votes"
LeilaKong-MSFT answered

Hello @FrankHeimes-6803 ,

Will the issue occur if you power off the computer instead of hibernation?
How to View RDP Connection Logs in Windows: https://sysadminpoint.com/2020/07/13/how_to_view_rdp_connection_logs_in_windows/
Troubleshoot user profiles with events: https://docs.microsoft.com/en-us/windows-server/storage/folder-redirection/troubleshoot-user-profiles-events


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.




5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FrankHeimes-6803 avatar image
1 Vote"
FrankHeimes-6803 answered

@LeilaKong-MSFT
Thanks for your hints.

I don't recall that the problem occurs if I power down the system. Only return from hibernation is affected.

The RDP log lists the following events; so everything is fine according to RDP
Event 261: Listener RDP-Tcp received a connection
Event 1149: Remote Desktop Services: User authentication succeeded: ...

The application log shows the folloging warnings and errors:
Event 17: Security Center failed to validate caller with error DC040780.
Event 0: The description for Event ID 0 from source openvpnserv cannot be found.
Event 6005: The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (CreateSession).
Event 6006: The winlogon notification subscriber <GPClient> took 64 second(s) to handle the notification event (CreateSession).
Event 6006: The winlogon notification subscriber <GPClient> took 491 second(s) to handle the notification event (CreateSession).

So your recommendation - check RDP log, then user profile log - was helpful.

I forgot to mention one specific circumstance that triggers the misbehavior:
On some weekends, I literally take "work" (i.e. my Intel-NUC) back home.
At work, the NUC is directly attached via LAN cable; at home it is connected via WiFi and OpenVPN.
The problem arises when I put it to hibernation at home and wake it up at work.

I found reports of GPClient randomly stalling the logon process for several minutes back in 2014.
Apparently that's undefined behavior that has never been fixed.

According to https://community.spiceworks.com/topic/324801-winlogon-notification-subscriber-gpclient-error-taking-605-seconds-to-boot, GPClient presumably tries to fix an allegedly corrupted WBEM repository

But that doesn't make sense because why is TeamViewer still able to open a login screen within a second and allow me to login without delay? If the WBEM repository was corrupted at that point, it still would require repair - right?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DA-3393 avatar image
0 Votes"
DA-3393 answered DA-3393 edited

Same problem for years when I bring laptop back to work from home. Stuck on please wait. Once in awhile it will time out after a long time, like 5 or 10 minutes, then give me the legal notice screen. Once I closed lid and tried again and it worked. 95% of the time I am force to reboot and lose all my windows and setup which windows will not restore; this is a massive issue for the programs and work I need open in the state they are in. These states cannot be saved, even for a particular Word compare mode, folders, and other programs that do not support restore.

It only does it in the office on the domain, never at home or anywhere else. I'm certain it is the new legal notice before logon that was added with GP.

I usually am on WIFI everywhere, but I've seen it do it with the NIC.

I waste 10 minutes a day, every morning, for years, for what???

9:09:39 AM 6005 The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (CreateSession).
9:12:30 AM 6006 The winlogon notification subscriber <GPClient> took 230 second(s) to handle the notification event (CreateSession).
9:12:30 AM 6006 The winlogon notification subscriber <GPClient> took 372 second(s) to handle the notification event (CreateSession).

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.