That's why I always have that box unchecked.
I don't want to try to run .EXE only to find out that it was wiped out because it was an "unused" file extension.
My mileage is totally different.
I always have that checked and never bother with a backup (though I do look first) and it has never hurt me.
It often complains about such things as ODS, ODT, etc.
These and many others are file extensions used by my Portable version of Open Office which has NOT registered its use in the registry.
After I have purged these entries from the registry I cannot double click a file with that extension and have Windows launch Open Office,
but even if I do not purge I get no such result anyway.
I can still launch Open Office and it can still remember and load the ODS and ODT files because CCleaner was not purging such files, only redundant registry values.
I cannot believe that Explorer.EXE would be zapped by CCleaner,
Even if CCleaner did attempt to zap Explorer.exe then it should encounter a natural Windows Protection "File in Use" blockage.
I suppose that if a removable device has an application which has registered its use of a particular extension,
then running CCleaner with that device removed would result in that registered key being declared "unused" because the "user" is missing,
and then when the device is reconnected you can double click on a file and the registry will not designate what uses it so it will not load.
Then you simply merge the backup registry file (which I never create if I know I will never need it).
For CCleaner to declare that EXE is an unused extension then Windows probably needs an inability to locate the entry point for launching an EXE,
which raises the question how on earth did you even BOOT the computer, and then to launch CCleaner.EXE ! ! !
Alan