Windows 7 64 dell laptop. Downloaded and running from Windows Explorer. Trend AV. Also fails to install with AV disabled. Fails install in safe mode. Running install as administrator. Fails on downloaded versions from 5.23 - 5.26.
appcrash
ccsetup526.exe
2.0.0.0
pfUI.dll
Your assistance is greatly appreciated.
can you run CC with the command line switch /DEBUG and post the output?
info here; http://www.piriform.com/docs/ccleaner/troubleshooting/running-ccleaner-in-debug-mode
"CCleaner526.exe /debug" or "CCleaner526.exe /DEBUG" has absolutely no effect (even when started from an admin comment line), there's no log file created anywhere, I just see a notification saying it is not compatible with my system.
All version up to 5.25 were installing or updating without problem.
Version 5.26 is no longer compatible with Windows 10 (64-bit version) official release ! The CCleaner instlaler was visibly incorrectly compiled (or compiled on an unsupported version of the Windows SDK, or only partly rebuilt instead of after a "make clean": the installer has evident problems of incorrect structures sizes when it calls the Windows API, probably caused by confusing 32-bit and 64-bit compiled modules, or mixing C/C++ headers from different SDK versions)
as per my link, above, you start a command line prompt, navigate to C:\Program Files\CCleaner and type the command ccleaner64.exe /debug
(adjusting as needed to suit your PC)
once done, in that same folder will be the debug file.
it looks like you are trying to use the /debug switch on the downloaded installation file instead of the installed program file.
and your problem is different from the OP's, so starting your own thread would be best.
I have been seeing a similar behavior on random systems since CC 5.19. I can't upgrade to any newer build (through 5.28). I start the installer, deselect any options not wanted and then the installer crashes with a pfUI error (see below)
Problem signature:
Problem Event Name: APPCRASH
Application Name: ccsetup528.exe
Application Version: 5.28.0.6005
Application Timestamp: 5682fc79
Fault Module Name: pfUI.DLL
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 57e2dcd9
Exception Code: c0000005
Exception Offset: 0002f146
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I'm having a similar issue and can't install CCleaner. I've run it for years, then all of a sudden about a month ago it crashed during install. Uninstalled and still can't install it on my Windows 10.
I run setup, get the setup dialog. Click Install,
"CCleaner Installer has stopped working." (An unhandled win32 exception occurred in ccsetup529.exe [17768].)
running install with debug does the same thing, but no log.
ccsetup529.exe /debug
Event 1000, Application Error.
you DO NOT run the /debug switch on the installer ccsetup529.exe
you run it on the actual executable ccleaner64.exe /debug (or ccleaner32.exe, as per post #4)
and since you can't install the program, this won't help you. so I actually gave you a bum steer in that regard.
try the portable build (which doesn't require installation) from here; https://www.piriform.com/ccleaner/builds
Yes, that does work. (Thanks!)
Any idea what's causing the installer to crash?
I noticed v530 was out so installed that and get the same crash as 529.
Any chance I can get this resolved or do I have to run portable forever?
as far as cleaning goes, there is no difference between the Portable, Slim or normal builds.
but something to try; perhaps it's your AV software, what do you use?
you can either try to install CC with your AV temporarily turned off, or install CC with the PC in Safe Mode.
Thanks for the prompt reply.
AV is Sophos and I see reports if it is triggered and no notification in this case, just the install crashing.
CC worked fine and I updated it regularly until a few months ago when the crashes started. I am a domain admin so shouldn't be a permission issue and other programs are installing without issue.
Is there a debug-enabled version I can install or anything from the event log that helps?
if you could try the installation from Safe Mode option if for no other reason then to cross it off the list, that would be helpful.
Sorry for the delay.
I have the same problem in safe mode. (v.5.30.0.6065)
bugger, thought Safe Mode would install OK.
another straw to clutch - log onto another User account (create one temporarily in necessary) and try installing when logged on to there.
assumption being something is corrupted in your current user profile.
You may be onto something there. When I changed the pw on a local user (not used for years), it was unable to login due to an error and suggested logging out to fix it, which didn't work. I had the same problem on a buddy's computer, which appeared to start last Feb and I had to wipe that since it wouldn't even boot into desktop. His computer also had CCleaner on it. Wiping a development computer and installing everything on it all over again can take a week, since it needs to be set up as a server and a pc. I suspect that may be the fix.
Thanks for your help. If I have anything else to add, I'll reply to this thread.
Due note you aren't alone with CCleaner not installing, and with it crashing - just look around the forums and you'll notice other topics. So with that in mind it "may not be your system"!
FWIW, updating to the latest version of WIndows 10 fixed my problem.
I was able to install the ccsetup530.exe that had failed before and was updated to the latest and it still worked.
Thanks for the help.
still seeing the same issue on systems -- through the latest 5.43 builds.
I guess Piriform does not care.
17 hours ago, garetjax said:<div class="ipsQuote_contents"> <p> I guess Piriform does not care. </p> </div>
Or perhaps they have too much to fix all at once.