[CCleaner appcrash after selecting install.]

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.

[CCleaner appcrash after selecting install.]

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.

[CCleaner appcrash after selecting install.]

Sorry for the delay. 

 

I have the same problem in safe mode. (v.5.30.0.6065)

[CCleaner appcrash after selecting install.]

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?

 

 

Faulting application name: ccsetup530.exe, version: 5.30.0.6063, time stamp: 0x5682fc79

Faulting module name: pfUI.DLL, version: 0.0.0.0, time stamp: 0x57e2dcd9

Exception code: 0xc000041d

Fault offset: 0x0002f146

Faulting process id: 0x1a74

Faulting application start time: 0x01d2cf15069607ce

Faulting application path: D:\Download\ccsetup530.exe

Faulting module path: D:\Temp\nst60D9.tmp\ui\pfUI.DLL

Report Id: f174353c-12e8-4c17-b1aa-892ba8c82a37

Faulting package full name: 

Faulting package-relative application ID: 

 

 

Fault bucket 108923166009, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: ccsetup530.exe

P2: 5.30.0.6063

P3: 5682fc79

P4: pfUI.DLL

P5: 0.0.0.0

P6: 57e2dcd9

P7: c0000005

P8: 0002f146

P9: 

P10: 

 

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER945A.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ccsetup530.exe_1a61339b9ee6dd5e50143dad05d8eaaff6033eb_53e6c27a_3983a8dc

 

Analysis symbol: 

Rechecking for solution: 0

Report Id: 5eaebabb-c3b0-4e30-abe4-7c9b2f0ede39

Report Status: 0

Hashed bucket: d6c689d8a6751cfcc4587dff597ea4d3

[CCleaner appcrash after selecting install.]

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? 

[CCleaner appcrash after selecting install.]

Yes, that does work. (Thanks!)

 

Any idea what's causing the installer to crash?

[CCleaner appcrash after selecting install.]

Event 1000, Application Error.

 

Faulting application name: ccsetup529.exe, version: 5.29.0.6033, time stamp: 0x5682fc79

Faulting module name: pfUI.DLL, version: 0.0.0.0, time stamp: 0x57e2dcd9

Exception code: 0xc000041d

Fault offset: 0x0002f146

Faulting process id: 0x42e8

Faulting application start time: 0x01d2c2aace899b31

Faulting application path: D:\Download\ccsetup529.exe

Faulting module path: D:\Temp\nsw7840.tmp\ui\pfUI.DLL

Report Id: 2d49cad4-eec9-4768-9345-bd9f5b0741c5

Faulting package full name: 

Faulting package-relative application ID: 

[CCleaner appcrash after selecting install.]

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