Windows 7 Command Prompt Message Errors (cmd.exe)

Question

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.

Answer 1

Explorer has never really been able to accept drag-dropped files from multiple users very well, i.e., dragging a file from a window from a user-opened folder into an admin-opened folder.  It can be done though with a hack.  What I have been able
to do in the past, as a workaround, is hot-login.  Hot-login is as opposed to warm-login in which is logging off Explorer and logging back in as a different user, or cold-login which is rebooting the system.  It is considered a hack by most Microsoft
professionals though is useful.
To hot-login, then, while logged in as a user use the Task Manager to stop the "explorer.exe" process.  This will close all Explorer windows and cause your taskbar and you desktop icons to disappear, but you will still have other applications running,
such as your Cmd windows.  Note that due to the user's credentials on that machine, you may need to do this using PsKill (part of PsTools, now a Microsoft Product), using the admin Cmd window itself.  After doing that, immediately run explorer.exe
from the admin Cmd window before Explorer has a chance to rerun itself (usually several seconds, though it might never come back by itself).
Doing that should now load the taskbar and desktop back, and they may look different if you previously had them customized.  This is because Explorer is now running as admin, as if you had logged into Windows as the admin account.  But, part of
the OS is also still running as the user, such as the server and workstation services, so you may, perhaps, be able to drag-drop files between users interchangeably, at that point.  In the least, running Explorer as admin has its enough advantages, in
some roles (like server administration), to be useful in and of itself.
This all may of course change after enough updates to Windows security.
Oh -- to access the user-specific desktop icons which are now gone from the actual desktop, find its icons in the respective subfolder in the \Users\ folder on the system drive and use them from there.  It should in a \Desktop\ folder right in the respective
user folder.  User-specific Quick Launch icons from the taskbar are probably in AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\, from the respective user folder. 
Now again, this is a hack that I'd use as an Active Directory administrator.  It is only needed once per Windows session, usually in conjunction with an AD admin account I had, as logged in and running Cmd via RunAs.  Local administrator accounts
function the same way with this process.  I don't expect Microsoft to officially endorse this process, so consider it from one power user to the next as the need arises.