Thanks but still no luck. I seem to remember resolving a similar issue a while back. I think it had one or more files in it's scheduled tasks, and I somehow found where it was storing them and erased them, then it was able to start. It seems from the stack trace below that it's trying to do a secure move on startup, and failing? Complete guess of course. Where does it store the scheduled list?
Current status:
the v5.8.8 I had previously installed (and seemed to work) no longer installs or uninstalls.

I'm not sure how it can be running because there is no eraser.exe on my computer (I use Everything to search
voidtools)
The latest version crashes on startup.
OS Name Microsoft Windows 10 Pro
Version 10.0.18362 Build 18362
Faulting application name: Eraser.exe, version: 6.2.0.2988, time stamp: 0x5eda526a
Faulting module name: KERNELBASE.dll, version: 10.0.18362.815, time stamp: 0xb89efff3
Exception code: 0xe0434352
Fault offset: 0x000000000003a799
Faulting process ID: 0x3d20
Faulting application start time: 0x01d63c08bfc713f6
Faulting application path: C:\Program Files\Eraser\Eraser.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 79616b10-544c-4cc7-a429-5f45dffcb423
Faulting package full name:
Faulting package-relative application ID:
Application: Eraser.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentNullException
at System.IO.Directory.CreateDirectory(System.String)
at Eraser.DefaultPlugins.SecureMoveErasureTarget.CopyFile(System.IO.FileInfo)
at Eraser.DefaultPlugins.SecureMoveErasureTarget.Execute()
at Eraser.Manager.Task.Execute()
at Eraser.Manager.DirectExecutor.Main()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()