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-19T15:16:55+00:00

    It started after .19 update via the Automatic update.  Before that I used RDP on daily basis and no issues.  After the Windows 10 Fall Creators update RDP isn't working and Adobe Acrobat crashes every time its used.  Adobe Acrobat crash issues are as below:

    Description

    Faulting application name: splwow64.exe, version: 10.0.16299.15, time stamp: 0x7403b6eb

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

    Exception code: 0xc0000409

    Fault offset: 0x0000000000090d5f

    Faulting process id: 0x2e64

    Faulting application start time: 0x01d3483ccbe929c9

    Faulting application path: C:\WINDOWS\splwow64.exe

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

    Report Id: 1840a731-f5f2-44de-b287-b1086b3096d8

    Faulting package full name: 

    Faulting package-relative application ID: 

    Description

    Faulting Application Path: C:\Windows\splwow64.exe

    Problem signature

    Problem Event Name: BEX64

    Application Name: splwow64.exe

    Application Version: 10.0.16299.15

    Application Timestamp: 7403b6eb

    Fault Module Name: ntdll.dll

    Fault Module Version: 10.0.16299.15

    Fault Module Timestamp: 493793ea

    Exception Offset: 0000000000090d5f

    Exception Code: c0000409

    Exception Data: 000000000000000a

    OS Version: 10.0.16299.2.0.0.256.48

    Locale ID: 1033

    Additional Information 1: 275f

    Additional Information 2: 275f0f44c060eb151c5662542ef60619

    Additional Information 3: a9c8

    Additional Information 4: a9c8e269d9d06af0b3bc00043cb3ee7d

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-10-19T15:21:44+00:00

    I shifted this over to TechNet per the moderator's request. You can find the thread here.

    Short version: for me and others, disabling printer support (in the connection options) before launching a connection appears to solve the problem. Your mileage may differ, of course.

    • Mark

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2017-10-20T01:28:16+00:00

    Opened a support case on this 

    [REG:117101916518777] RDP with rdgateway broken in Windows 10 1709

    Where did you post on TechNet?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-10-20T01:38:28+00:00

    Ignore, found your link.

    Was this answer helpful?

    0 comments