I believe you on your bug report.
After some investigation it seems the AV app (ESET) in my case was locking the file and it then got queued for erase on reboot.
Could you turn off the AV protection, re-run your test and let me know what happens.
I can repeat your bug but not all the time...
ok another release
Again tested on Win10.
Seems like corrupt registry entries.
Make sure you have administrator access to the PC.
Uninstall eraser from the windows programs and features section. if it fails try install/uninstall...
Install the .Net framework from here first: https://support.microsoft.com/en-ie/help/4054530/microsoft-net-framework-4-7-2-offline-installer-for-windows Then try installing eraser.
I'll look at embedding the runtime in the install but that tends to make it very large.
The problem has been responded to many times. Errors are caused by a variety of reasons e.g locked files , Anti -Virus application interfering, Disk errors etc You need to look there first before blaming eraser.