How can I downgrade a RDP client to an older version? RRS feed

  • Question

  • Greetings,

    How can I downgrade a RDP client to an older version (on a thin client)?

    As for why: One of our departments received new thin clients earlier this year which have RDP client version 10.*something* on them. However, the department has barcodescanners attached to their thin clients and the barcodescanners do not seem to work properly on RDP client version 10 (the scanners now sometimes skip characters). On their previous, older thin clients which they ran RDP client version 6, the barcodescanners worked perfectly. Even though we've applied the exact same settings of RDP client version 6 to RDP client version 10, it doesn't fix the issue. We've also contacted the company of the barcodescanner (Zebra) multiple times but they also ended up not being able to help us out as they've tried everything they could from their side. They suggested us to either somehow downgrade the RDP client version or otherwise to buy new barcodescanners. Obviously we'd preferably skip the latter. 

    Wednesday, August 1, 2018 10:02 AM

All replies

  • Hiya,

    Which version are you after?

    This guys seems to have the same issue, with a resolution.


    "Thanks for your answer, but uninstall & reinstall gives me the most recent version of course, and not the version I want.

    The solution - in short - is as follows:

    Disable automatic app updates
    • open the Store
    • click on your profile icon and choose "Settings"
    • disable "Update apps automatically"
    Restore the old version

    You must have a copy of the wanted version of the app, in our case Remote Desktop 6.3.

    • uninstall the app
    • copy the RemoteDesktop_6.3.9600.16419_neutral__8wekyb3d8bbwe folder to C:\Program Files\WindowsApps
    Add the package to your user account
    Windows PowerShell
    Copyright (C) 2015 Microsoft Corporation. All rights reserved.
    PS C:\Users\user> Add-AppxPackage -Confirm -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.RemoteDesktop_6.3.9600.16419_neutral__8we
    Are you sure you want to perform this action?
    Performing the operation "Register package" on target "C:\Program
    [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): Y
    PS C:\Users\user>
    Grant access to the app folder

    Grant access to "ALL APPLICATION PACKAGES" (LOCAL user!) to folder "C:\Program Files\WindowsApps\Microsoft.RemoteDesktop_6.3.9600.16419_neutral__8wekyb3d8bbwe"


    Failed to notice it was Windows embedded, it might not work there, worth a try.
    Wednesday, August 1, 2018 10:13 AM
  • Hi, thanks for the support

    Yes I've stumbled upon that thread as well :-) just where can I obtain RDP 6.3 if I don't have a copy of it? Considering the old thin clients which had RDP 6.3 are gone :-) 

    Wednesday, August 1, 2018 12:08 PM
  • What OS were they on?

    Wednesday, August 1, 2018 12:25 PM
  • This forum is for Windows Embedded POSReady OS.

    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    Wednesday, August 1, 2018 4:25 PM
  • I managed to get the files needed for version 6.3 mstsc from an old server. It's not an install package, so not quite sure if it will work as described in the previous post.

    Never the less, I can open mstsc as version 6.3, as long as I keep the files in that structure as in my zip file.

    Maybe it can get you through.

    The below is a Onedrive link to the folder, which should contain a zip file named MSTSC6.3.zip


    Let me know if it works for you :)

    Thursday, August 2, 2018 7:51 AM
  • My apologies for submitting this to an "Embedded" thread but it was this thread that indirectly helped me to achieve a successful downgrade (thanks for the inspiration Jesper!)

    I was able to downgrade the mstsc client service on a 2016 server from 10.0 to 6.1 using the following steps.

    Build a win7 workstation, update it all the way, then uninstall these updates (uninstalling these gets you back to v6.1.7601.24514).


    The mstsc files in the win7 workstaion are:





    Create 2 folders on the win7 workstation to keep the sys32 and syswow files separate. 
    Copy the files above into the folders you created. 
    Next, zip the folders and copy the zip files to your win10 or server 2016 device.

    Now - for the downgrade process:

    1 - stop the 3 RDP services if any are running.
    2 - change the ownership to "local administrators group" on the 4 mstsc files in System32 and in SysWow64.
    3 - add full control permissions to the files you now own.
    4 - replace the original v10 files with the v6.1 files copied from the Win7 workstation.
    5 - register the DLL's (regsvr32 c:\windows\system32\mstscax.dll,  regsvr32 c:\windows\syswow64\mstscax.dll)
    6 - reboot
    7 - test

    I did this as a POC which turned out to be a success for an older Program i use to RDP into various devices.  The v10 mstsc files would cause the app to fail after about 10 concurrent desktops were opened.  I've been able to open more than 10 after the downgrade with ZERO failures!!  I've been able to RDP into the POC server without any apparent issues.

    I know this is an older thread, but this is something I had to figure out due the retirement of server 2008 and thought i'd share in hopes that it will help others that have a been searching for a "successful?" way to downgrade.

    I do not recommend doing something like this for a "production level" solution.
    This is something that works as a "for me" solution.

    If there's an easier way to do this, please reply.

    If there's a more appropriate thread for this - pleas let me know and i'll move it.

    • Edited by Mr.Jazz Wednesday, January 8, 2020 2:46 PM
    Monday, January 6, 2020 6:45 PM
  • Update:

    Feb 2020 updates pushed a new version of mstscax.dll - 10.0.14393.3503

    I had to revert back to my v6 dll.

    the other associated RDP files appear to be the v6 versions I added back in January.

    Appears to have worked without re-registering the v6 dll files.

    Monday, February 17, 2020 7:06 PM