top of page

Bedtime Stories - Tales from Our Commmunity

Öffentlich·9 Mitglieder
Elijah Bailey
Elijah Bailey

Ccleaner Protable

Actually, there is a portable file on the Piriform download server (https:// if you know where to look for it, but it is not posted on the builds page because of the problems it will create if you run the executables in their current state. I don't know why Piriform hasn't removed this .zip file from their download server.

Ccleaner Protable

.... Actually, there is a portable file on the Piriform download server (https:// if you know where to look for it, but it is not posted on the builds page because of the problems it will create if you run the executables in their current state. I don't know why Piriform hasn't removed this .zip file from their download server.

If built correctly, a CCleaner Portable app that can be run from a removable USB thumb drive on different computers should not be making changes to the Windows registry when it is launched. Instead, all custom configuration settings should be stored in the ccleaner.ini file that is created the first time you run CCleaner.exe or CCleaner64.exe.

If I cut and paste CCleaner64.exe back into it's correct location (i.e., in the main "root" directory where License.txt and portable.dat are located) then I am able to change the language and a new ccleaner.ini will be saved in the same directory as CCleaner64.exe.

I grabbed the portable zip, and expanded it to a drive.In the x64 directory, I launched ccleaner64.exeOn the first launch, it displayed v 5.92The file system dates are April 7. 2022 at 04:42amThe 64 bit version displays "v5.92.9652"I closed it, and launched a second time.This time, it asks several "do you want to run" questions.When CC finally comes up, it is now v6.00.9727Files are dated 5/11/2022 at 01:16 am.Options Keep Updated Automatically is checked.

The main crux of the problem is that Piriform / Avast's idea of a Portable build is to just take the identical 32-bit CCleaner.exe and 64-bit CCleaner64.exe files used with the "regular" installed version of CCleaner, bundle them in a file with some language files and a portable.dat file to make it a portable build, and ensure that any configuration changes made in the interface are saved in a ccleaner.ini file. What they really need to do is re-design CCleaner.exe and CCleaner64.exe files specifically for the portable build so that it can't create a scheduled Emergency Updater task or registry entries and doesn't include other unnecessary features like a Software Updater and Performance Optimizer that really don't belong in a portable program that can be run from a removable USB drive on multiple machines with different operating systems and different software/hardware configurations.

I'm not sure what your script does, but the ccleaner.ini files will contain all the custom settings from your previous CCleaner Portable version. As long as your script only overwrites the old 32-bit CCleaner.exe (if required), 64-bit CCleaner64.exe and portable.dat files (plus any required language files if you use a non-English interface) and does not delete the old ccleaner.ini file or copy over any extraneous files like CCupdate.exe then there shouldn't be any need for your script to re-create the custom settings for your updated interface or perform other cleanup routines. I personally prefer to always keep my CCleaner Portable files in the same folder (in my case, in a folder I created on my removable thumb drive at D:\Portable\CCleaner) so that the path to my CCleaner64.exe file never changes and I won't need to create a new ccleaner.ini file with all the default configuration settings the first time I launch the updated CCleaner64.exe executable that I manually copied and pasted into that folder.-------------64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v100.0.2 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1676 * Macrium Reflect Free v8.0.6758 * CCleaner Free Portable v5.92.9652Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

Just an aside, but note that you should be able to download older CCleaner Portable .zip files by browsing to https: // For example, if you ever need the .zip file for CCleaner Portable v5.76 browse to .

I've never had the v6.00 update pushed out to my CCleaner Free Portable v5.92 (unzipped on 13-Apr-2022 before CCleaner v6.00 was released on 12-May-2022) that I run from a removable USB thumb drive. The ccleaner.ini file I'm using now was copied and pasted from my previous v5.91 portable and currently has:

Note that I was running a test for another user (see my 13-Apr-2022 post in mogli's 5.92 Portable Broken) and made the mistake of unzipping a fresh copy of on my hard drive in C:\Users\\Downloads and immediately double-clicking the CCleaner64.exe file now located the \x64 subfolder, which generated a brand new ccleaner.ini file with all the default settings. As noted in mogli's thread, there is something seriously wrong with the structure of the folders and files in the file and launching that CCleaner64.exe file appeared to create a scheduled CCleaner Update task in Task Scheduler that tries to run the emergency updater CCUpdate.exe, a file that normally isn't bundled with the Portable build. Note that I've deleted this scheduled CCleaner Update task since the image below was captured, as well as CCleanerDU.dll, CCleanerReactivator.dll and all the other unnecessary files and folders bundled inside that aren't required to run the Portable version of CCleaner.

I've never installed the "regular" version of CCleaner Free on my Win 10 computer but when I searched my registry today for "Piriform" I found dozens of registry entries in HKEY_CURRENT_USER\SOFTWARE\Piriform\CCleaner, HKEY_LOCAL_MACHINE\SOFTWARE\Piriform\CCleaner and others. I don't know when these registry entries were first created but I suspect most, if not all, were created when I launched CCIeaner64.exe during my 13-Apr-2022 test of CCleaner Free Portable v5.92 for mogli and created a new ccleaner.ini file (i.e., before I copied over my old v5.91 ccleaner.ini file with my customized settings and deleted all the other unnecessary files and folders bundled inside that aren't required to run the Portable version of CCleaner). Portable software should never be allowed to make these types of changes to the registry. Here's just a partial list of what I found:

My image below shows the three other files [ccleaner.ini, portable.dat and License.txt (optional)] I normally keep in the same folder as my CCleaner64.exe executable. I do not have a system with a 32-bit OS so I don't need the CCleaner.exe executable, and I use the English interface so I do not need the \lang subfolder in that same location. Note that I only use the Custom Clean feature and don't want to use Health Check, Software Updater, Performance Optimizer, or any of the other bloat that's been added to recent versions of CCleaner.

I have a 64-bit OS and use the default English interface, and when I unzip the Portable file on a removable USB thumb drive there are only three essential files I need to keep - CCleaner64.exe and portable.dat plus my "old" ccleaner.ini file (which stores the custom configuration settings I made in my previous CCleaner Portable versions). Hopefully that won't change when CCleaner Portable v6.1 is released next month.

Hi Imacri with almost all zip portable software even after deleting the software leaves entries in the windows registry HKEY_CURRENT_USER/software and HKEY_LOCAL MACHINE/software look for piriform that's ccleaner left overs I have for the most stopped using ccleaner since being baught by avast

Problem signature:Problem Event Name:CLR20r3Problem Signature 01:ccleanerenhancer[1].exeProblem Signature 02: Signature 03:4c19c5b7Problem Signature 04:CCleaner EnhancerProblem Signature 05: Signature 06:4c19c5b7Problem Signature 07:fProblem Signature 08:e9Problem Signature 09:System.InvalidOperationExceptionOS Version:6.0.6001. ID:1033

hi. used your enhancer for a couple of months without issues. i have just updated ccleaner. when i try to run ccleaner enhancer to ensure that it is up to date, i get a message that ccleaner is not installed. there were no problems with the previous version of ccleaner, so assume there is a problem since the update to v3.00.1303 or is it me. any chance of checking, please?

Not stealth, createsHKLM\software\Piriform\CCleanerHKCU\current\software\AvastAdSDKHKCU\current\software\Piriform\CCleanerShould block these on hosts: www.ccleaner.com0.0.0.0 ipm-provider.ff.avast.com0.0.0.0 shepherd.ff.avast.com0.0.0.0 ip-info.ff.avast.com0.0.0.0 license.piriform.com0.0.0.0 ipmcdn.avast.com0.0.0.0 analytics.ff.avast.com0.0.0.0 healthcheck.ccleaner.com0.0.0.0 download.ccleaner.com0.0.0.0 verify.ccleaner.com0.0.0.0

Superfluous language dll's in /lang (currently totalling 1.26MB):To follow up on this further: as per message posted at piriform forums below (url munged by this site's posting script, reconstruct manually from the visible), it seems that English (GB) and English (USA) at least are built into ccleaner.exe itself as these two are listed by respective decimal numbers in the page quoted below but do not appear in the /lang subdirectory of ccleaner; so if you want only these languages just delete all the lang-*.dll's... =32535&st=0&p=193275&hl=+english%20+language%20+dll&fromsearch=1&#entry193275Posted 12 May 2011 - 02:50 PM -codes.aspLook at the "Decimal" column.English is included into the program.


Welcome to the group! You can connect with other members, ge...


bottom of page