Disabling Printer redirect on RDP connection resolved the crashing. Crashing was taking place on a Windows 10 PC using the native Desktop RDP app, not the Windows 10 RDP store app.
Ray
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I just installed the Fall Creators Update on Windows 10/64 bit, and now Remote Desktop Connection crashes every time I try to connect to another PC running Windows 10 64 bit (which I haven't updated yet). Moreover, my Surface 3, running Windows 10 (but also not yet updated) can successfully connect to the same target PC.
To be clear, the connection goes through. But, invariably, within 30 seconds the Remote Desktop Connection app crashes on the machine running the Fall Creators Update.
Methinks something didn't get tested before the update was rolled out.
Any workarounds or solutions?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Disabling Printer redirect on RDP connection resolved the crashing. Crashing was taking place on a Windows 10 PC using the native Desktop RDP app, not the Windows 10 RDP store app.
Ray
I thought I would chime in - I have 4 computers: 2 dell desktops, 1 dell laptop and a SP3 - all came to the fall creators update via Insider builds until .15 when I remove from insider, yesterday I received the cumulative update to .19. All my machines work with RDP fine, I'm in and out of sessions a few times a day.
I did just receive a call from a client, who just had his computer reboot to install through the standard channel, and they are now having issue on that computer, after a connection it locks up about 30 seconds. I can connect from my machine fine to this particular server. So there is some kind of issue, but it's more than just having the fall creators update.
Is it new to .19? I was using .15 for days, when it was the current Insider build (.19 wasn't pushed out for a while), and I used mstsc.exe all the time. I didn't see the issue.
Methinks something didn't get tested before the update was rolled out.
C.f.
I was wondering if I should uninstall Hyper-V before doing the update. I think I have my answer. ; )
Sadly, no. My only workaround was to remote in from a machine that hadn't updated to the Fall Creators Update yet.