1703->1709 BSOD 0xc00000bb on devices with NVMe SSD's

I have an Asus  ROG Strix Z370-H Gaming board with a Samsung NVMe    SSD 960.
Up to v 1709 I had no problems.
When I tried to update to 1803 the update fails with different errors which are vaguely related to a driver issue, according to thing I found on MS site. There was no way to find out which driver. The update kept re-downloading and installing.
I then made the mistake to try the update through Medi creation tool. That resulted in a botched install that tried to roll back but could not, and bricked my PC.
Next I tried a clean install of 1803. This kept failing due to BSODs.
I decided to go back to a clean 1709 install, and put windows update in Semi Annual Channel +365 days.
Since then , no problems.
A month later , after OS Build 17134.48 came out, I tried to update again - it failed again.
I dare not try with OS Build 17134.81.
A second computer I tried this update on is an HP Probook 440 G5 , which has an Intel Pro 6000p. This was an update from 1703. It updated without a problem, but since then had an assortment of BSODs, mostly "critical process died".
To make things worse, the OS does not create any dump files to analyze.
I called HP support who kindly sent me to Microsoft to work it out with them. Yeah, right.
I did a factory reset to 1703 (took over 2 hours) and upgraded to 1709. So far, no BSODs.
The intel ssd is mentioned in the incompatibility list of the first 1803 versions. But the MS description of the errors is quite different then what I had:
"When attempting to upgrade to the Window 10 April 2018 Update, select devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series may repeatedly enter a UEFI screen after restart or stop working."

My conclusion is that MS completely screwed this update.
I know quite a few people who's PC was bricked by the automatic update. Some have Win 10 Home, so they cannot delay this update.
I would not be surprised if a large class action lawsuit is opened against MS.
In my business we have 20 PCs with WIn 10 1709. If they were bricked we would suffer significant financial and reputation damage. Luckily all our PCs are set to Semi Annual Channel +365 days., and I hope none will get this update.
I think if you have an ssd machine, you should avoid this update for now. Don't trust MS on this update. You might suffer significant damage. If you can, back your computer with an imaging program such as Acronis TI . This is the fastest way to get back up should this update brick your PC.
Absurdly, if you have an old PC with HDD you are probably safe, at least from the few PCs I updated.
Unbelievable.