RDP in Win10 Fall Creators Update, version 1709, crashes if there’s a redirected printer

Topic

New Reply

Chariman MAO on the TechNet forum offers this: I just installed the Fall Creators Update on Windows 10/64 bit, and now Remote Desktop  Connection cras
[See the full post at: RDP in Win10 Fall Creators Update, version 1709, crashes if there’s a redirected printer]

Reply | Quote

Replies

A “jphughan” in that thread hits the nail on the head:

This issue and the original topic of this thread are incidentally emblematic of a concern I’ve had for a while, namely that the relative ease of deploying patches these days has led developers not to bother getting it right in the first place.  That’s true across multiple industries, but the fact that Microsoft has now officially moved to a planned 6-month cadence for major Windows 10 releases only amplifies this concern, since I really worry that the norm will be that issues “will be fixed as part of the next release, which is only a few months away” rather than being fixed the current release promptly, or ever.  But since new releases are always going to have new features as well, and the bugs that come with them, I think we may well end up in a state of affairs where NO release ever really works the way it’s supposed to.  Bugs will creep in, they won’t get fixed until the next release (if then), but that release turns out to introduce several NEW frustrations, so rather than ever having a properly stable platform, you’ll just constantly be trading one set of aggravations for another.

Welcome to Windows as a Service.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

8 users thanked author for this post.

DAVe3283, johnf, Noel Carboni, Ascaris, MrBrian, Sessh, BobbyB, Elly

Reply | Quote

Wait, let me get this straight… The remote desktop software delivered with Windows fails while the tsclient in the previous version AND the stuff available in their store works?

All the while there’s telemetry that tells Microsoft the moment there’s a crash, and a Windows Update process in place primed to download gigabytes and reboot the computer on any given night?

Version 1709 has an 09 in it because that corresponds to September, and it’s now November, right?

In what universe does this help sell WaaS to business – the base of customers who care whether things actually work and from whom Microsoft expects to extract big money.

When we see Satya Nadella reconstitute Microsoft’s system testing organization in order to be able to deliver working software, then I’ll start to think there’s a prayer again for Microsoft.

-Noel

3 users thanked author for this post.

DAVe3283, RamRod, Cybertooth

Reply | Quote

This is what you get when M$ force their Win 10 users to upgrade to new Versions every 6 months, which was implemented mainly for the purpose of filling up their money coffer$. No other fairer and right-minded OS vendors are doing thus.

Similarly for greedy and “left”-minded M$ putting their full-featured and heavyweight desktop OS, ie Win 8.x/10, on mobile touchscreen tablets which conversely by design have to be lightweight, thin, compact, miniaturized, fanless and battery-powered(= low power and low speed). No other OS vendors are doing thus.

Reply | Quote

I had to revert Windows 10 back to the previous version in recovery options to version 1706 to enable remote printing again.  Also, version 1703 works as well.  I had to do this because some of my clients using remote desktop need remote printing as a necessary feature.  They have depended on this feature for quite a few years which has worked successfully through Windows XP, Windows 7, Windows 8, and Windows 10 (up to version 1706).  Then, after I reverted Windows 10 back to version 1706, I went into services.msc and disabled automatic updates temporarily until Microsoft can get their act together and launch a fix for this annoying bug.  I’m sure thousands, if not millions, of people have been affected and will voice their frustration at Microsoft until it is fixed.

Adam Glazener

I.T. Administrator

Broadcast Technical Services

http://www.btshouston.com

1 user thanked author for this post.

woody

Reply | Quote

I see you mention version 1706. Do you mean v1607 Anniversary Update?

Reply | Quote

Must be 1607. I think.

Hey, it’s hard keeping track of all of these versions!

Reply | Quote

I’ve heard a rumor that a fix will be distributed late this month.

Reply | Quote

Does anyone know if the patch has been released to fix this?

Reply | Quote

Fixed in https://support.microsoft.com/en-us/help/4051963

Reply | Quote

Well now we are in last december, and this rdp still crashes, why cant Micorsoft fix it and release it quickly, becourse off so many people is use rdp.
this issue was allso in the eastern greator update, tree month afte the was there, now its the same again, start all over and no rdp, sad they not can check before release.

Ronny

Reply | Quote