Runas Command Does Not Work with UPN Name

This article was previously published under Q272472
This article has been archived. It is offered "as is" and will no longer be updated.
After you install Microsoft Windows 2000 Service Pack 1, the runas command may not work correctly (whether you use the command from a command prompt or in a script).

If you use a user principal name (UPN) name, such as,, the program starts successfully, but when the program initializes you may receive the following error message:
Microsoft Visual C++ Runtime Library
Runtime Error!
Program "path to executable"
abnormal program termination
If you use "plain" user names, the behavior on standalone computers is the same as for UPN names. On domain members and domain controllers, the runas command generates the following error message:
RUNAS ERROR: Unable to run - "command"
1326: Logon failure: unknown user name or bad password.
You may experience these issues with tools such as Ntbackup.exe or Mmc.exe that are used by administrative consoles.
The runas command uses the TranslateName function to convert the user name syntax to the domain\user syntax if necessary. The value that is returned from the TranslateName function is used to grant desktop access to the user. If this does not work, the user does not have access to the desktop and the program does not start.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
   Date        Time    Version        Size     File name   --------------------------------------------------------   12/18/2000  01:05p  5.0.2195.2778  357,648  Advapi32.dll				

To work around this problem, you can use the domain\user syntax for both UPN names and plain user names. On standalone computers or when you want to use a local account on a domain member, use the computer name as the security principal. For UPN names, use the down-level domain name and the down-level user name.

For domain members and domain controllers, the supported formats for user names are domainname\username and UPN name. 'Plain' names are not supported in this configuration if the intent is to run Runas with domain credentials.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

Article ID: 272472 - Last Review: 10/21/2013 00:59:22 - Revision: 3.4

  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Service Pack 1
  • kbnosurvey kbarchive kbbug kbfix kbwin2000presp2fix kbqfe kbhotfixserver KB272472