Not as "Executable computer programs" installer packaging.
To install hardware things on other operating systems normally takes a simple script, and dropping of a few support files. Most of the required functions are already supported in the OS kernel, and that's relatively easy to upgrade if not. Linux users really never hear of the word drivers or trouble with them - but yeah they do exist as support files and modules.
But windows likes to do it instead with a full blown GUI application 'setup.exe' deployment and all the downsides of that install, when it pulls in other library dependencies and then we have to worry about their security issues. Not to mention, other unwanted programs being installed. Spyware perhaps?
All of the above makes a simple thing like installing a new printer, a complete dance - and a worry when upgrading operating systems, and wondering if this package will be OK going forward or will the printer company write a new one?
Agreed. It would be useful if certification came from somewhere else than the driver manufacturer. Microsoft does do this for some device classes, but they are conflicted when they want to basically sell new operating systems and make obsolescent the old.