Hello,
I am having the same problem BUT ONLY after raising my UAC level anything higher than "never notify." It seems "never notify" resolves the problem.
I haven't tried it but ... maybe one could lower the UAC to "never notify" and run eraser and then raise it back up again.
Another WORK AROUND: As the problem seems related to the UAC, Microsoft left one time in the system when the UAC is not yet on (or at least it looks that way). If you set up the task scheduler to run a program / file at login time, the UAC basically runs at the "never notify" level (for Windows 7). I start several programs, including two command prompts and everyone one of them runs with full admin privileges.
Presently, I'm on version 5 and am thinking about upgrading to version 6 and trying out some of these work around ideas. I'm wondering if anyone has already tried them out with version 6 and/or would like to do so?!/
Thanks and take care.
UPDATE/P.S. Is Eraser development still on-going? I"m asking as the date for the most recent version of Eraser (6.0.10.2620) is May 22, 2012 according to the Files section. Given today is May 6, 2014, well, its been 1 year, 11 months, about 15 days +/- several days, since 6.0.10.26.20 came out.