[FEATURE REQUEST] Possibility of updating drivers such as snappy driver installer and Driver Booster

[STVGecko]

Please confirm these before moving forward.

• I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
• This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use this template.

Describe the new feature

Can you add the possibility of updating drivers such as snappy driver installer and Driver Booster :
https://sdi-tool.org/ - https://www.iobit.com/en/driver-booster.php

Describe how this new feature could help users

The benefit is similar to that of this superb application: it saves precious time.

[NotaInutilis]

It would indeed be useful! Another open source reference would be Snappy Driver Installer Origin. https://sourceforge.net/projects/snappy-driver-installer-origin/ It seems that this fork is recommended over SDI because of malware issues.

They both work on the same principle though and their sources are driver packs compiled by a third party that are downloaded in their entierty before extracting the useful drivers.

They also rely on other variables and informations than the installed/updated version such as windows version, part ID (to determine compatibility), driver editor (eg microsoft or manufacturer), release date… This way it does not update, for exemple, a gpu driver if the new version does not support your hardware anymore.

I can't really help otherwise, but I hope this information will be useful for the people willing to tackle this issue!

[ladiko]

I can confirm that SDIO is preferable over SDI due to the named issue. I use it portable (which is it by default as it's just a zip file) on an external drive, so previously downloaded driver packages, which can be 1 - 3 GB in size, will not be downloaded again on the next machine. A package usually includes f.e. all recent nvidia video drivers or all amd video drivers, bluetooth drivers separated by chip vendor, audio drivers separated by chip vendor (realtek, connexant, etc.), chipset drivers separated by chipset vendor (intel, amd, nvidia, via etc.).

As Nota Inutilis (@NotaInutilis) describes it perfectly, I also doubt this can be easily integrated into UniGetUI as it works way differently and the whole process of determining which drivers can be used by downloading the ~16MB index file (if it was updated) for the driver packs on each UniGetUI search, wouldn't make much sense. There are too many dependencies just to re-invent / re-implement the wheel.