The issue is most likely to be because an instance of Eraser was running already without administrative privileges in the 1st place.
Eraser starts automatically (without these privileges) when windows starts up so you'll need to exit this first, "unprivileged" instance before any of your...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.