Member Avatar for gianus

mstsc doesn't start anymore, after windows update with the message
cannot find c:\windows\system32\<LANG_NAME>\mstsc.exe.mui

if I restore the system with a point before 11/08/2010, it works.

  • 2 Contributors
  • 2 Replies
  • 245 Views
  • 2 Months Discussion Span
  • Latest Post Latest Post by gianus

Dani AI

Generated

A short expert note that complements the thread and explains why the symptom happens and what to try next.

The missing file is a language/resource MUI for Remote Desktop. When Windows reports it cannot find the mstsc.exe.mui in the system MUI folder, the Remote Desktop client will fail to start. The fact that a System Restore to a point before 11/08/2010 fixed the problem (as reported by ) strongly suggests an update replaced or removed the MUI for the installed language.

's idea of using a separate folder can work in some edge cases, but often fails because the Windows MUI loader prefers the system language subfolder and will still look there regardless of shortcut location. The $NtServicePackUninstall$ folder exists only when uninstall payloads were kept, so it may be absent on many systems — that explains the missing source files for some machines.

Suggested troubleshooting sequence (in order of least to most intrusive):

  • Run System File Checker from an elevated command prompt to restore missing/corrupt system files:

    sfc /scannow

  • If SFC reports problems it could not fix, run the Windows 7 System Update Readiness tool (CheckSUR) or reapply Windows Update, then re-run SFC.

  • Search the machine for any existing mstsc.exe.mui copies and verify language and file version. If a manual copy is needed, obtain the file only from an identical Windows 7 edition and service-pack level; placing a mismatched MUI can break behavior.

  • Inspect Event Viewer and the CBS log for side-by-side or MUI load errors to narrow the cause.

  • If all else fails, use the previously successful System Restore or perform an in-place repair (repair install) to restore all system MUI files safely.

Cautions: avoid mixing builds or service-pack levels when copying system files; mismatched .mui files cause subtle failures. The above explains why copying executables into an arbitrary folder often did not help : the MUI lookup and system versioning must match the OS.

Recommended Answers

All 2 Replies

Member Avatar for kristain

Stop the process mstsc.exe
- Created a new folder "RDP" in %windir%
- Copy "mstsc.exe" and "mstscax.dll" from "C:\Windows\
$NtServicePackUninstall$" to this folder
- Copy the folder "en-US" "from C:\Windows\System32" to this folder
- Copy the "mstsc.exe.mui" and "mstscax.dll.mui" from "C:\Windows\
$NtServicePackUninstall$" to "C:\Windows\RDP\en-US"
- Change RDP shortcut to ""C:\Windows\RDP\mstsc.exe"

Member Avatar for gianus

First of all, I cannot find
C:\Windows\$NtServicePackUninstall$
Anyway, Ican find in three folders the files You say, but they are all the same date, same size
Moving those files in those folders, it doesn't work. Same error.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.