mitja.kolsek -

[Update 8/4/2020: We've issued a new 0patch Agent version which by default excludes CCleaner.exe and CCleaner64.exe from injection by 0patch.]

CCleaner, versions 5.67, 5.66, 5.65 and likely some other versions, has a compatibility problem with 0patch resulting in ccleaner.exe or ccleaner64.exe processes occasionally crashing. We were only able to reproduce this immediately after installation of CCleaner but some users reported crashes while using CCleaner.



Option A. Excluding CCleaner.exe and CCleaner64.exe in 0patch.

  1. As administrator, set registry value ExcludeModules under HKEY_LOCAL_MACHINE\SOFTWARE\0patch to "CCleaner.exe|CCleaner64.exe" (without the quotes)
  2. As administrator, change registry value Counter under HKEY_LOCAL_MACHINE\SOFTWARE\0patch\CallbackKeys\UnloadLoaderDll to arbitrary other number than it already is (e.g., if the current value is 0, change it to 1, and if it is anything other than 0, change it to 0).
  3. Restart 0patch Service

Option B. Using older CCleaner, as suggested by some forums as a solution for crashing with other security products. We confirmed that version 5.40 ( didn't result in any crashes after installation. Some users have reported that CCleaner 5.64 is not affected.

Have more questions? Submit a request


  • 0

    I have not been able to get that registry trick to work. I have tried "CCleaner.exe|CCleaner64.exe", CCleaner.exe|CCleaner64.exe, and CCleaner64.exe in the ExcludeModules and even restarted the computer to make sure. Still did not work but uninstalling 0Patch did work on letting CCleaner run again.

  • 0

    Version 5.63 also works without issues on my computer. Any version higher than that allows a normal installation, but immediately goes to a blank CCleaner screen when you launch the program.

    I spent quite some time trying o troubelshoot that when I tried to update to a newer version. Now I know where it came from.

Please sign in to leave a comment.