It has been one year since the last release of Eraser, and we are happy to announce the release of Eraser 6.0.9. Eraser 6.0.9 only contains bug fixes and is the most stable release of the Eraser 6.0 series; users are encouraged to upgrade to this version as soon as possible.
|2277||Fixed documentation errors when adding new tasks||Joel|
|2280||Fixed fatal errors when erasing files which the current user do not have access to||Joel|
|2305||Fixed updater with the change in server||Joel|
|2315||Fixed bug in monthly schedules||Joel|
|2327||Implementation suggestion by Jackjack that the title of balloon tips should be “Task Completed” and not “Task Executed” for clarity inÂ #388.||Joel|
|2328||Document working around UAC to erase unused disk space.||Joel|
|2331||Fixed bug in scheduler where tasks will only be run once per Eraser start up even if the schedule should have been triggered||Joel|
|2333||Fixed memory leak when the Unlocker feature was enabled.||Joel|
|2338||Fixed some cases where file unlocking would still not allow a file to be unlocked for erasure.||Joel|
|2340||Fixed a situation where by a task would be initiated from the Explorer context menu and when Eraser was not running. Under some situations, the task will run but the UI will not reflect that.||Joel|
|2342||Fixed a crash when using the Unlocker code from Windows Vista.||Joel|
It is important to note that users downgrading from 6.1 should delete their Task Lists (%LOCALAPPDATA%\Eraser 6\Task List.ersx) before running Eraser 6.0.x as that will result in a crash of 6.0.x builds. If you are upgrading from an earlier 6.0.x build, and especially if you have defined custom erasure methods or Plausible Deniability files, if upon upgrading Eraser refuses to start after the upgrade you can try deleting the task list (the same file as mentioned earlier) and if that fails, theÂ HKCU\Software\Eraser\Eraser 6Â registry key. Deleting the latter will result in a reset of all Eraser settings to defaults.
Download Eraser 6.0.9 fromÂ SourceForge