SmartClose Version History
(February 3, 2010)
Fixed: in some cases, SmartClose didn't save the
closed/killed programs to the system snapshot.
Fixed: after running the Close Programs wizard more than
once in the same SmartClose instance, the closed/killed programs and stopped
services didn't get saved to the system snapshot correctly anymore.
(December 27, 2009)
- Fixed: SmartClose could hang at startup, with the result that it
didn't appear (or possibly only in the task bar), and that the program
had to be ended with the Task Manager.
- Fixed: SmartClose failed to see 64-bit processes.
- Fixed: several problems on Windows Vista and 7:
- SmartClose sometimes failed to detect if a program was closed, and
didn't write it to the system snapshot.
- SmartClose failed to retrieve the current path of Explorer windows.
- Possible disappearing buttons, radio buttons and checkboxes
when pressing the Alt-key.
- Fixed: On Windows XP or higher, SmartClose didn't detect if the
navigation tree of Explorer windows was visible.
- Fixed: In the Restore-wizard, unavailable (disabled) programs were
sometimes still checked, so they couldn't be deselected.
- Launching SmartClose will now always show the UAC (User Account
Control) prompt, if UAC is enabled.
- The following critical programs have been added to the built-in list
of Protected Programs, to prevent SmartClose from ever killing them:
Smss.exe, Csrss.exe, Wininit.exe, Logonui.exe.
- The following services have been removed from the default list of
services to stop, because stopping them is unwanted in some cases:
Error Reporting Service, Fax Service, Human Interface Device Access,
Portable Media Serial Number, Secondary Logon, Smart Card, Smart Card
Helper, SSDP Discovery Service, System Restore Service, Uninterruptible
Power Supply, Universal Plug and Play Device Host.
- Changed the default System Snapshot folder to SmartClose\Snapshots
in the current user's Application Data folder.
- The /noresult command-line parameter can now be used together with
the /close and /kill parameters, to suppress the result window.
(March 9, 2005)
Fixed: some antivirus programs,
such as McAfee AntiVirus, could falsely detect the
SmartClose executable as a trojan (BackDoor-ASB.b.dll).
This was because of the technique SmartClose used to
SmartKill a program on Windows 95, 98 or ME. As a
precaution, support for SmartKill on these OS's has been
temporarily removed from SmartClose, but a later version
will probably support SmartKill on all OS's again.
Note: SmartClose didn't, doesn't and won't ever include
any malicious code.
(March 1, 2005)