[Update by largest version number, not latest date]

On 28/07/2021 at 09:09, MeganCCleaner said:

Hi @Anthony Dean Exactly as you've noticed, we use release dates as criteria for driver updates, rather than version numbers, and in some cases a newer driver may actually have a smaller version number because of how different manufacturers use different numbering ranges.

For example, for a Intel device on Windows 10, the version of a default Microsoft driver can be 10.0.19041.1 (date: 06/21/2006), but the newer driver supplied by Intel may have a driver version 9.4.0.1025 (date 07/31/2013). The Intel driver is preferred because its release date has a higher priority.

However I can definitely understand your concern with this and I also feel as though it would be ideal for the end user to have an option to select their preference; I'll send all of this feedback directly over to our management team for further review, and as a suggestion.

Sadly it's something the average clueless consumer wouldn't really understand from the start that a newer driver may have a lower version number (if by the same brand or updating over the default one from Windows 10

Honestly people don't look at the information that Ccleaner clearly shows if they would take the time to look, the average consumer will just click scan then click update without a care in the world then complain when theres something they don't like but could have avoided if they took the time to read what's in plain sight at the click of a button

[Driver Updater Crashed my PC DO NOT USE]

On 04/08/2021 at 14:04, reservoirjack said:

I've been a loyal CCleaner user for years. Never had any problems so I wanted to buy the product. Signed up for the trial, ran the driver updater, trusted it to update the correct drivers, and suddenly my computer would only restart to blue screen. System restore points wouldn't work either. 

I fixed this by restarting in safe mode with networking, opening CCleaner, going to driver updater again, "fix this problem", only to find CCleaner can only restore drivers it originally installed...  So the advice on their website did not help me one bit.

Next, I went to the windows search bar and typed recovery, found system restore, and that's where I'm at. Last night the system could not restore from command prompt, but hopefully it can restore from safe mode since I got it to reboot.

CCleaner, remove the genius that developed the driver updater and instead have him at the ready to "chat now" with  working chat now option so toy can help your users with this? This could sink your company. It's costing your basic PC user a lot of money to FIX YOUR PROBLEM. 

Wow. Not able to revert the drivers or system restore. I can't attach a picture, but did get a specific error this time. It says -

"What failed: RTKVHD64.sys" 

Bruh all you had to do is temporarily boot into "Disable Driver Signature Enforcement" mode and see IF it boots, if it does then test audio, then try a normal reboot, if it BSODs then just reboot back into "Disable Driver Signature Enforcement" and revert the Realtek driver to the previous version or simply uninstall it entirely, this isn't Piriforms problem your PC crashed because windows apparently didn't want to boot the machine with a new Realtek driver that hasn't gotten approved by microsoft yet, that's literally WHY your pc would refuse to boot (unless via disable driver verification mode).

 

This driver RTKVHD64.sys causes so many BSOD's for so many people all the time, this has nothing to do with Piriforms product and what it does, next time maybe go search up google about exactly what driver it is, why it crashed and what to do rather than post on the forums saying "DO NOT USE" and scaring people for no reason.

 

I just updated my drivers, which included Realtek audio as well (yes, RTKVHD64.sys driver is a part of the update) and rebooted just fine.  Some people get boned by it, some do not, it's just down to luck and your pc model and age, blame Realtek

On 05/08/2021 at 06:06, AnFe said:

The same happened to me
I am now reinstalling Win10, loosing all my personal data and installed programs.
I am lucky to have a backup from only a few days ago.

driver update is fatal, do not use it.

bulls**t, see my reply above to the other user, that Realtek driver is always causing problems for people, this isn't a fatal problem done by Ccleaner, all you had to do is boot in "Disable Driver Signature Enforcement" and see IF it does boot and you do have audio, after that a normal reboot should work, if not reboot in that same mode and uninstall the damn drivers and let windows reinstall them instead, it'll be an slightly older version but it'll be a verified by microsoft one so.