This topic contains 21 replies, has 4 voices, and was last updated by 
-
Posts
-
George CaneHi,
Just updated System Ninja to version 3.2.5 in the hope that I could now use the Junk Cleaner again, which I’ve not been able to use since the start of Windows 10.
Disappointed. The same thing is still happening, I start the cleaner, it displays the filepath of just one file, pauses for a few seconds then System Ninja closes.
Everything else seems to work, I didn’t actually use any of the other tools because I’d just used those I use with the previous version.
System Ninja, the previous version, still works properly in my wife’s Windows 7 laptop.
George Cane
Run the program as an administrator. Activate the debug mode in the settings. Reproduce the problem. Download here “debug-errors-***.log” from the program folder.
Windows XP SP3, x86; Windows 7, x64; Windows 10, x64
Exception encountered in module [System Ninja]
Message: Object reference not set to an instance of an object.
at System_Ninja.routine_startup_data.read_x64_registry_startups()Exception encountered in module [System Ninja]
Message: Object reference not set to an instance of an object.
at System_Ninja.routine_startup_data.read_x64_registry_startups()Exception encountered in module [System Ninja]
Message: Object reference not set to an instance of an object.
at System_Ninja.routine_startup_data.read_x64_registry_startups()Exception encountered in module [System Ninja]
Message: Object reference not set to an instance of an object.
at System_Ninja.routine_startup_data.read_x64_registry_startups()These don’t cause any issues. They’re leftovers from when Windows first implemented the Wow6432Node redirects.
OK…
So, I uninstalled System Ninja, then using RegEdit, I removed all references to System Ninja from the registry.
Then re-booted the laptop, re-installed from “ninja-setup-3.2.5.exe” running as administrator.
Than ran System Ninja, ‘ as administrator’, went to the ‘Options’ tab and selected ‘Debug Mode’, and tried using ‘Junk Remover’, the problem is still just the same.
I opened the System Ninja folder but this time ‘ debug-errors-***.log’ is absent.
I find that there is a ‘Dump’ file in ‘AppData\Local\CrashDumps’.
herewith in case it helps.
Ah… too big, zipped is smaller.
Try again.
Still trying to find an answer to my problem.
Usually when I start Junk Scanner, I’m offered a choice of which drives to scan, and usually I choose just C:\ and click Scan, today out of curiosity I chose D:\ and clicked Scan… Junk Scanner worked correctly, finding and deleting over a gigabyte of junk !
Then I tried scanning C:\again and the application failed in the usual way. I tried de-selecting all but ‘Temporary’ files and tried again, and sadly the application failed again. I then tried de-selecting just ‘Temporary’ files, and again the application failed.
Logically there must be something somewhere ‘Protecting’ the C:\drive… I’m not keen on the idea of closing my AV program to test that, and anyway, why would that protect the C:\ drive but not the D:\ ?
C:\ is typically the system drive and would be protected more than others.
What A/V are you using? We can spin up a VM and test whether there’s a conflict happening.
I think we need to look into Windows journal through the event viewer.
Windows XP SP3, x86; Windows 7, x64; Windows 10, x64
