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
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

63 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-12-05T01:53:20+00:00

    it seems to have also solved this.

    i am also having the program PhotoScape X Pro crash when i tell it to print. when will MS have a solution?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-12-04T22:00:26+00:00

    Follow this:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/37294254-0fc6-4eb8-aa9c-87da8af32279/error-remote-desktop-connection-has-stopped-working?forum=winserverTS

    If anyone else runs into this issue I would suggest the following steps:

    1. Disable the "printers" check box on your Remote Desktop Connection by navigating to Options>Local Resources>Local Devices and resources. Then try to connect.
    2. If connection is successful with the printers disable, start removing printers on your local machine one by one in order to figure out which printer is causing the problem.
    3. Once you have figured out the problem printer driver, reinstall with a different driver.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-12-04T20:58:12+00:00

    Crash report, if it helps:

    Faulting application name: mstsc.exe, version: 10.0.16299.15, time stamp: 0x3a40081f

    Faulting module name: ntdll.dll, version: 10.0.16299.64, time stamp: 0x493793ea

    Exception code: 0xc0000374

    Fault offset: 0x00000000000f87bb

    Faulting process id: 0x2210

    Faulting application start time: 0x01d36d17ac63fe3a

    Faulting application path: C:\WINDOWS\system32\mstsc.exe

    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

    Report Id: 427431e2-6ca2-49e2-8061-c52b63c17bea

    Faulting package full name:

    Faulting package-relative application ID:

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-12-04T20:09:50+00:00

    also screenshot of printers

    Was this answer helpful?

    0 comments