This is an even larger release than yesterday, with more major functionality introduced!
- Added an Allow list, so programs on this list will not be terminated. You can add to the Allow list either by pressing ‘A‘ in Debug mode, or through KillEmAll Configuration.
- Added ability to Block programs from execution, meaning they cannot run. This is a system-wide setting and takes effect even after KillEmAll is closed. Add to the Blocked programs by pressing ‘B‘ in Debug mode, and remove the block in KillEmAll Configuration. Note that KillEmAll must be Run as Administrator to enable the add/remove block functionality. Note that program blocking does NOT work with Windows Store Apps!
- NOTE: Some Debug mode hotkeys have changed due to new features (see above!)
- You can now Run as TrustedInstaller directly from Standard User mode at any prompt you would normally also be allowed to Run as Administrator OR by simply holding the SHIFT key while starting KillEmAll normally (this is not available when KillEmAll is running from a network drive, from there it must progress to Administrator first then TrustedInstaller .)
- KillEmAll previously didn’t show the ending menu/prompt after process termination when it was run by typing “killemall” at a command prompt/console window, this was by design but due to other functionality it needed to be changed, so now it shows the ending menu/prompt regardless of how you launch KillEmAll.
- Fixed an issue when passing /log=”alt_log_filename.txt” but relaunching KillEmAll as Administrator or TrustedInstaller was losing the custom filename originally passed to KillEmAll.exe, now it preserves the file name (or full file path) passed when relaunching itself.
- KillEmAll now remembers if you selected to create a log file (or if the /log command line argument was passed) when relaunching itself (as Administrator or TrustedInstaller), and so it will automatically log the new sessions, showing you the final log when you close KillEmAll as expected.
- Fixes and tweaks to functionality and application flow when KillEmAll doesn’t have write access to its own directory (preventing Config from saving or Updates from being installed.)
- Other minor fixes and tweaks.
- v188.8.131.52 – Added ability to skip terminating the remaining processes (or not) when quitting Debug mode by pressing ‘Q’ before it has completed.
- v184.108.40.206 – Added a ‘dummy EXE’ to install to C:\Windows by default when blocking a program, because the program blocking requires a redirected executable, or a dummy. In the previous two releases KillEmAll configured the dummy as “cmd.exe /c echo.” which satisfied Windows so that it didn’t throw “File not found” errors when the blocked program tried to run, however this caused a brief console window (command prompt) to flash on screen every time a blocked program ran. With this release a dummy EXE runs silently and uses no resources, terminating instantly, so that your applications in the foreground do not briefly lose focus with a flashing console window. Note any programs blocked with the previous two releases should be blocked again. This setting can be disabled in Config, (uncheck “Prevent File Not Found Errors” under the Blocked Programs list.)
Get the latest KillEmAll here, or you may of course update from within the app if you have a version that allows it.
(BTW: there will NOT be an update to the open source KillEmAll.NET to include the allow list and block list functionality.)