Troubleshooting
STEP 1. Make sure you are using the latest version. The version number is shown on the first line of the helpscreen by entering SANUR/?. You'll also find it on the Version tab, by right-clicking SANUR.EXE and choosing properties. BE SURE TO DELETE ANY EARLIER VERSIONS.

STEP 2. DO NOT, I repeat, DO NOT use Sanur until you have confirmed that your Runas command works ok when you manually enter the password.

STEP 3. Because Runas uses stdout to display errors, any errors that Runas prints will be piped into Sanur. Therefore if you are having problems getting Sanur to work, add >&2 to the end of the Runas commandline so you can see any Runas error messages, for example:-

runas /u:domain\username program.exe >&2 | SANUR password

STEP 4. Temporarily change the password of the account you are trying to use to Password456, (or something equally simple using ONLY ASCII characters in the range 0-9, A-Z and a-z). If Sanur now works then this confirms that Sanur is not 100% compatible with your system and you now have three choices:-

• Only use passwords containing ASCII characters in the range 0-9, A-Z and a-z.
• Find an alternative to Sanur.

Common Runas Mistakes
The commandline that Runas is to execute must be quoted if any parameters are being used (this is nothing to do with Sanur). For example, the first example is wrong, the second correct:-

wrong ==> runas /u:domain\username cmd /k dir /s | SANUR pa55w0rd

correct ==> runas /u:domain\username "cmd /k dir /s" | SANUR pa55w0rd

Note in the example above there is a space between cmd and /k. Without that space, Runas will try to execute a program named cmd/k.

If the program's name, path or any of its arguments need quoting, then these quotes must be escaped using a backslash for Runas to interpret them correctly (again, this is nothing to do with Sanur). For example:-

runas /u:domain\username "\"c:\program files\prog\" \"my file.txt\"" | SANUR pa55w0rd

And finally, bear in mind that processes started by Runas will (most likely?) start from the system32 folder (typically c:\winnt\system32 or c:\windows\system32). If you're using Runas to launch a script, then you might need to change the working directory from within the script.