This is a followup of https://docs.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?