Re: They say history repeats itself.
Eventually HP's support admitted that the scanner driver was broken by the Windows 10 Update.
Let me fix that for you...
"Eventually HO's support passed the buck and blamed Microsoft"
you see, there is the right way to code drivers, the wrong way to code drivers and coding drivers that fit within the guidelines for 100% compatibility with windows.
Devs have a habit of taking shortcuts to get a piece of code out the door on time instead of properly. They plan to fix it sometime soon in an update, but quite often they don't get around to fixing it and hope nobody notices that they screwed it up in the first place.
Windows update comes along and it will fix some bit of bad code that some previous MS dev strung together after a hard night of drinking and womanising. playing D&D and binge watching TBBT. and inadvertently breaking a bit of code from some third party who was not following the rules.
This happened a few years ago with I think it was windows 7 service pack 2. when lots of software was using a non standard way of reading from memory. The same loophole was being used by miscreants so Microsoft decided to close the hole. Devs were given months and months to update code so that windows update would not break their code. Some fixed it, but plenty did not and charged companies lots of money to fix software they blamed for Microsoft breaking....