KB4601937 Windows 10 Insider Preview Dev Build 21292.1010 - Jan. 15 Insider

It downloaded and installed during the settings screen portion fine. Then ran fine during the first grey screen process when that made it to 100% then rebooted and hit the normal 30% reboot level it did indeed restart but when it restarted I was met with a GSOD (WHEA_UNCORRECTABLE_ERROR).
It collected data and restarted the PC, which then said there is no boot device found. I pressed ctrl - alt - del and entered UEFI and sure enough my M.2 NVMe drive (MP500) was not listed. I plugged in a Live Ubuntu USB to boot from to see if that would see my boot drive. I powered down my PC via the power button and then turned it back on. I pressed F11 for the boot menu (ASRock B450 MB) when that opened my MP 500 boot drive was listed so I selected it expecting the update to rollback.
It did not, what it did was display the 30% progress information screen and restarted. Then restarted again with what looked to be a generic display driver and then finished the update. Everything so far seems okay now.

I was getting ready to start from scratch.

Here is a HWinfo64 report of my PC Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

swarfega said:

Installed. So RS now replaces FE?

I think in the Active development branch, you have 3 subsets: RS_PRERELEASE, Mn_RELEASE, Fe_RELEASE. I have even heard that at some point you can even see a Cobalt one (Co). According to my understanding, depending on how advanced the features are in those subsets, one can be akin to Fast ring and the other to Skip ahead. Under what algorithm MS does it, no clue, not a scintilla.

Like I said this is just my understanding.

Fast...

f14tomcat said:

We expect to move all Insiders in the Dev Channel back to receiving builds from RS_PRERELEASE sometime after the holidays.

Windows 10 Insider Preview Dev Build 20279.1 (fe_release) - Dec. 14

Me thinks the Fe was a brief experiment in something and never was intended to hang around for long.


Ah! More clarification....

but we wanted to test our ability to quickly follow-up a flight with another flight.

Fe was not supposed to hang around. I suppose it was probably the same fate for Mn, but they are still around. We will see what happens after the holidays if MS holds on to its promises. They (MS) certainly have their way of confusing everybody...