Especially not when your point (whatever you think it may be) is made here.
Microsoft did not produce the driver in question. There is not any evidence that it does what you say it does - that you have presented, and being the accuser, that burden is yours. Microsoft is not responsible for the hardware devices they do not produce
and rely (always have, likely always will) on the manufacturer to do with their devices and the associated support products - such as drivers and software - what they want/what they feel is best for THEIR customers.
Your issue about this product (the subject of this conversation) is, was and will remain to be one with the manufacturer of the product in question - not Microsoft.
You definitely do not have to install hardware device drivers that Microsoft offers and - as many have said over the years in these very forums - Microsoft did not likely manufacture nor do they support the hardware you utilize and even if they are offering
the drivers through their normal method of pushing updates, you would (likely always will) be better served going straight to the manufacturer for the hardware device drivers and software and HIDING any hardware updates for non-Microsoft hardware offered to
you via Microsoft Updates.
You sentence, "He contacts the software company and blames them because their product is no longer any good to him." describes exactly what should happen. If their driver, even one they gave to Microsoft to be pushed via their service, is flawed - the issue
still lies with the manufacturer of the product and the driver.
So, although you may have a point - it is LOST here. Link to where you complained to the manufacturer on their forums...