By running the cleaner only, it just removes temporary unimportant junk, right? So if I want to find & delete some leftover's from a bad uninstall of a software program, the cleaning won't cause a problem?
Thanks
By running the cleaner only, it just removes temporary unimportant junk, right? So if I want to find & delete some leftover's from a bad uninstall of a software program, the cleaning won't cause a problem?
Thanks
nothing is 100% certain, if it was, there wouldn't be this forum.
remove the word temporary and the statement unimportant junk is definitely true - that's what it does, just the junk, temp or not.
if the software has already been uninstalled (bad or not) removing the remaining should cause no more harm as the software won't work anyway.
also use winapp2.ini if you aren't already, as it goes that bit further with removing left-over crap.
Many programs leave behind a lot of registry entries after uninstalling it. Use the CCleaner Registry cleaner to get most of them, look at the list before deleting all of them.
also use winapp2.ini if you aren't already, as it goes that bit further with removing left-over crap.
We shouldn't recommend anyone on here use winapp2.ini as firstly it isn't endorsed by Piriform, and secondly, with all due respect to grits, it can cause problems which is the last thing a less experienced user needs ...
A large ini such as this one can cause a slower startup for ccleaner (far more noticeable on older/slower machines) and users may wish to manually remove entries they do not need from the file if they feel this lag time is too great.
Please bear in mind that these entries are NOT endorsed or supported in any way by the developers of CCleaner, and should be considered "beta."
That being said, they can (though we do our best to prevent this) cause issues with various programs or your system as a whole.
Piriform is not responsible for any damages done to your computer, and I also ask that if you encounter an error/problem with an entry here, you post it in this thread to keep winapp2.ini related issues centralized.
... taken from the "spoiler" ...