Windir System32 Mstsc Exede

Learning has never been so easy!
  1. Windows Cannot Find %windir% System32
  2. Windir System32 Mstsc Exede Service

Anyone connecting via RemoteApp and Remote Connection Gateway will receive the following error when attempting to connect to a remote desktop:

“Your computer can’t connect to the Remote Desktop Gateway server. Contact your network administrator for assistance.”

This applies to Win10 users after receiving the creators update.
I beleive this problem only exists if the remote gateway app is hosted on Server 2008R2.

Steps below should resolve the issue. It's a workaround however, and you will NOT be using the latest version of the MS RDC client after completion.

4 Steps total

Step 1: Here is the error message

Step 2: Locate Files

The Windows update replaced two key files which cause the issue.
We need to replace them.

They are located in
%windir%system32

The system cannot find the file specified. C: WINDOWS system32 NAME mstsc.exe.MUI I have a Dutch Windows version. The file mstsc.exe.MUI is available in C: Windows System32 nl-NL. It was not available in C: Windows System32 nl but after I copied it over I still get the same message. Hello, I need to use mstsc.exe from SysWoW64 folder (so 32-bit one). Previously (up until Windows 8.1) I used a small batch to do it: Code: @echo off set WinDir= start C: Windows SysWow64 mstsc.exe/quote Now on Windows 10 it doesn't work anymore. 32-bit mstsc.exe starts for few miliseconds just to launch mstsc.exe from System32.

and they are called:
- mstsc.exe
- mstscax.dll

Step 3: Change File Permissions & Rename

Now you have located the files, you will need to rename them.
Windows will prevent you doing this, so you will need to take ownership of the files first, and then grant the local user full RW permissions.

Windir System32 Mstsc Exede

Once you have done this, rename them as:
- mstsc.exe.BAK
- mstscax.dll.BAK

Step 4: Replace With Older Versions

After the Creator's Update - you should find a folder on your main OS drive called Windows.old.

Open this up and browse to system32 directory.
Find the files with the same name again:
- mstsc.exe
- mstscax.dll

And copy them over to %windir%system32

This should resolve the issue. It's a workaround however, and you will NOT be using the latest version of the MS RDC client after completion.

Windows Cannot Find %windir% System32

7 Comments

Windir System32 Mstsc Exede Service

  • Chipotle
    Howard8569 Apr 21, 2017 at 06:05pm

    Thank you for that one i can see that being an issue. Wonder if Microsoft will have a fix for it.

  • Cayenne
    ManyHats08 Apr 21, 2017 at 06:12pm

    MS fix is to dump that ancient 08r2 server. You need to have everything on at least 12r2 and in their cloud. Did you not get the cool aid?

  • Chipotle
    Howard8569 Apr 21, 2017 at 06:14pm

    Nope stepped out of line for the cool aid took beer instead ;)

  • Datil
    Theborgman77 Apr 22, 2017 at 02:36pm

    This is fix is only needed if you have not correctly setup your RDC broker/gateway. Lots of people do this on purpose to skirt license requirements. It can also happen if you upgraded from 2003 terminal services.

  • Cayenne
    Lumpyone Apr 22, 2017 at 07:02pm

    Not seen this yet, but thank you. I'll be on the look out for it.

  • Datil
    CrimsonKidA Apr 23, 2017 at 07:43pm

    Haven't been able to get my Surface 3 to install the creator's update...from what all in reading (it also breaks RSAT, at least for some) that might not be such a bad thing!

  • Pimiento
    eamonndempsey Apr 24, 2017 at 10:14pm

    I have the creators update but no Windows.old folder. Any idea how I can get the older version? The version of mstsc.exe & mstscax.dll in the system32 folder is 10.0.15063.0.

    Any help gratefully received

Posted on