- This topic has 12 replies, 5 voices, and was last updated 4 years, 2 months ago by LBL.
May 28, 2018 at 5:03 pm #13410Shane GowlandKeymaster
This should be fixed in the upcoming version.June 4, 2018 at 4:14 pm #13449LBLGuest
It’s FINALLY working again. I fixed it by accident. I had (as Micro$oft recommended) an Administrators account and a Users account that I was logged into. Guess what? That users account didn’t have full rights to access all folders or something. That’s all I can figure.
I had an Event error where I couldn’t access THAT log under the user account so I changed it somehow and went back to jut the one account. Don’t ask me how. And NOW System Ninja works.
Before that it was just accessing the temp folders and the Firefox one was always empty.June 7, 2018 at 10:53 am #13453LBLGuest
Spoke too soon. When I closed out System Ninja or restarted my computer it no longer worked.
What I suspect is that SN updated itself and since I had installed an older version the Winapp2.ini no longer worked in the updated version. They are two totally different files.
I go to GitHub and download the Zip File which contains the Winapp2-Master to my desktop.
Now looking at the (new) Winapp2.ini from the Non-CCleaner Folder with Notepad++ and comparing THAT with my OLD Winapp2.ini from SN v5.15.160311 – well.
This winapp2.ini starts out with:
[.NET Assembly Temps*]
And every other winapp2.ini from there on in looks identical to a CCleaner winapp2.ini instead. I don’t write code and I don’t know anything about code but would you mind looking at the old .ini files and comparing them? I have every possible NETFramework program installed so that’s not the problem.