Eraser Portable 5.82 Revision 3 has been released. Eraser Portable is a secure data removal tool that can completely remove files from most media. This new release has an improved launcher and installer and is now digitally signed to ensure integrity. It's packaged in PortableApps.com Format so it can easily integrate with the PortableApps.com Suite. And it's open source and completely free.
5.86a Release Removed: Due to bugs with the Eraser Portable 5.86a release posted earlier today, we are recommending this new 5.82 release for all users. Our sincere apologies for any inconvenience this may have caused.
Features
Eraser Portable is a secure file-deletion and data wiping utility. With support for multiple wipes, pattern writing and more, it can be used to securely delete any sensitive data. Learn more about Eraser...
Flash Drive Note: Most modern flash drives use wear leveling to spread write operations out over a device. This interferes with Eraser (and other secure deletion utilities) ability to wipe single files. Wiping an entire drive or erasing a file and then wiping free space should still work securely, though it will put additional wear on your drive.
New In This Release
This release has an improved launcher and installer using the latest PortableApps.com Format and is now digitally signed to ensure integrity.
PortableApps.com Installer / PortableApps.com Format
Eraser Portable is packaged in a PortableApps.com Installer so it will automatically detect an existing PortableApps.com installation when your drive is plugged in. And it's in PortableApps.com Format, so it automatically works with the PortableApps.com Suite including the Menu and Backup Utility.
Download
Eraser Portable is available for immediate download from the Eraser Portable homepage. Get it today!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Comments
Works
Thanks for the great work
cool
Works well, leaves nothing.
We're back on the safe side
Why was 5.86 removed?
Was the 5.86 version removed just because of the VC dlls issue, or were there more serious problems with it?
I.e. if I'm not seeing the VC dll issue, should I downgrade to this "new" version?
It was more than dll issues
It was more than dll issues I think, it was displaying a message saying the application was incorrectly configured. Not sure what it means, but it was probably more than just the dlls.
Can't be fully portable
5.86a can not be fully portable at the moment and will only work on systems with Visual C++ 8.0 DLLs installed and registered. Keeping all the runtime DLLs and manifests in the same directory as eraser does not work. The compilation of Eraser has been getting much messier in the current versions and now uses the complicated side by side DLLs (WinSxS) feature in Windows.
Actually they probably can
Actually they probably can be packaged with it if you include a file named Microsoft.VC80.CRT.manifest in the app directory (from my Visual Studio installation).
This has worked for me before.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <noInheritable></noInheritable> <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity> <file name="msvcr80.dll" hash="10f4cb2831f1e9288a73387a8734a8b604e5beaa" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>n9On8FItNsK/DmT8UQxu6jYDtWQ=</dsig:DigestValue></asmv2:hash></file> <file name="msvcp80.dll" hash="b2082dfd3009365c5b287448dcb3b4e2158a6d26" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>0KJ/VTwP4OUHx98HlIW2AdW1kuY=</dsig:DigestValue></asmv2:hash></file> <file name="msvcm80.dll" hash="542490d0fcf8615c46d0ca487033ccaeb3941f0b" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>YJuB+9Os2oxW4mY+2oC/r8lICZE=</dsig:DigestValue></asmv2:hash></file> </assembly>oh yes
The compilation of Eraser has been getting much messier in the current versions
Oh yes. And a lot bigger (2 mb vs. 5mb)