New
#150
...so it's perhaps lousy drivers' specification and verification / validation process that OEMs are able to circumvent easily?
(how many have we had these over the years? This is most recent change: https://techcommunity.microsoft.com/...y/ba-p/1389785)
But also on the other hand: why 1909 release would work absolutely fine with the latest Samsung NVMe driver - as such this driver has been released to masses and Windows allows installing it either - whereas 2004 would suddenly start having problems?
What has changed in I/O domain so significantly lately?
Why don't I have the same problem with my dated AMD driver?
I detect lack of integrity here, dear Watson.