The mstscax.dll errors you may see
Windows or an application may display one of these messages:
- “Could not load the Remote Desktop Services ActiveX control. Make sure mstscax.dll is in the path.”
- “The program can’t start because mstscax.dll is missing from your computer.”
- “mstscax.dll could not be loaded.”
- “
C:WindowsSystem32mstscax.dllis either not designed to run on Windows or it contains an error.” - Error status
0xc000012f - “The Remote Desktop Services ActiveX control (mstscax.dll) does not match the version of the client shell.”
mstscax.dll is a genuine Microsoft Windows component called the Microsoft Terminal Services Client Control. It belongs to Remote Desktop Services and is used by mstsc.exe, legacy Remote Desktop web features, and applications that embed Microsoft’s Remote Desktop ActiveX control.
The 60-second answer
Do not download an isolated copy of mstscax.dll. First install pending Windows updates, restart, and repair protected Windows files from an elevated Command Prompt:
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Restart Windows and test the built-in client:
mstsc.exe
If Remote Desktop Connection was intentionally removed on Windows 11 version 23H2 or later, reinstall the official Microsoft Remote Desktop Connection package that matches your system architecture. If only one third-party program fails, repair or reinstall that program instead.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
What mstscax.dll does
Microsoft documents the component as the MsTscAx class, a Remote Desktop ActiveX client. It provides functions used for starting and ending RDP connections, virtual channels, device redirection, and other client-control operations. The component is documented by Microsoft here.
The file is part of Microsoft Windows, not a general-purpose runtime. It is normally associated with:
- The built-in Remote Desktop Connection client,
mstsc.exe - Legacy Remote Desktop Web Connection pages
- RemoteApp-related tools
- Older RDCMan-era integrations
- Business or administration software embedding Microsoft’s ActiveX control
- Third-party applications that use Microsoft Remote Desktop components
It is generally unrelated to Visual C++ Redistributable packages, DirectX, .NET runtimes, graphics drivers, chipset drivers, or game-specific redistributables. A game or launcher can report the error if it embeds or invokes an RDP-related component, but reinstalling a random runtime is not a reliable solution.
Where Windows normally keeps the file
On a typical Windows installation, the native copy is under:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
%windir%System32
On 64-bit Windows, 32-bit Windows components may use:
%windir%SysWOW64
The names can be confusing. On 64-bit Windows, System32 is normally the native 64-bit system directory, while SysWOW64 contains 32-bit system components.
Both copies can exist because Windows supports applications built for different architectures:
- x64: native 64-bit Windows and applications
- x86: 32-bit applications running on 64-bit Windows or on 32-bit Windows
- ARM64: compatible Windows devices using ARM64 packages and components
Do not decide that a file is correct merely because it has the right name. A DLL can exist but still fail because it has the wrong architecture, belongs to a different Windows build, has a damaged dependency, or does not match the executable loading it.
Older Microsoft documentation also lists other locations in legacy or redistributed Remote Desktop deployments. The normal Windows system directories remain the safest places to investigate first. Microsoft’s historical file-location information is available in its Remote Desktop security update documentation.
What each error usually means
“mstscax.dll is missing” or “was not found”
The file may have been deleted, quarantined, damaged, or removed with an incomplete Remote Desktop uninstall. This message can also appear when the file exists but Windows cannot load one of its dependencies.
Start with Windows servicing rather than replacing the file manually.
“Could not be loaded”
This is a general loader failure. Possible causes include:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- A corrupt Windows component
- A wrong-architecture DLL
- A missing dependency
- An invalid entry point
- A private copy in an application folder
- A damaged ActiveX registration
- A mismatch between
mstsc.exeandmstscax.dll
The wording alone does not prove that the file is absent.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
“Not designed to run on Windows” or status 0xc000012f
This commonly indicates that Windows found a file but rejected its binary format or integrity. A bad replacement, incomplete update, failed servicing operation, or incompatible copy can produce this result.
Do not respond by downloading another copy. Repair the Windows component store and protected files first.
“Does not match the version of the client shell”
This specifically points toward a version mismatch between the Remote Desktop client shell, usually mstsc.exe, and the ActiveX control. It can happen after manually copying files, restoring an old backup, mixing packages, or incompletely reinstalling Remote Desktop.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Replacing only mstscax.dll is likely to preserve or worsen the mismatch. Restore the pair through Windows servicing or the official Remote Desktop installation package.
Fix 1: Install Windows updates and restart
A pending update can leave related Remote Desktop files at different servicing levels. Updating Windows is the least invasive repair.
- Press Windows + I to open Settings.
- Select Windows Update.
- Select Check for updates.
- Install every available Windows update.
- Restart the computer, even if Windows does not immediately require it.
- Open Windows Update again and check once more.
- Press Windows + R, type
mstsc.exe, and press Enter.
If Remote Desktop opens, connect to a test computer or use the application that previously failed. If the same error remains, continue with DISM and SFC.
Fix 2: Repair Windows with DISM and SFC
Microsoft recommends running Deployment Image Servicing and Management, or DISM, before System File Checker. DISM repairs the Windows component source that SFC uses to restore protected files. Microsoft’s procedure is documented here.
Run DISM
- Open the Start menu.
- Type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Approve the User Account Control prompt.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Wait for the operation to finish. It can remain at one percentage for a while.
A successful repair normally ends with a message indicating that the restore operation completed successfully. Restart if requested, then open an elevated Command Prompt again and run SFC.
Run SFC
sfc /scannow
Leave the window open until verification reaches 100 percent. Then interpret the result:
- Windows Resource Protection did not find any integrity violations: protected system files appear intact. Test
mstsc.exeand the affected application. - Windows Resource Protection found corrupt files and successfully repaired them: restart Windows and test again.
- Windows Resource Protection found corrupt files but was unable to fix some of them: continue to the log and recovery steps below.
- Windows Resource Protection could not start the repair service: restart Windows and retry from an elevated Command Prompt.
If you prefer help identifying which files changed instead of repeatedly hunting through Windows servicing output, Outbyte PC Repair can scan for reported system problems and show what needs attention; its full version performs the repair, while the scan is available without requiring the paid version.
Recommended Free Tools
If DISM cannot find repair files
DISM normally obtains repair content through Windows Update. If it reports that source files could not be found, do not copy mstscax.dll from a download site or a random computer. Use a matching Windows installation or repair source and follow Microsoft’s documented /Source and /LimitAccess procedure.
The source must correspond closely to the installed Windows edition, architecture, and build. A mismatched source can leave the component store in an inconsistent state.
If SFC reports a hash mismatch or cannot repair the file
Extract the relevant SFC entries:
findstr /c:"[SR]" %windir%LogsCBSCBS.log >"%userprofile%Desktopsfcdetails.txt"
Open sfcdetails.txt from the desktop and look for entries involving mstscax.dll or related Remote Desktop files. The log can distinguish a protected-file problem from a broader servicing failure.
Rank #3
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
If SFC repeatedly fails, other Windows files are also disappearing, or the problem returns after repair, investigate disk and file-system health, back up important data, and consider System Restore or an in-place Windows repair.
Fix 3: Reinstall Remote Desktop Connection officially
On Windows 11 version 23H2 and later, Remote Desktop Connection can be uninstalled. If the failure began after removing or reinstalling it, use Microsoft’s official package rather than extracting a loose DLL.
Microsoft’s current procedure is documented here.
Check whether Remote Desktop Connection was removed
- Open Settings with Windows + I.
- Select Apps.
- Select Installed apps.
- Search for Remote Desktop Connection.
- If it is listed, select its menu and choose Uninstall only if you are deliberately preparing for a clean reinstall.
- Restart Windows.
- Install the official Microsoft Remote Desktop Connection package matching the device.
Microsoft also documents this command-line uninstall:
mstsc.exe /uninstall
Use it only when following the official reinstall procedure. The official download is an installer containing setup.exe, not a replacement DLL.
Choose the package matching the Windows architecture:
- Windows 64-bit: use the x64 package
- Windows 32-bit: use the x86 package
- Windows on ARM: use the ARM64 package
After installation, restart Windows and run:
mstsc.exe
If the built-in client works but a particular application still reports the error, that application may be loading its own private copy. Repair or reinstall the application from its publisher and verify whether it is 32-bit or 64-bit.
Fix 4: Repair the application that reports the error
If mstsc.exe opens normally but a third-party program does not, the Windows copy may be healthy. The application could have a damaged installation, an incompatible embedded control, or a private DLL in its own folder.
Try the application’s repair option first:
- Open Settings.
- Select Apps.
- Select Installed apps.
- Select the affected program.
- Choose Advanced options, if available.
- Select Repair.
- Restart the application.
If no repair option exists, uninstall and reinstall it using the vendor’s official installer. For a game or launcher, use its built-in Verify, Repair, or equivalent function. There is no verified reason to install a game-specific redistributable to obtain mstscax.dll.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteIf the problem affects only one Windows user profile, test the same application from another profile. A difference between profiles can point to per-user COM or browser registration rather than damaged system files.
Fix 5: Use regsvr32 only for a legacy ActiveX problem
mstscax.dll is a COM/ActiveX control, so registration can matter in old Remote Desktop Web Connection scenarios. Microsoft documents this procedure for legacy troubleshooting:
%windir%System32regsvr32 mstscax.dll
Use it only when all of these are true:
- The file exists in the expected Windows directory.
- The failure concerns a legacy Remote Desktop ActiveX control or web workflow.
- Windows is able to read the file.
- You are following the applicable Microsoft procedure.
To run it:
- Open Start.
- Type
Command Prompt. - Right-click it and select Run as administrator.
- Run the command above.
- Look for a confirmation that registration succeeded.
- Restart the affected legacy application or browser workflow.
regsvr32 is not a general missing-DLL repair. It cannot fix a missing file, damaged binary, wrong architecture, broken dependency, component-store corruption, or a mismatch between mstsc.exe and mstscax.dll. Modern Windows 10 and Windows 11 Remote Desktop launches normally do not require this step.
Microsoft’s legacy troubleshooting guidance is available here.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- Video Link to instructions and Free support VIA Amazon
- Great Support fast responce
- 15 plus years of experiance
- Key is included
Fix 6: Check security software quarantine
If the file disappeared immediately after an antivirus detection or cleanup operation, inspect the security product’s protection history.
- Open Windows Security.
- Select Virus & threat protection.
- Select Protection history.
- Look for an event involving
mstscax.dll. - Confirm that the detected path is a Windows system path.
- Check that the file is digitally signed by Microsoft before restoring it.
- Run Windows Update, DISM, and SFC after restoration.
Restore a quarantined file only when you are confident it is the original Microsoft Windows component and the detection is a false positive. Do not disable security protection merely to install a downloaded DLL.
If the file is restored but fails with a version or format error, let Windows servicing replace it instead of keeping the quarantined copy.
Fix 7: Check architecture and version matching
A 32-bit application may need the 32-bit control, while native 64-bit software needs the 64-bit control. On a 64-bit Windows installation, both system paths may therefore contain related components.
Do not:
- Copy an x86 file into the native 64-bit location.
- Copy an x64 file into a 32-bit application directory.
- Replace a Windows file with one from another edition or build.
- Replace only
mstscax.dllwhile keeping a different-versionmstsc.exe. - Assume that a file’s size proves it is correct.
Historical Microsoft servicing data lists several versions and sizes for different Windows releases and architectures, but those values are not a complete current inventory. Exact values vary with Windows build and cumulative updates. The important match is between the installed Windows servicing level, architecture, mstsc.exe, and mstscax.dll.
To identify your system type:
- Open Settings.
- Select System.
- Select About.
- Check System type.
For a detailed file check:
- Open File Explorer.
- Enter
%windir%System32in the address bar. - Locate
mstscax.dll. - Right-click it and select Properties.
- Review the Details and Digital Signatures tabs.
These properties do not replace Windows integrity checks, but they can reveal an obviously old, unsigned, or manually copied file.
Fix 8: Check Windows Features only for legacy workflows
Modern Remote Desktop Connection is not repaired by randomly enabling Windows features. The Windows Features dialog does not provide a general-purpose replacement for a missing mstscax.dll.
For legacy web-based workflows, you can inspect available features:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Press Windows + R.
- Type:
optionalfeatures
- Press Enter.
- Review the available Windows features.
- Apply only a feature required by the documented legacy application.
- Restart if Windows requests it.
Windows 11 does not provide the old Internet Explorer experience used by many historical ActiveX instructions. Do not enable unrelated browser or compatibility features expecting them to install the current Remote Desktop client control.
Should you reinstall a graphics or network driver
Usually, no. mstscax.dll is an RDP client component, not a graphics, network, or chipset driver. A driver can cause connection, display, audio, or redirection problems after Remote Desktop starts, but reinstalling a driver normally does not restore this DLL.
Check drivers only when the DLL error is accompanied by separate device symptoms:
- Right-click Start.
- Select Device Manager.
- Expand Display adapters, Network adapters, or the device category showing a warning icon.
- Right-click the affected device.
- Select Properties and review Device status.
- Use Update driver or install a driver supplied by the device manufacturer.
- Restart Windows and test again.
If manually identifying which of many device drivers is stale is taking longer than expected, Outbyte Driver Updater can scan and identify reported driver problems; its free scan shows the findings, while driver installation is handled by the full version. It is not a substitute for DISM, SFC, or an official Remote Desktop reinstall when mstscax.dll itself is damaged.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Do not download a loose mstscax.dll
Random DLL download sites create several risks:
- The file may contain malware or unwanted modifications.
- It may be unsigned or falsely labeled.
- It may be the wrong x86, x64, or ARM64 architecture.
- It may belong to a different Windows build.
- It may not include a required dependency.
- It can create a version mismatch with
mstsc.exe. - It may conceal the underlying component-store or disk problem.
The safe sources are Windows Update, DISM and SFC, the official Microsoft Remote Desktop Connection installer, and the repair or reinstall process for the affected application. Do not copy the file from another PC unless it has the identical Windows edition and build and you have verified the file through an appropriate Microsoft-supported recovery process.
When to use System Restore or Windows recovery
System Restore is reasonable when the error began immediately after a Windows update, cleanup utility, antivirus action, or failed installation and a suitable restore point exists.
- Open Start and search for Create a restore point.
- Open it.
- Select System Restore.
- Choose a restore point dated before the failure.
- Review the affected programs.
- Start the restore and allow Windows to restart.
System Restore is not guaranteed to recover a file deleted outside protected Windows servicing. If DISM, SFC, the official Remote Desktop reinstall, and rollback all fail, perform an in-place Windows repair or use a managed recovery process after backing up personal data. Continued manual DLL replacement is less reliable than repairing the operating system as a whole.
Quick diagnostic checklist
Before escalating, confirm the following:
- Windows Update has completed and the PC has restarted.
- DISM completed without an unrepaired component-store error.
sfc /scannowcompleted and its result was reviewed.mstsc.exewas tested independently.- The affected program was repaired or reinstalled if only it fails.
- The file architecture matches the program and Windows installation.
mstsc.exeandmstscax.dllwere not mixed from different systems.- Antivirus quarantine was checked.
- Legacy
regsvr32registration was used only for an applicable ActiveX problem. - CBS logs were reviewed if SFC could not repair the file.
- Disk health and backup status were checked if files keep becoming damaged.
A DLL loading error does not necessarily indicate a faulty remote server, network connection, graphics adapter, or RDP credential. First restore the local Windows component and its matching client files. Once mstsc.exe starts normally, diagnose connection and authentication problems separately.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
