Windows 7 Enterprise 32 bit
Windows 7 Home Premium 64 bit
Windows XP SP2 32 bit
Page updated September 2015
Email: Support (at) TryWare.dk <--- Change (at) to @
Address: Radhuspladsen 5, 1 th., DK-4200 Slagelse, Denmark
Context RunAs UAC
License Software: Not released before 2016
As you can see in EULA-Copyright.txt located in the C:\ITD\TrywareDk\Setup\SW\Bin folder, I give you one 100% freeware lifetime license to use my Windows Tool with unlimited features. But it's with the exception that you don't have license to distribute my CapaLib Windows Tool. So if you want to give my CapaLib Windows Tool to a friend, then don't do anything else than give them my download link. There is no restrictions in my one 100% freeware license, except showing you my donation website after you have used my Windows Tool 90 days.
I'm currently BETA-Testing my Windows Tool solution, and expect it to be ready early in 2016.
When it's ready you can pay for a lifetime license. As you can see in my W8-EULA-Copyright.txt located in the C:\ITD\TrywareDk\W7-Setup\Bin folder, I give you a lifetime license after paying me
Maybe your company's security rules, forces you to logon as not being member of the local administrators group, but sometimes you need the credentials of the local administrator, or your domain administrator.
If so, your option is to rightclick a file in Explorer.exe, and select the "Run as a different user" in the context menu, each and every time you want to run the program. After that you need to type the wanted user's logonname and password, before the program is started.
But in some cases, you might need to rightclick a file, that don't show you the "Run as different user" option in Explorer.exe's context menu, even if you hold down the SHIFT key while rightclicking the file. That is e.g. the case for .vbs files (vbScript), where Explorer.exe's context menu only gives you the option to run e.g. the .vbs file with one of the editors, you have selected in your file associations in registry.
The solution is to use my Windows Tool instead of Windows Explorer.exe
I've examined it for some week, and I don't know why, but the main part of these Control Panel feateres below always works if you use the Start/Run menu, and types the .cpl, .exe or .msc filename. But if you (or I) runs them using a script with credentials, lilke e.g. the Windows builtin command line runas.exe, then some of them only works on Windows XP, but not on Windows 7, and some of then only works on Windows 7, but not on Windows XP, and a few of the both works on Windows XP and Windows 7. And I'm using exactly the same source code in Windows 7 and Windows XP to start these Control Panel features.
If you know why and have the solution, then please tell me, so it can be part of my Windows Tool.
Below I have marked which operating system they works on, acoording to my test results:
When using my ContextFileExplorer.exe Windows Tool, you can start any program without any need to type username and password, but they will start with your choice of another users account credentials and userprofile:
Please note that in all the options mentioned above (except #4), you don't need to type any username or password.
But if the vendor have compiled a manifest into their program, forcing your operating system to UAC-elevate a local administrator account, before starting their program, I can't change anything about that.
And far as I have searched the market, I'm the only one giving you all these options in the same Windows Tool file as 100% freeware. But because I have used more than 5 weeks with 8 hours man power to create my Windows Tool, I want you to consider about supporting my work, and make a donation to me, after trying my Windows Tool for a while. There will be no changes in my Windows Tool file, when you use it, even if you decides not to donate anything to me, except that I will show you my donation website each time you have used my Windows Tool 90 days.
But there is a tiny tiny risk, that if a hacker gets access to your harddisk, or your backup maybe on a USB-Disk, your domain fileserver, or a FTP-server, or a Cloud Backup service, without being logged on as you, and if they could figure out what is needed to do (I won't tell anybody about how), they could manipulate my windows Tools to gain access to use (not to see your passwords) one of the 4 user credentials described below, saved in a 1.048 bit encrypted binary Passwords.bin file. In order to avoid that 100% securely, I always automatically disables the encrypted Passwords.bin file described below each time you logoff your computer, so in order for yourself to use it, you are always (but only once after you login) asked to enable it with your domain administrators password as described below. Otherwise the encrypted Password.bin file isn't enabled.
And in order to disable hackers choice of using 'brute force' or simular tools to crack your encrypted Passwords.bin file, I'm delaying my enabling algorithm 15 seconds, because these hacker tools is using trillions of attacks each second, in order to crack it. So now they can only use 1 attack each 15 second.
NSA have decided that AES 256 bit encryption is enough for government use, because hackers would need 50 supercomputers build in 2012 in 3.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000.000 years if they attack 1.000.000.000.000.000.000 times each second. These numbers should be multiplied with 32 (from 256 bit to 8.192 bit) with my encryption, and multiplied with 1.000.000.000.000.000.000 * 15 (for each second). Maybe it would be much faster than that, if hackers could use NSA’s new monster computer, but it’s too expensive, and will never be used to crack my 1.024 bytes encryption, so I believe you can use it without any problems.
But I give you the option to change the seconds between 0 - 15 seconds, if you don't find this nessessary.
Here is what my ContextRunas.exe Windows Tool automatically does, so you don't need to do anything of the description below, it's only shown automatically just after install, and it's here to explain to you, how my Windows Tool works.
In the example below I'm running .vbs files with my PsPad Editor, where my Windows Tool does the following for you:
1. Create an encrypted Passwords.bin file with passwords of the LogonUser setting described below in #3
2. Create a special "substituted" copy of your original program file C:\Program Files\PsPad Editor\PsPad.exe as ContextPsPad.exe in the same folder.
3. Create a copy of C:\ITD\TrywareDk\ContextRunAs\SW\Ini\ContextDefaultSettings.ini as
4. Add C:\Program Files\PsPad Editor\PsPad.exe to your list of substituted program files in
NOTE: There's no need to change any of your shortcuts to your original program file for PsPad Editor, and no need to change anything in your registry about your file associations for the *.vbs extension to the PsPad Editor.
The first time you run my ContextFileExplorer.exe Windows Tool, it will automatically force you to run my
My ContextPasswordSave.exe Windows Tool will then use a strong encryption to save these 4 settings in a encrypted Passwords.bin file, where your around 100 bytes, is converted to a binary string containing more than 175.000 encrypted bytes.
If you want to change the default filenames filter when using my file open dialog box, or the default selected substituted file, or the delay options, use this file:
;o) Your brain is also like a parachute. It works best when it's open