Using 32-bit mstsc.exe on Windows 10

  1. Posts : 3
    Windows 8.1

    Using 32-bit mstsc.exe on Windows 10


    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:
    @echo off
    set WinDir=
    start C:\Windows\SysWow64\mstsc.exe
    Now on Windows 10 it doesn't work anymore. 32-bit mstsc.exe starts for few miliseconds just to launch mstsc.exe from System32.
    When I copied mstsc.exe from SysWoW64 and paste it to System32 it ends up with a infinite loop of starting System32 mstsc.exe (now 32-bit but this one again tries to open the one from System32 and it goes forever).
    The only one possibility to do it is to rename mstsc.exe from System32 to other one and then, when mstsc.exe from SysWow64 can't find mstsc.exe in System32 it runs itself.

    However this solution is not suitable for me. I would like to do it with a batch so I wouldn't have to set it up manually on every PC I would like to use it.

    Did some one find a way to do it?
      My Computer

  2. Posts : 3
    Windows 8.1
    Thread Starter

    One year later and we still don't have solution for this problem...
      My Computer

  3. Posts : 1,249
    Windows 10 Pro

    Why do you need to run the 32 bit version of mstsc.exe?

    When the 32 bit version starts it checks if it is running on a 64 bit OS. If so it will look for a 64 bit version in system32 and run it if present. The 32 bit version will then terminate. This is done within the 32 bit version and is beyond user control. That is how it works in Windows7, presumably the same in Windows 10. The 32 bit version is the same in either a 32 or 64 bit OS.

    Other than renaming or removing the 64 bit version I don't see how to run the 32 bit version.
      My Computer

  4. Posts : 3
    Windows 8.1
    Thread Starter

    Our 32-bit C++/MFC product uses VirtualChannel functionality of RDP and we have 32-bit DLL loaded for this purpose (it shares common libraries with product apps) and it is registered in registry under ...\Software\Microsoft\Terminal Server Client\Default\AddIns. Mstsc.exe automatically loads DLL's when you put them there. Previously (before Windows 10) it wasn't beyond user control because there was this solution mentioned in first post. Since Windows 10 it stopped working. Currently there is no chance to migrate to x64 because it would take hundreds of hours to do so (mainly because mentioned DLL and APPs share common libraries so every app would have to be migrated - and that's few gigabytes of source code). I hope now you can understand our problem.
      My Computer


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:31.
Find Us

Windows 10 Forums