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
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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?
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.
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
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.
I posted this issue on TechNet forum and got below response. I guess we will have to wait for an update from Microsoft to fix this issue.
I can confirm this behavior on every device with Version 1709 Build 16299.19. The Insider Version 1709 Build 17017.1000 does not crash, so we will probably need to wait for that to hit the pipeline. To resolve this problem for my clients I used the Recovery options in windows settings to go back to an earlier build of windows. Another work around is installing Remote Desktop from the Microsoft Windows App Store. Note that some terminal services like TSPrint won't work with this app.
After beginning to consider printers as a possible cause I deleted unised printers (to PDF and XPS) and this solved mu issue. Thanks!
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.