Sorry, but no, it's not ridiculous. Ridiculous was the 2nd build from last year not being released because it affected tens of millions of installs. With Insider Preview builds, you cannot ever expect 100% reliability - ever. You already know this. Everyone in here that uses an Insider Preview build knows this. If there are 1, 2, or even 5 builds that don't work for a small number of systems, then the program is accomplishing what it set out to achieve - we're one big ẞeta test for future versions of Windows. Not current, future. Not released to the general public, but something you have to actively sign up for, install, and maintain.
If you're not ready to test (and more importantly, if you're not ready for things to break) you really should not be using Insider Preview builds at all.
I'm not trying to be a dick, though I am coming across that way, but it is a matter of fact. No matter how many employees Microsoft has, and how many testbeds they have, things will slip by when you take into account just how many lines of code are incorporated into the OS. But, instead of having things slip by in final versions, now, we Insiders, are the 'second line of defense' to (hopefully) stop major bugs from slipping past. Obviously, even this system is not foolproof - last year's October build proved that.
But complaining about ẞeta builds that don't work - that is not really cool. You know it may not work.
I worked with a user last year (or 2017, forgotten which) for a long time trying to get a particular set of builds working on a system very similar to my own - I was able to install each upgrade flawlessly, and he was not. Same chipset, same generation CPU, similar RAM. He ended up finally upgrading his machine. Meanwhile I had 0 issues for the entire time he was having issues (this went on for 3-4 months, IIRC).
This. Instead of complaining, start writing to folks, asking questions, gathering data for bug reports. That's what we're supposed to be doing as Insiders.