So it's stuck on updating a driver for over 10 minutes, nothing is showing on the progress bar, and Cancel doesn't do anything.
what should I do now?
If you are sure that it's stuck and not just taking a long time (look in Task Manager to see if it's doing anything) then:
Close CCleaner using the 'X' in the top right. (Or 'End Task' it in Task Manager if you have to).
Next time CCleaner offers that particular update to ignore that update version.
Hey Nuke, how do we know, or how can we figure out which updates to get?? Google the update's name?
CCleaner tells you what it has found to update, and (usually) what it thinks the 'newest' version should be.
ie In your screenshot it says it's trying to update a NVIDIA audio driver to v1.3.40.14
The scan screen before that one also tells you what it has found if/when you click on the arrows to expand the entries:
<img alt="image.png" class="ipsImage ipsImage_thumbnailed" data-fileid="19252" data-ratio="56.70" data-unique="p6kybxytt" width="993" src="<fileStore.core_Attachment>/monthly_2024_07/image.png.c26581c5ee110cbe9a03a16a10d21285.png">
You can then click the 'Details' box to get this screen with more detail, and where you can also tell it to either:
- 'Pause Updates' which will stop it offering you any future updates for that driver.
-
'Skip this version' which as it says won't offer again until there is a newer version.
</li>
You should always note that just because there is a 'newer' version of a driver doesn't mean that it is meant for your particular computer, or that it will do anything different for you than the one you already have.
In the worst cases it may not suit your machine at all, and the device will stop working as it should until you roll the driver back again.
That's why CCleaner's Driver Updater has a '<strong><em>+Fix a problem</em></strong>' button to try and help if that happens to you.
<img alt="image.png" class="ipsImage ipsImage_thumbnailed" data-fileid="19254" data-ratio="99.82" data-unique="a0t08xk0j" width="567" src="<fileStore.core_Attachment>/monthly_2024_07/image.png.8b220c6112e69416faed22a60d6c6607.png">
PS. You may have noticed from my screenshots that I'm one of the many who don't update drivers just because there is a newer version.
If your machine is working properly then there is normally no need to update your device drivers.
The old saying- If it's working then you don't need to fix it. (and if you try then you might just break it).
2 hours ago, nukecad said:<div class="ipsQuote_contents"> <p> PS. You may have noticed from my screenshots that I'm one of the many who don't update drivers just because there is a newer version. If your machine is working properly then there is normally no need to update your device drivers. The old saying- If it's working then you don't need to fix it. (and if you try then you might just break it). </p> </div>
That is some good advice Nuke, thanks for the help!
On 21/07/2024 at 02:22, nukecad said:<div class="ipsQuote_contents"> <p> f your machine is working properly then there is normally no need to update your device drivers. </p> </div>
Say Nuke, what would be the signs for the machine not working properly?
For drivers not working properly?
Sound issues, screen issues, wifi and/or bluetooth issues, etc, etc. up to and including CPU or drive access issues that could make it unbootable.
Basically anything that uses/needs a driver can stop working properly or stop working altogether if it doesn’t have the driver that it needs or has the 'wrong' driver.
You only have to read some of the threads here to see examples of what can go wrong with a mismatched device/driver pairing.
OK mate I'll try and keep all this in mind! Thanks for your insight!
BTW, don't worry about it too much the drivers you have are fine unless you start to see such problems.
So many, myself included, leave automatic driver updaters alone and don't take a gamble.
There again they can be useful if you do already have an issue with a particular device driver.
Right on, How do I give you a big Thumbs Up!
2 hours ago, nukecad said:<div class="ipsQuote_contents ipsClearfix" data-gramm="false"> <p> You only have to read some of the threads here to see examples of what <em>can</em> go wrong with a mismatched device/driver pairing. </p> </div>
And having just said that we get a new example: