Safe to trust a driver publisher?

AlecEiffel

Hi all,

Is it generally considered safe to trust a driver publisher? When installing a new Epson printer I get the choice at the driver install stage to trust Seiko Epson. Its default ticked to trust. Should I keep this? If I trust it to install the initial driver is it safe to trust future driver updates?

If I trust it and decide to revoke it is it simply a case of deleting the certificate in the local computer certificates folder (trusted publishers)?

esuhl

I've never ticked the box to "always allow". I definitely want to know when a driver is installed on my PC.

AlecEiffel wrote: »

If I trust it and decide to revoke it is it simply a case of deleting the certificate in the local computer certificates folder (trusted publishers)?

Good question! Anyone know?

were

I always would like to choose, or at least be notified and given a choice when the driver is updated.

MS drivers are often not the newest drivers.

Manufacturers normally offer a better and more up to date driver than MS, because mostly the manufacturer will make the driver for MS. WHL tested and approved cost £250 per O/S family, but some smaller companies, or limited batches, or older model products, it was probably not worth a company spending on this, and you are fortunate by the copany to still show some interest in their product giving you updated driver support for a dead revenue stream.

I always check the version number, backup the old driver, install the newer version and sometimes you my get a bug fix/feature text too. Both wifi and cabled nics are notorious for driver revisions, and so a graphics cards.

I do know of people who have be caught out with HP server RAID updates on drives - via firmware upgrades, all the data was unreadable after. Also on this page others seem to have been caught out with driver update from MS - https://forums.moneysavingexpert.com/discussion/5749441 . There are other forum users here who complain about MS updates clobbering their system, and those updates are MS certified

The other school if though is 'if it ain't broke, then don't fix it.'

At work continually patching batches MS servers after hours, sometimes the small hours of the morning, and weekends, has been a pain, esp if you have 1500 servers