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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-10-20T14:41:39+00:00

    I have two computers that I updated - a desktop and a laptop. The laptop is the only one that experienced the RDP hang problem. I opened up the connection and clicked on Show Options, Local Resources tab, and unchecked Printers as I have no printer connected to the laptop. RDP worked fine after that.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-10-21T17:02:53+00:00

    Bingo! Worked for me as well! Unchecking "Printers" under "Local resources" solved crash issue. You obviously lose printing ability, though.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-10-21T21:41:29+00:00

    Bingo! Worked for me as well! Unchecking "Printers" under "Local resources" solved crash issue. You obviously lose printing ability, though.

    Did you have a printer physically attached to that computer? In the case of my laptop I had no printer so one could not provide a local resource. My desktop did have a printer physically attached so it did work with printers checked.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-10-24T16:25:53+00:00

    Hey. Wanted to weigh in here. I'm having the same issue after updating to the Fall Creators Update. MSTSC.exe is crashing after logging into one of my servers. It's only affecting the log in to the one server though. I have two others that I can remote to with no issue. I'm thinking the Fall Creators Update has screwed up something with MSTSC.exe somehow. Never had this issue prior to the update. 

    Here's the crash code: 

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

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

    Exception code: 0xc0000409

    Fault offset: 0x0000000000090d5f

    Faulting process id: 0x4e4c

    Faulting application start time: 0x01d34ce3d588131e

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

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

    Report Id: 3d49b658-6210-40bd-8c20-bbfe2938baa5

    Faulting package full name:

    Faulting package-relative application ID:

    Was this answer helpful?

    0 comments