Before installing a device or a driver, first ....  

I'm not seeing how a driver package which includes additional software components for a hardware device can become installed successfully in version 1903, but the drivers don't do a thing. Autoruns lists two (verified) INF files associated with the device which should contain all the information and device settings which Window's device installation components used to install the driver package.

Before Windows ever installed the driver, Windows analyzed the driver package's digital signature. A signature was present and so Windows used the signature to validate the files in the driver package. AFAICT, the digital signature should be recognized whether if I'm running Windows version 1709, 1803, 1809, 1903, or 1909, or whatever upcoming version is installed.

It's not clear why the driver worked in Windows 10 version 1709 after a successful first install, and then worked again in version 1809 after a successfull re-install of the device on the same computer. But after re-installing in version 1903 or 1909, I get kernel faults where the integrity of the drivers appear to throw errors with Windows.

I shouldn't have to consider disabling Windows driver signature verification to allow a driver that's already signed to be installed as an unsigned driver. That doesn't make sense. It not only sounds like nonsense, but if anyone ever noticed, TenForums never wrote a tutorial on disabling driver signature verification. I'm guessing the chances are was probably because even if there were precautions posted to end users to use the methods of instructions at their own risk, it could potentially make a system unstable, and so [he] chose rather not to endorse it.

I've read everything that I could find and nobody has a believable reason that explains what's causing this.
Even this Microsoft article fails to shed any light. The same driver package that I got from the manufacturer's site is in Microsoft's Windows Update Catalog. I tried the packages from both WUC and the manufacturer's site and I get faults and errors having to do with Windows not able to communicate.

Can anyone explain if this must have to do with signed drivers no longer verified or if it has to do with something else?

Of what I could understand of this article due to heavy accent is this : you have had a driver that worked right up till version 190x of windows where it started throwing kernel faults .

Basically this is correct on a level , you see Windows 10 is being slowly modified in an attempt to follow Mobile OSes (Like Google Chrome) , the variety of hardware settings are worked on to be integrated within Windows interface/settings and not 3rd party control panels (So I assume here your driver must have one of those third party control utility to handle it) , so it had been noticed that this approach had been passed to all manufacturers of devices and drivers where they started slowly removing control panels / autorun utilities and hand all tweaks to windows

Of course there had been few manufacturers that announced that their devices has more functions than Windows settings has to offer and hence to continue , Microsoft allowed them to release their control panels in the form of Store Apps than rather independent startup utilities (Just like Mobile OSes) .

In the process Microsoft started to legacy out those drivers that don't comply to that standard by crippling their setups / operation some (they try to not be clear about it so it won't backfire at them by users all at once) , so yea its deliberate , and unless you get an updated driver from manufacturer to comply with their new standards all your drivers may inevitably reach an eol phase where they won't even setup due to Windows version incompatibility .

What will happen then ? simply that there will be drivers in Windows Update catalog that are pretty basic but comply with Windows standards .

So now that you know its you choice to continue with the cycle of Windows updates or stick to the 1809 build for a while until there is no other choice .

nIGHTmAYOR said:

Of what I could understand of this article due to heavy accent is this : you have had a driver that worked right up till version 190x of windows where it started throwing kernel faults .

Basically this is correct on a level , you see Windows 10 is being slowly modified in an attempt to follow Mobile OSes (Like Google Chrome) , the variety of hardware settings are worked on to be integrated within Windows interface/settings and not 3rd party control panels (So I assume here your driver must have one of those third party control utility to handle it) , so it had been noticed that this approach had been passed to all manufacturers of devices and drivers where they started slowly removing control panels / autorun utilities and hand all tweaks to windows

Of course there had been few manufacturers that announced that their devices has more functions than Windows settings has to offer and hence to continue , Microsoft allowed them to release their control panels in the form of Store Apps than rather independent startup utilities (Just like Mobile OSes) .

In the process Microsoft started to legacy out those drivers that don't comply to that standard by crippling their setups / operation some (they try to not be clear about it so it won't backfire at them by users all at once) , so yea its deliberate , and unless you get an updated driver from manufacturer to comply with their new standards all your drivers may inevitably reach an eol phase where they won't even setup due to Windows version incompatibility .

What will happen then ? simply that there will be drivers in Windows Update catalog that are pretty basic but comply with Windows standards .

So now that you know its you choice to continue with the cycle of Windows updates or stick to the 1809 build for a while until there is no other choice .

Thanks for the informative notes. Very interesting.
So in a nutshell, [MS] embraced a move toward unifying the worlds between desktop and mobile to converge two platforms and form a new "system" where they essentially are mandating which independent files will be permitted now to load on Windows 10.

RIP Windows 7
Oct 22, 2009 - January 14, 2020