johnccleaner

Would you mind providing us with more information so that this can be looked into? For instance, what version of Windows is installed on the computer? If it's Windows 10, can you also let us know the OS Build and Experience (if present)? That information can be found in the Settings App > System > About > Windows specifications section. The brand and model of the computer could also help, as would the report from the System Information utility in Windows? You can save the System Information report using the following steps: Open the "Run" dialog in Windows (On the keyboard, hold the "Windows" () and "R" keys simultaneously) Type: msinfo32.exe > click OK Click File > Save... The following log files could also be helpful. C:\Program Files\CCleaner\Data\DUState.dat C:\Program Files\CCleaner\LOG\DriverUpdaterLib.log C:\Windows\INF\setupapi.dev.log Of course, I understand completely if you don't want to send along all this information 'out in the open' like on a forum - you're more than welcome to instead contact our support team directly via the Contact Us form here: https://support.piriform.com/hc/en-us/requests/new?ticket_form_id=86507 or by emailing support@ccleaner.com and sending the needed information along that way instead. Also, keep in mind that System Restore is entirely a Microsoft system; we actually don't have any interaction with this system save for deleting these points when asked to via the Tools > System Restore section of CCleaner; when new System Restore points are created as part of the Driver Update, this is actually a Windows function that does it. You'd think that you could then use a Windows function to restore them, accordingly... Unfortunately, in Windows 10 especially, it seems to have gotten a touch more temperamental (though I'm not sure if that's because of changes Microsoft's made or various antivirus providers).

CCleaner for Windows is typically sold on an annual basis; we also sometimes offer two or three-year licenses (this will be marked in any relevant promotion). We do not offer 'one-time purchases' of any of our products.

That sounds like there was a hardware failure, then (and so sending it to Lenovo for repair was very likely the best option to repair the problem) - if it had been an installed driver that had caused the problem, that shouldn't have interfered with the recovery media, since that would have its own set of drivers and could just, at worst, install a fresh version of Windows onto the computer in that case. In any event, I'm certain Lenovo repair will get it back up and running promptly.

You can check or uncheck the programs listed in the Security tab of Health Check, unchecking the ones that you do not want to update. Like the other options in the Health Check, this is not remembered from one run to the other. Custom Clean doesn't do any application updates whatsoever; you would go to the Tools > Software Updater for that. Simply check or uncheck the programs you want to update there - quite similar to how it's presented in the Health Check, in fact. Basically, Health Check (including its Security tab) is meant to be a semi-automated tool for inexperienced or less confident users who just want to 'push a button and make it better' - for a user like yourself, you may prefer using the individual options for greater control. I'll be happy to get your feedback to our development team, though, so we can consider these points further!

We have an article with some general advice on resolving these issues located here: https://support.piriform.com/hc/en-us/articles/4402564268429 If problems persist, please get in contact with our support team via the Contact Us form located here: https://support.piriform.com/hc/en-us/articles/4402564268429 or by emailing support@ccleaner.com directly.

We have an article with some general advice on resolving these issues located here: https://support.piriform.com/hc/en-us/articles/4402564268429 If problems persist, please get in contact with our support team via the Contact Us form located here: https://support.piriform.com/hc/en-us/articles/4402564268429 or by emailing support@ccleaner.com directly. (Regarding the touchpad specifically, you may be able to work around this long enough for any needed repair by using a mouse instead.)

Please note that, per the developers of IrfanView, the 32-bit version is recommended for most users: https://www.irfanview.com/64bit.htm The only advantages relate to immensely large images that most users will not be dealing with (even an 8K BMP photo would only be about 35MB, and even 32-bit IrfanView can open files that are well over a GB), while the 32-bit version is smaller, more compatible, has more features (command-line options, specifically) and has more plugins that work for it. Just food for thought.

Please get in contact with our support team via our Contact Us form here: https://support.piriform.com/hc/en-us/requests/new?ticket_form_id=86507 or via emailing support@ccleaner.com so that we can look into this matter further - Kamo shouldn't be able to affect your internet connection at all, so that's a very odd behavior indeed. (To clarify, adding a site to the Allowed Sites simply ensures that the "Browser cleanup schedule" won't clean cookies for it; there isn't a way to turn off the anti-tracking features for a single website, short of turning off Kamo entirely as you mentioned doing.)

Just to clarify, at this time, the whitelist only affects the cookie cleaning portion of Kamo ("Browser cleanup schedule") - there is not a way to disable the anti-track functions for a single website, so there isn't really a way to 'turn off Kamo' for a particular website (short of, well, turning off Kamo). What you could do would be to disable Kamo entirely for a browser that you don't commonly use, say Microsoft Edge, by going to "Browser Protection" > unchecking that browser > visiting the website with that browser. That should then prevent Kamo from affecting that browser, allowing the website to work as expected. Alternately, the process you describe will certainly work as well. If you'd be willing to let me know the website in question, I can certainly bring that to the attention of our development team as well so we can look into it and see if there's anything that can be done on our side as well.

Please contact Support directly about this matter, either via our Contact Us form here: https://support.piriform.com/hc/en-us/requests/new?ticket_form_id=86507 or by emailing support@ccleaner.com for assistance with this or any other registration/licensing inquiries.

This is actually working as expected - when CCleaner Browser isn't 'open' (in the sense of having a browser window open), it still leaves a very small portion - this then runs a task to check for updates periodically (I believe this is indeed intended to run once and hour). When that task completes, CCleaner 'sees' the system event that a CCleaner Browser process has closed, which then prompts a cleaning event, as that's the trigger for these cleaning events. As such, both programs are doing exactly what they're supposed to. You can control this behavior in CCleaner's Options > Smart Cleaning; you could set it to clean this browser without notifications, or even to not monitor this browser at all (if you want to rely on manual cleaning and/or CCleaner Browser's own tools). More information on the Smart Cleaning function here: https://support.piriform.com/hc/en-us/articles/360015058012 and information on cleaning CCleaner Browser within the software here: https://support.piriform.com/hc/en-us/articles/360028862611

This can occur if the manufacturer of the driver changed how versions were numbered. What you'd want to check would be the release dates of the drivers in question, which you can find in the 'Learn More' section for each driver; I believe that's what the Driver Updater actually uses to determine if a driver is newer or not.

We don't currently test or design CCleaner for use with Powershell. We offer some command line parameters listed here: https://support.piriform.com/hc/en-us/articles/360047885872-Command-line-parameters-for-CCleaner-for-Windows for use with the Command Prompt or via batch files.

If you'd be willing to let me know the website in question, I'll be happy to get that information to our development team for further investigation. Alternately, you can send this request (including the website in question) to support@ccleaner.com if you do not want the site to be disclosed here on the forum - whichever works better for you!

Well, yes, I'm sure there will be... unsupported options to bypass the requirement. People get creative. :) I'm just discussing the requirements as written, though, since that seems like the best way to avoid unwanted issues! We can but hope! Tinfoil hat warning: I have a feeling that they're insisting on this stuff to try to make it harder to bootleg Windows. (And/or to make it harder to dual-boot unacceptable 'alternative' OSes.) If so, then I doubt they'll drop the requirement no matter the outrage. But we'll see. There's some time before it actually comes out, after all.