Remote Desktop Connection Client

No Screenshot

Submit Screenshot
Windows 7 x32, Windows Server 2008 R2 x64

Application Details:

Version: 6.1.7600.16385 x32
License: Retail
Votes: 4
Latest Rating: Bronze
Latest Wine Version Tested: 1.7.51

Maintainers: About Maintainership

Link KB969084 Free Download KB969084 for Windows XP

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Able to launch application, change options

Able to connect to Windows Server 2003 and Windows Server 2008 (logon screen)

Application remembered last user logged in

Able to authenticate to Server 2003 and navigate desktop

All applications seem to work under 2003

What does not

Authenticate to 2008 and 2008 R2

Connect to remote desktop on 2008/R2


What was not tested

Save RDP file

Hardware tested


  • GPU:
  • Driver:

Additional Comments

Wasnt able to install (installer said was already installed). Extracted from EXE with /extract copied files to system32 had had to make an en-US folder in system32 folder and copy MUI files

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowGentoo Linux x86_64Sep 10 20151.7.51No, but has workaround Yes BronzeNathan Shearer 
ShowUbuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)Dec 06 20121.5.18No, but has workaround Yes Bronzekenjiru 
CurrentDebian GNU/Linux Unstable "Sid" x86_64Mar 21 20121.5.0No, but has workaround Yes Silveran anonymous user 

Known Bugs

Bug # Description Status Resolution Other apps affected
32384 MSTSC (Remote Desktop) 7.0 hangs when connecting through RD Gateway RESOLVED ABANDONED View
32385 MSTSC (Remote Desktop) 7.0 drawing issues UNCONFIRMED View
52215 MSTSC (Remote Desktop) 7.0 cannot find its MUI files when Windows version is set to 7 UNCONFIRMED View

Show all bugs

HowTo / Notes

HOWTO: Make RDP-Client work under wine
To get it running under Wine you need a Windows 7 pc available.

To make Remote Desktop Connection 7 work under Wine, you will need to copy four files from your Windows system.
  1. mstc.exe, Folder: C:\WINDOWS\system32\
  2. mstscax.dll, Folder: C:\WINDOWS\system32\
  3. mstsc.exe.mui, Folder: C:\WINDOWS\system32\_locale_
  4. mstscax.dll.mui, Folder: C:\WINDOWS\system32\_locale_
The folder called C:\WINDOWS\system32\ you will find in the Windows-System.
The files from the C:\WINDOWS\system32\_locale_ are necessary for a localized GUI, e.g. it talks to you in your language. This files reside in a subfolder of C:\WINDOWS\system32\. The _locale_ is a place marker for your locale language settings.

As an example take this for Argentina:
search for C:\WINDOWS\system32\es-ar\

Copy the above four files to some temporary directory on your Linux machine.

On your Linux machine create a new Wine Windows XP Bottle. To choose the right windows version use winecfg from the commandline. There will be a dropdown to set the right windows version. Set it to Windows XP.

Use your linux file manager to Browse to the Wine bottle C: Drive subdirectories that match those above.

Copy all 4 files to their respective matching subdirectory in Wine.

After you have done that I would reboot the bottle.

Finally to start Remote Desktop Client v7 you will need to have wine execute the Windows RDC 7 executable (mstsc.exe).

Open a terminal and at the command prompt execute the following (make sure you are using the same "bottle":

wine mstsc.exe

You should then see the RDC 7 client app appear prompting you for Server Address and Login.


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Error when running wine mstsc.exe
by Alex Chapin on Tuesday November 4th 2014, 21:45
I get the following error:

err:process:create_process L"C:\\windows\\system32\\mstsc.exe" not supported on this installation (x86_64 binary)
wine: Bad EXE format for C:\windows\system32\mstsc.exe.

I have Ubuntu 14.04 32 bit and wine 1.7.28. Do I need to change something in the registry, that part wasn't clear to me.
RE: Error when running wine mstsc.exe
by Joerg Schiermeier on Saturday December 27th 2014, 12:39
You will have to use the same bitness than mstsc.exe:

if you take the mstesc.exe from a 32bit system you only can use the 32bit wine folder: e.g. ~/.wine. Maybe you need to add WINEARCH=win32 when you run the mstsc.exe:

env WINEARCH=win32 wine /path/to/mstsc.exe

Nothing to change in the registry.
And this: the file command (see there: is your friend.
Does this work under 14.04?
by Brian Legg on Thursday August 7th 2014, 16:40
I have tried and cant seem to get this to find the exe no matter what i do.

support@CLA-NUC4-Woodlands:/home/classica-user/Downloads$ wine mstsc.exe
No protocol specified
No protocol specified
No protocol specified
wine: cannot find L"C:\\windows\\system32\\mstsc.exe"
support@CLA-NUC4-Woodlands:/home/classica-user/Downloads$ No protocol specified
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:systray:initialize_systray Could not create tray window
RE: Does this work under 14.04?
by Joerg Schiermeier on Thursday August 7th 2014, 16:58
Did you read the HowTo here?
Did you have an original Windows?

For this
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:systray:initialize_systray Could not create tray window
please file a bug report in wines bugtracker.
RE: Does this work under 14.04?
by Brian Legg on Thursday August 7th 2014, 20:43
I did read the how to, but am not sure of a few things.
First we are running 14.04 in x64 and Wine 1.7 (was 1.6)
should I use an xp with x64 files?

Second, your comments about modifying the registry to make the installer think it was windows xp sp3,
In the registry I see syswow64 does that mean the registry inside wine is a 64bit. How did you trick the installer, because every time I tried to install the x86 it said I had the wrong hardware platform.
When I tried the x64 version... WindowsServer2003.WindowsXP-KB925876-v2-x64-ENU thru the installer it said path not found.

Should I just copy the files to the hidden .wine c:\windows\system32 and c:\windows\system32\en-US directories?

Any help is greatly appreciated.
TS Gateway
by Turio on Wednesday February 12th 2014, 12:17
I read in the "Test Results": "I was also able to activate the RD Gateway option in the Advanced tab by modifying the registry."

What is the solution? How can I activate the RD Gateway option?
Thanks a lot...
RE: TS Gateway
by grinchon on Wednesday March 5th 2014, 14:28
I have the same problem, very nice thing to obtain a detailed explanation of modifications to do in the registry in order to activate the RD Gateway option.
Sorry for my awful english !
Thanks a lot !

grinchon at
Create XP Bottle?
by Richard Raseley on Thursday July 21st 2011, 22:41
It is unclear from your post what you mean by "create a Windows XP bottle" - can you explain more? When copying the files to the virtual wine C drive (in the specified locations), adding the mstsc.exe application via the Wine interface, the executing "wine mstsc.exe" I get the following error:

fixme:advapi:RegisterTraceGuidsW (0x1044843, 0x1066058, {0c51b20c-f755-48a8-8123-bf6da2adc727}, 1, 0x32fdd8, (null), (null), 0x1066060,): stub
fixme:shell:SetCurrentProcessExplicitAppUserModelID L"Microsoft.Windows.RemoteDesktop": stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:module:load_library unsupported flag(s) used (flags: 0x00000022)

Any assistance would be appreciated.

RichardRaseley GMail com
RE: Create XP Bottle?
by Joerg Schiermeier on Monday November 28th 2011, 20:35
> what you mean by "create a Windows XP bottle":
run from the commandline winecfg and choose *Windows XP* als windows version.

> I get the following error:
> fixme:shell:SetCurrentProcessExplicitAppUserModelID
> ..

As you can read there, this is a so called *FIXME*, far away from an error. Either you will implement the missing function this message indicates or you simply ignore this.

Did you see the GUI (Interface)? If so, it works.
Connect from anywhere option broken
by JKrizzle on Monday February 21st 2011, 16:57
Under the Advanced tab, reads:

"Connections using a gateway server are not supported by your system configuration."
RE: Connect from anywhere option broken
by Nigel Shindler on Friday September 9th 2011, 14:25

I have had the same error message trying to make this work, but as it seems to imply the possibility of a fix at the client side, I wondered whether you've made any progress with it?

I'm running Ubuntu 10.04, on a rather elderly Toshiba Satellite laptop.


RE: Connect from anywhere option broken
by Joerg Schiermeier on Monday November 28th 2011, 20:38
Did you have a serious reason to run this RDP-client? Please read the general description of this RDP-Client:
RE: Connect from anywhere option broken
by W Thomas Jones on Wednesday October 10th 2012, 10:33
The functionality that is broken here is not implemented in any of the open source rdp clients, they don't support Terminal Services Gateway.