Runas + password +
encryption = RunasSpc
Guidance and Examples
- Security patches,
software updates, programs and each other
software-package can be installed by the user themselves without having
Runasspc will start the application with other
credentials than the logged-on user. The login information for the
application like username and password are read from an encrypted file.
An administrator can specify, e.g. by central encrypt files, which
applications have to start with admin rights.
RunasSpc is compatible with the most file endings like
No installation procedure for RunasSpc.
- Many users are working
under administrator account, because some programs are missing
administrator rights to run correctly.
With runasspc a standard user has not to login as
administrator to run this applications.
- Surfing the Internet as an administrator makes the
vulnerable to malware, spyware, viruses and other security risks. Surf
with a limited rights account, the amount of risk decreases
Start your Browser under this limited account with Runas
or RunasSpc, if you do
not want to enter the password every time.
- You want to instruct
someone to configure a computer, but
you cannot give him the administrator account information because you
use it also on other systems?
With runasspc and an encrypted file crypt.spc which starts the computer
console (compmgmt.msc) or a filemanager (like wincommander) based on
administrator account you can give him full access to this computer.
Before i developed runasspc. I looked for a version of runas with the
programs under another user account than the logged-in
- The user does
to enter a password, like runas.
- Only the
allowed by me, could be started by the user.
tool must not be bypassed by simple renaming the application name or
of Identification like runas/savecred
- It should be
The application and the account information will be read from a secured
crypt file, which built on command line with runasspc or the
administrator interface runasspcadmin.
Each encrypted file receives his own password on runtime, created by
the file itself, like a finger mark.
Before runasspc start the authorized application, the application will
be checked on bit level (only exe and batch files).
Runasspc does not require an installation procedure. You only need to
copy runasspc and a cryptfile on a computer to start it directly.
Runasspc can also be run without using a cyptfile. You can call
runasspc with password in cleartext on commandline. It can be useful
scripts and tests.
Guidance and Examples
- UAC and Runas Spc work together. If an application
request elevated privilege, the UAC dialog will pop up after you run it
You can launch a non-elevated application with elevated rights with our
new tool RunasRob
- bypass the UAC Dialog is the way of our tool RunasRob
- RunasSpc couldn’t find the application
- Set the complete path of the application in the cryptfile.
- The application must be reached for the user who calls the
application over RunaSpc because runasspc read the checksum of the
application before the application will be call under another user
- Hide start up window of RunasSpc
You can hide this window with the RunasSpc switch /quiet
RunasSpc /cryptfile:“pfad/cryptfile.spc“ /quiet
- UNC Path are supported. Mapped drives not .
The cryptfile can be on a mapped drive but not the application.
- Novell Netware
novell netware path can be a problem for runasspc
- RunasSpc, cryptfile and the application can be on
- Errors Codes:
The most errors codes are explained on Microsoft MSDN.
- Running on XP, Server 2003, Server 2008, Vista,
Windows 7, Windows 8 64 and 32 Bit
- The restriction of the free version for private use
is the start-up window with license information which appears at random
even if you set the switch /quiet.
For any suggestions, errors or questions
RunasSpc is free for private use.
For companies we deliver a licensed version of runasspc, registered to
the enterprise`s name..