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
Windows 10 Fall Creators Update: Remote Desktop Crashes
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
Answer accepted by question author
Anonymous
63 additional answers
Sort by: Oldest
-
Anonymous
2017-11-03T22:08:13+00:00 Definitely that was the issue. Excellent.
-
Anonymous
2017-11-04T14:41:37+00:00 HI Following this thread I solved my problems. Seams a problem with the driver of a printer installed by Quickbooks
"I have tested this with a few machines running 1709 16299.19 for me it was defiantly a print driver issue. I removed the offending driver and remote desktop and remoteapp now function correctly without crashing. You must remove the printer then go to administrative tools and then print management. Remove the driver package for the printer and poof all if fine.
(Amyuni Document Converter 400 driver)
Working with a client we discovered changing version settings of the ABS PDF driver from 400 to 450 solves the problem.
FWIW, according to this article, the ABS driver is no longer used directly by QuickBooks after 2013. It remains for only the Business Plan Tool subcomponent, and kept for legacy compatibility. It should be safe to remove the ABS driver and still get PDF output from QuickBooks.
Hi jp_538 -
Excellent job! Reminds me of a problem I had with one of my desktops. I could not upgrade to Win 10 - would run for a long time and then croak. Turns out a Quicken ini file that had a null entry and the upgrade script could not handle that.
-
Anonymous
2017-11-09T23:42:25+00:00 I had to revert Windows 10 back to version 1703 in recovery options which worked. Also version 1703 works as well with the remote printing feature enabled. Then, I went into services.msc to disable automatic updates temporarily until Microsoft can get this resolved. Unfortunately, Microsoft has this problem to fix in version 1709 to allow remote printing not to crash Remote Desktop Protocol from running. (Please hurry and fix this issue Microsoft!!!) :(
--
Adam Glazener
I.T. Administrator
Broadcast Technical Services
-
Anonymous
2017-11-13T07:22:10+00:00 I had the same issue, and unchecking Printers under the Local Resources tab allowed me to connect and stay connected.
As someone had mentioned Quickbooks....I do not have that app installed at all, yet I still had the same issue after updating my laptop to 1709 while my desktop was still version 1703.
I updated my desktop to 1709, hoping that doing so would solve the problem, but it did not. With my desktop and laptop on 1709, RDP still dropped immediately after connecting, and continued to do so until I unchecked PRinters under the Local Resources tab on my laptop (which I use to remote into my desktop).