Windows 10 Fall Creators Update: Remote Desktop Crashes

Anonymous
2017-10-17T21:48:11+00:00

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?

  • Mark
Windows for home | Windows 10 | Internet and connectivity

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.

0 comments No comments
Answer accepted by question author
Anonymous
2017-10-31T00:43:15+00:00

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

Was this answer helpful?

60+ people found this answer helpful.
0 comments No comments

63 additional answers

Sort by: Oldest
  1. Anonymous
    2017-12-08T05:56:12+00:00

    You don't need to do any of this crazy workaround, this issue was fixed in the previous cumulative update. Just make sure you have Windows 10 version 1709 November 30, 2017 cumulative update - KB4051963 (build 16299.98) or later. (Current build is 16299.125)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-12-08T06:20:34+00:00

    Thanks for that info! 

    That update just showed up on my computer today after I told it to check for updates.  I am able to print remotely now.  Thanks again.

    -Stan

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-12-23T14:33:27+00:00

    Excellent! This also solved the issue for me. Thank-you.

    Was this answer helpful?

    0 comments No comments