Running 32-bit Remote Desktop Connection on Windows 64 bit

On Windows Vista 64 and Windows 7 64, there is a 32 bit version of Remote Desktop Connection (Microsoft Terminal Services Client, mstsc.exe) in %SystemRoot%SysWOW64. Running this mstsc.exe will launch the 32 bit process but it will instantly launch the 64-bit mstsc.exe from System32 and shut itself down. This makes it impossible to run Remote Desktop Connection 32 bit. This is a problem when you have 32 bit Terminal Services add-ins (which won't run under 64 bit).

Solution: Rename the 64-bit mstsc.exe from System32 to prevent it from replacing the 32-bit process.

Open an elevated command prompt or PowerShell session and run the following:

Microsoft.Playwright.PlaywrightException: Error: The language "cmd" has no grammar.
    at Object.highlight (http://127.0.0.1:41899/main.js:3978:11)
    at eval (eval at evaluate (:226:30), :2:18)
    at UtilityScript.evaluate (:233:19)
    at UtilityScript. (:1:44)
   at Microsoft.Playwright.Transport.Connection.InnerSendMessageToServerAsync[T](ChannelOwnerBase object, String method, Dictionary`2 dictionary, Boolean keepNulls) in /_/src/Playwright/Transport/Connection.cs:line 209
   at Microsoft.Playwright.Transport.Connection.WrapApiCallAsync[T](Func`1 action, Boolean isInternal) in /_/src/Playwright/Transport/Connection.cs:line 535
   at Microsoft.Playwright.Core.Frame.EvaluateAsync[T](String script, Object arg) in /_/src/Playwright/Core/Frame.cs:line 548
   at SiteGen.Extensions.Markdown.Prism.PrismHost.Highlight(String source, String language)
   at SiteGen.Extensions.Markdown.Prism.PrismCodeBlockRenderer.Write(HtmlRenderer renderer, PrismCodeBlock obj)

This is simple if you have rights to rename that file. If you're on NTFS you may get a “You require permission from TrustedInstaller to make changes to this file” error. To get by this error, you can take Ownership of the file and give yourself full permissions.

1. Browse to %SystemRoot%System32
2. Right click mstsc.exe and choose Properties
3. Go to the Security tab
4. Click Advanced
5. Go to the Owner tab
6. Click Edit
7. From the "Change owner to:" list, choose your user name
8. Click OK
9. Go to the Permissions tab
10. Click Change Permissions
11. Click Add
12. Enter your user name and click OK
13. Tick the box in the Allow column for Full control
14. Click OK
15. Click OK
16. A Windows Security warning will come up; click Yes to proceed
17. Click OK

Now, you can rename the file mstsc.exe to something like mstsc.exe.bak Then, you can launch mstsc.exe from %SystemRoot%SysWOW64 and you will have 32-bit Remote Desktop Connection running.