The CCleaner Bug Reporting board now has multiple reports of CCleaner Pro v users who experienced BSODs after allowing the new Driver Updater feature to update their drivers - see BenRiver's 1 Driver Update Caused BSD for one example. I wouldn't be surprised to learn that Avast has added Driver Updater to CCleaner v5.82 so they can use CCleaner users as beta testers for their own Avast Driver Update utility.Ħ4-bit Win 10 Pro v20H2 build 19042.1052 * Firefox v89.0.1 * Microsoft Defender v.5 * Malwarebytes Premium v4.4.0.117- * CCleaner Free Portable v I don't know if the standalone Avast Driver Updater is currently flagged by Malwarebytes as a PUP but I'm curious to see if Malwarebytes finally stops giving Avast (who acquired Piriform in 2017) a free pass and starts flagging CCleaner as a PUP.
Simply excluding all Intel network cards from the driver scan seems like a quick and dirty way to solve the problem, and it makes me wonder how many other outdated drivers are being recommended (and automatically installed) by Driver Updater in CCleaner Pro.Īs a general rule most third-party driver updater and registry cleaner utilities are detected by Malwarebytes as PUPs (potentially unwanted programs). This has been corrected, so that such driver updates for Intel network cards should no longer be offered as of tomorrow morning. According to employee Ezra CCleaner's post today (1) in Two Issues with Driver UpdaterDriver Updater will be "fixed" so that it no longer looks for driver updates for Intel network cards.įor the point 1 It's detecting an older version as if it's newer (see screenshot).
I've seen reports where the new Driver Updater feature in CCleaner v5.82 is offering outdated drivers for Intel network cards that are older than the installed version.
0 kommentar(er)
