You said " You should NEVER have to pay for a driver for any hardware " I say, " I don't pay for the drivers or other updates, I pay for the Program TweakBit \ Driver Updater to scan and detect what Programs, Utilities and Driver installed on my system (workstation) that are out of date and need updating." I would point out that the Microsoft Update updates only Microsoft's OS's and Microsoft Application Programs (the later if selected) and other programs have updater's nowadays and some in fact have a pop-up when you use them to tell you that an update is available, which you should use to fix any bugs and have the respective program or utility perform optimally and better. That said, I would remind all that there are at least 69% of drivers that are installed on any Computer Workstation in particular to extra installed Hardware that is not automatically updated by Microsoft or other Publishers for which we then have utility Programs such as TweakBit Driver Update that wil do the job for you. - I trust that clears up what I pay for and what I don't and would agree with you that I would never pay for a driver for any hardware.
What makes you think that Programs / Utilities of this type do not cross reference the need to update a driver or program with the actual Publisher of the driver or program ???
There are some honks out there, however there are also some legitimate updater type utilities and programs that do a legitimate job and in fact perform the correct update of the utility or program or driver that is out of date on your system workstation if you have installed a utility program such as TweakBit Driver Update to do the job for you.
Until Malware Bytes in the post back in 2016 suggests that it is a Virus or lately lists it as a PUP, both of which are contentious to say the least, I will refrain from taking MalwareBytes detection as being a PUP and disregard the old post of 2016 suggesting it is a virus.
My message to MalwareByts is, "Update, Update, Revise, Revise, all that you post or list whereas the old posts like the 2016 are out of date and are in my opinion misleading the consumer referring to old data and Publishers version of a particular anomaly in one of their old program versions. Where the old data of 2016 is still applicable to the TweakBit Driver Update, remains to be seen, as I am awaiting a reply from TweakBit in regard to this matter.
Regards pcbugfixer 😈