And how is this MSFTs fault?
Sounds like the devs of Chromium have poorly coded the driver so it relied on a particular memory layout or undocumented API and have been caught out. Obviously they never bothered testing Chromium on the Insiders build of 1803 that have been available for months.