Supported Platforms for KillProcess
Windows Vista User Account Control (UAC) issues
Why cannot KillProcess terminate my process?
KillProcess is unable to retrieve debug privileges
How can I contribute to the development?
Will KillProcess or TimeStamp be distributed as Open Source?
KillProcess hijack .lst files for other applications
Can KillProcess be run from the command prompt?
Frequently Asked Questions
Our applications should be very easy and effective to use. There has however come up some questions in the past that might be of interest for all users.
Supported Platforms for KillProcess
KillProcess ONLY supports the following Microsoft operating systems
- Windows NT 4.0 (KillProcess version 1.6.3 only)
- Windows 2000
- Windows XP
- Windows Server 2003
- Windows Vista
- Windows Server 2008
- Windows 7
If your Windows platform isn't listed above, the application might still work but it hasn't been tested properly. This is essentially true for all 64-bit platforms of Windows.
These platforms are UNSUPPORTED:
- Windows 95
- Windows 98
- Windows Me
- Windows CE or Mobile
KillProcess of versions prior to 2.42 doesn't autostart at logon since they are not digitally signed and require administrative privileges to run. Download and install KillProcess 2.43 or above to solve this issue
Replacing the Task Manager will not work in Vista with UAC switched on
In order to replace the Windows Task Manager with KillProcess on Vista when UAC is switched, you have to elevating the KillProcess application before trying to apply this setting. Otherwise Windows will reject (virtualize) the change to the Windows registry.
There is an number of reasons for why some processes cannot be terminated by KillProcess:
- KillProcess was not able to retrieve debug priviliges on the computer. This is usually the case when running as an restricted or less privileged user. On Windows Vista elevating the KillProcess application will solve this issue. For other operating systems see KillProcess is unable to retrieve debug privileges below
- Some applications cannot be terminated if they are attached to an debugger, such as Microsoft Developer Studio or Kernel Debugger.
- The process was started by the WOWEXEC subsystem (Windows 16 bit On Windows). You will have to terminate wowexec.exe instead.
If KillProcess is unable to retrieve debug privileges when trying to terminate the applications, this is due to the Security Policy settings in the operating system. This page helps you to solve this problem.
This error and also the solution were originally reported by Juan Gonzalez in early May 2003. Thanks for the help Juan!
KillProcess and all other applications developed by Orange Lamp Software Solutions are totally free of use. We would however greatly appreciate if you would kindly donate 10 EUR for the future development of the application. Such a donation would make it financially possible for us to continue to improve our software products.
Any donations to Orange Lamp Software Solutions will be made using the PayPal service. This is for the convenience and the safety of your transaction.
Please contact us if you would prefer to send us the donation via standard "snail-mail"
KillProcess and TimeStamp will probably never be distributed as free source. The main reason for this is simply that I still like to be in full control of the development, since all my applications are my children :-)
KillProcess will register the .lst extension for the Kill List files during the installation. There has been reports on other applications, such as RegSeeker, that use this extension for other purposes. If the application that uses the extension cannot re-register the usage or be reinstalled, delete or change the registry setting in HKEY_CLASSES_ROOT as shown below: