This article will show you how to resolve error 0x2350 or 0x2331 after you renamed cmd.exe or any other application file in System32 folder.
What a pleasure to resolve a long standing problem. And not by an accident. No. But by applying a heavy-duty problem-solving pressure tactic. This is gold, Jerry, gold! Can I use it?
At some point you are so fed up with a problem, you are ready to tackle almost anything.
Ever since Vista and Windows 2008 Server, if you rename cmd.exe for security reasons, you wouldn’t be able to see any feedback messages in a Command Prompt console, and what is even worse, you wouldn’t see any error messages.
Instead all you see is something like this depending on version of your Windows:
The system cannot find message text for message number 0x2350 in the message file for Application.
The system cannot find message text for message number 0x8 in the message file for System.
The system cannot find message text for message number 0x2331 in the message file for Application.
The solution is very simple. Let’s say that your renamed CMD.EXE into YourCMD.EXE. To get the messages in Command Prompt back, navigate to %WinDir%\System32\en-US directory and copy file cmd.exe.mui. Name a new file YourCMD.exe.mui.
If you are using x64 system (most of us do today), also rename file WinDir%\SysWOW64\en-US\cmd.exe.mui
That is it. Now you got your console messages and errors back:
The problem was that starting from Vista all the text messages are compiled into a separate file, and system would search for a message file with your new CMD name and would not be able to find it.
To make your custom Command Prompt shortcut with Run as administrator option checked to open at C:\, you need to use this command:
%ComSpec% /k cd C:\
To point your %ComSpec% to your new custom CMD you need to run this registry command:
REG ADD “HKLM\System\CurrentControlSet\Control\Session Manager\Environment” /v ComSpec /t REG_EXPAND_SZ /d ^%SystemRoot^%\system32\YourCMD.exe /f