Opening a command prompt in Windows 7 and running any command results in error messages such as the ones below (in this case a dir command):01/28/2010 09:06 AM The system cannot find message text for message number 0x2373 in the message file for Application. Windows The system cannot find message text for message number 0x2378 in the message file for Application. The system cannot find message text for message number 0x2379 in the message file for Application.For other commands it references "System" rather than "Application" in the error message. I've seen other posts online describing the same behavior linked to the copies of Win7 distributed at the Gartner Symposium in October as part of the general availability announcement (this is where I got my copy). Any help or suggestions would be appreciated.

Hi,You're getting those messages because you're running the CMD.exe from a folder different than what's defined in the %COMSPEC% environment variable. If you want to open a command prompt to a specific folder you can right-click and pick "Open Command Window Here" (built into Vista and 7). It's extra slick because if you do it on a network share Windows will automatically map a drive letter to it for you. Right-click on the folder C:\windows\system32 on your machine while holding down the shift key. You'll see an extra context-sensitive menu item there: Open Command Prompt here. Just click on this menu and a command window will open with the current working directory set to the folder's actual location. Another option is to make a new CMD shortcut. Make a new shortcut, enter %COMSPEC% as the Target, and give it a name you'd like. Once it's created, edit the shortcut and change the "Start in" path to where you'd like the command prompt to open to.

Hi, It's far more subtle then that: 0) I have created (and then uncreated) the same problem by trying to run a RENAMED copy of CMD.exe from ...\system32 under win 7. ------ 1) In an effort to work around Win 7's "magnificent" user access controls, I have tried to create TWO separate links to the command prompt, and PIN them to my START menu: The first runs as a USER (red background) and the second runs as an ADMINISTRATOR (blue background). 2) This was necessary because when CMD is run as a standard user (from an admin account) it cannot access system areas. On the other hand, when launched as an admin, it cannot accept drag&dropped file paths. This inconsistency is a terrible nuisance for all apps. 3) The first attempt was to simply create TWO separate links to a single CMD.exe, set one for ADMIN and the other for USER, color-code the window background so I could easily tell which is which, and then PIN them to the START menu. 4) The problem was that Windows 7 "De-references" the links during the PIN process, and does not allow you to PIN both shortcuts, even if they are setup differently, IF they point to the SAME target. -- 5) I therefore created two additional copies of CMD.exe = CMD_User.exe = CMD_Admin.exe, Created separate shortcuts to each, configured the properties, and PINNED them to the START menu. 6) Everything worked fine, until I tried to execute a simple DIR command, and got the weird MESSAGE ERROR above. 7) Launching the original CMD.exe works just fine. Launching the identical but renamed CMD causes the error. -- Any ideas how to work around this ?! BTW, I do wish Microsoft made cars and SUV's, nobody would drive them, we could prevent climate change, save the planet ... everybody would walk !!!! MJS.