CCleaner Breaking Sage

[taffybach]

I ran CCleaner (as I have done for about 10years) today and it killed my Sage installation.

I couldn't find any mention of this in this forum but there is a warning on Sage that CCleaner breaks Sage v23 and v24.

See http://ask.sage.co.uk/scripts/ask.cfg/php.exe/enduser/std_adp.php?p_faqid=37124

Will this be fixed?

 

[mta]

g'day taffyback and welcome to the forums,

do you use CC with winapp2.ini or and other enhancements?

run an Analyse and look in the Applications results for anything mentioning Sage, double click that entry to show the files and then you can right click and Add to exclude list.

[nukecad]

Hi taffybach,

The link you give refers to the registry cleaner section of CCleaner removing Sage entries.

Don't run the registry cleaner, it's a specialist technicians tool and not intended for normal everyday use.
Any reg. cleaner should be used carefully and can break things if you are not familiar with the registry.

Just stick with using the cleaning tool.

[taffybach]

Thanks  - not sure a 'don't use it' is the right response though.

CCleaner is the leading cleanup tool and Sage the number one accounting package.

CCleaner shouldn't really be stomping on Sage installation and registry files.The whole idea of CCleaner is an easy (and supposedly safe) tool for cleaning the system AND the registry.

 

[Nergal]

It's not really a case of not using the registry section, as MTA suggests, but using it judiciously.  Scrutinize each suggested cleaning entry.  If indeed you are running the registry section when you lose sage funtionality, you should run analyze on each section and excluded the sage keys.  Ccleaner detects non-functional possible cleanup entries in a certain way, if the software (sage in this case) uses a different method to connect program to registry communication it might show up in ccleaner.  For more info on a sane way to use the registry section, see my signature below this post

[Guest Stephen CCleaner]

Hi taffybach,

We've recently become aware of this via support tickets and we are investigating what would be required to add cleaning definitions for Sage. As Sage is a heavyweight financial accounting product, these cleaning definitions will only be available in our business products (Business Edition, Technician Edition, CCleaner Cloud). They will not be available in CCleaner Free or CCleaner Pro, as these products are for personal (non-commercial) use only.

You can find more information about our business products here: https://www.ccleaner.com/business. CCleaner Cloud is our newest product and is actually a pretty nifty bit of kit for IT managers.

We can't commit to a release date for the Sage cleaning definitions at present; we first need to investigate how the products (for there are multiple) behave. We will try to contact Sage directly for assistance and hopefully this will speed up the process.

In the meantime, you can whitelist the Sage registry entries in the Options > Exclude menu:

From what we can see, the registry entries for Sage are stored in HKCR (HKEY_CLASSES_ROOT) under many different CLSID keys (e.g. HKCR\CLSID\{60DE926F-7CB2-41AA-AD59-0709DDE1A296} ). It's not clear if those keys are always the same for every machine you install it on or if they are generated dynamically on every install. If it is the latter, it will be very difficult if not impossible for us to clean it. Hopefully if we can initiate a dialogue with their development team we can make progress on this.

For excluding Sage registry entries, you have two options:

1. Exclude the specific Sage CLSIDs you can find by performing a search in HKCR for 'Sage' and adding each CLSID key one by one
2. Exclude all CLSIDs

Option #2 (shown above) is a much faster but ultimately heavy-handed approach that will exclude a lot of other applications from registry cleaning. It's your call.