I'm using the last version of Win10 64b with e-set's nod32 and malware bytes protection tools.
The upgrade process fails completely at deleting ccleaner.exe and ccleaner64.exe, resulting in the install routine to propose to cancel, retry or ignore. Whatever the choice, it's a wrong one.
Such routine should <u>never</u> fail...
I had to change the default installation path, but what about the next update?
This is not the first time, and it's the only program that has this problem.
then go into the Program Files folder for CC and delete its contents
(keep the .ini file if you have customised settings)
download the latest build from here; <a href="https://www.piriform.com/ccleaner/builds" rel="external nofollow">https://www.piriform.com/ccleaner/builds</a>
reboot the PC then install CC from your downloaded file.
Thanks for the suggestion, but I've already tried to delete the original folder: impossible. I can't even take the ownership of the two executables.
As usual, Windows' response is as clear as Crypted Traditional Chinese language for a French speaking guy who tries to write more or less correct English...
<div class="ipsQuote_contents">
<p>
Uninstalling with RevoUninstaller prior to install - SAME RESULT - IT BOMBS AFTER UNPACKING THE FILES!
This is a GIGANTIC PITA - FIX THIS!
</p>
</div>
I'm have the same problem as described in the original post by YPhil. I'm using the Pro version. Windows 10 (version 1803); anti-virus is Windows Defender with Malwarebytes.
This is a significant problem, it needs a resolution. I have finally uninstalled the Ccleaner and reverted to my original Pro purchase (revision 5.24).
How do I install 5.44 Pro so it works and recognizes my registration code?
Also, in trying to install 5.44, which was a Ccleaner pop-up recommendation I some how install Avast which I didn't want. This is really irritating and YES I always watch and try to uncheck the installation of extra software. I saw nothing saying Avast would be installed.
<div class="ipsQuote_contents">
<p>
I'm have the same problem as described in the original post by YPhil. I'm using the Pro version. Windows 10 (version 1803); anti-virus is Windows Defender with Malwarebytes.
</p>
<p>
This is a significant problem, it needs a resolution. I have finally uninstalled the Ccleaner and reverted to my original Pro purchase (revision 5.24).
</p>
<p>
How do I install 5.44 Pro so it works and recognizes my registration code?
</p>
<p>
Also, in trying to install 5.44, which was a Ccleaner pop-up recommendation I some how install Avast which I didn't want. This is really irritating and YES I always watch and try to uncheck the installation of extra software. I saw nothing saying Avast would be installed.
</p>
</div>
0x40000015 is defined as an Unknown Software Exception via MSDN....
I purged the TEMP directory manually to get rid of the offending ASDK.DLL file - tried installing again. It's YOUR file that is failing!
These are from my Windows Home Server 2011 machine. Most of the rest of the workstations have been resolved after many attempts to install, but...
FIX IT!
ps: you have NEVER seen "uncalm" from ME! NEVER ASSUME!
25 years Network Engineer, 30 years PC Tech
Just to add my two cents worth - it also did it to me, and I didn't know where to go to re-download my CCleaner Professional Plus, so I reloaded the folder from my most recent backup. I'm not doing anymore updates.
It appears their attempt to bungle (bundle) Avast with CCleaner IS THE POINT OF FAILURE!
The installer versions bombs on asdk.dll - Avast Ad ASK - pimping Avast AV....
<div class="ipsQuote_contents ipsClearfix">
<p>
Hi
</p>
<p>
Weird reaction of the upgrade routine...
</p>
<p>
I'm using the last version of Win10 64b with e-set's nod32 and malware bytes protection tools.
The upgrade process fails completely at deleting ccleaner.exe and ccleaner64.exe, resulting in the install routine to propose to cancel, retry or ignore. Whatever the choice, it's a wrong one.
Such routine should <u>never</u> fail...
I had to change the default installation path, but what about the next update?
This is not the first time, and it's the only program that has this problem.
</p>
</div>
Thank you for reporting.
Which edition/flavour of CCleaner are you using (e.g. Free, Pro, Business Edition, Tech Edition, Portable, Slim)
Please can you confirm which actions you take to perform an update? E.g. do you run the UI and click a button, or do you run some script?
Which version of Windows 10 are you running (including build number)?
Which custom path did you successfully install CCleaner to?
<div class="ipsQuote_contents">
<p>
Thank you for reporting.
</p>
<ol><li>
Which edition/flavour of CCleaner are you using (e.g. Free, Pro, Business Edition, Tech Edition, Portable, Slim)
</li>
<li>
Please can you confirm which actions you take to perform an update? E.g. do you run the UI and click a button, or do you run some script?
</li>
<li>
Which version of Windows 10 are you running (including build number)?
</li>
<li>
Which custom path did you successfully install CCleaner to?
</li>
</ol></div>
1. CCleaner Professional V5.44.6575
2. I first used the program's update feature, then the standalone path
3. Win10 Home (Swiss-French version) V1803/17134.112
4. C:\Program Files\CCleaner2018 because the default C:\Program Files\CCleaner couldn't be.... cleaned
6577 is a minor fix for a shopping cart URL in the Pro & Pro Trial editions only (one for the 'Subscription Expired'). It didn't merit a big announcement or prompting people to update as it affects a very small portion of the userbase.
I will however take on your feedback about transparency and include the MD5 for 6577 in a separate post of the Announcement thread in the forum for clarity, with this mini changelog.
Update Failures
This change is in no way related to the original post in this thread regarding failed updates. There is a known issue with MWB Ransomware Protection feature that breaks the update process of both CCleaner and other applications such as Skype, Visual Studio Community Edition and so on. MWB have released a fix for this to their Beta programme.
Furthermore, Norton had been originally blocking the file on release, in spite of us releasing the installer files to VirusTotal ahead of time. This could be because their heuristics rely in part on MWB, or perhaps there was some other false positive triggering it. Either way, by the time I sent the False Positive report through it had already been fixed.