[Maxximou5]

Whoa, we got a necromancer over here, res-ing threads from the dead.
However, I found these two threads:

1. http://www.tenforums.com/network-sha...onnecting.html
2. http://www.tenforums.com/network-sha...w-seconds.html

[Fearts]

Yea, it's a old thread but it's my own thread and it's the exact same issue. I bumped this instead of making a new thread because I wanted to make sure anyone reading this saw my solution from the last time.

Thanks for your post but I don't think either of those links have a solution to my issue. I don't think it can be the computer going to sleep or logging off the session. The reason is if I log into another computer in my home with old Windows 7 RDP this issue doesn't occur. Also a friend of mine who also has Win 10 is able RDP into my machine without this issue.

Let me say the issue again, connecting via Win RDP to my machine is fine. I can connect and do what ever I want and it all works great. The issue lies in when I terminate the RDP connection. This seems to hang the machine.


If anyone has a solution I will pay a very nice sum of money. It's really causing me a lot of stress.

[Maxximou5]

Not sure if I just missed it, but can you tell me what version of Windows your VDS is running?

If you give me your setup and which version of Windows you tried connecting with, I will try to replicate this and see if I can find a solution on my own time. Being that I have every version of Windows.

While the issue may rely solely in Windows 8 and above connecting with RDP, I would first try the solutions given in the links I provided. They may not be the same problem, but you might as well try everything at this point before being so dismissive and asking for more help when the solution is something you could of been just that. But I can see that some solutions may not have any effect.

[Fearts]

I'm using Windows 2008 R2 Service Pack 1.

Also I found these two errors I think might be related:

http://pastebin.com/GTYB9Kqm

http://pastebin.com/fFKWYmyF

[Maxximou5]

That is very helpful information, in order of preference, try these links:
Hopefully one of these gives you more insight. More or less I just looked through links that seemed to be the same as your issue.

1. https://social.technet.microsoft.com...um=winserverTS
2. https://blogs.msdn.microsoft.com/scs...nent-x-224-de/
3. http://serverfault.com/questions/531...attempt-to-rdp
4. http://thebackroomtech.com/2010/08/3...ly-terminated/

[Fearts]

Also if I try to connect to the machine while my servers are timed out I see this screen: https://gyazo.com/3b2634084fe242bfc37935f2257bbf8b

[Fearts]

For anyone who is also having this issue now or in the future I will post some of my findings.

I did tests with 5 users who ran Windows 10 Home and 5 users who ran Windows 10 Pro. Each of them logged into my test machine 4 times. Each time with Home user it caused the crash to happen. Not once with the Pro user did it cause this issue.

Asherkin has read this thread and saw my errors and screen shot with the welcome screen. He says he is 100% sure that those two things together point to a winlogon crash.

[Fearts]

I upgraded from Home to Pro and that didn't seem to fix anything.

[Snaggle]

I've had similar issues in the past, both at home and at work. In both situations, turning off devices in local resources has resolved this for me.

RDP > Show Options > Local Resources

I keep everything other than Clipboard unticked.

Edit: Just saw your post about the windows home/pro tests. So this might not apply.