On Friday, November 15, Fast Ring Insiders got build 19025. Just four days later, Tuesday, November 19, build 19028 was released. It only contains fixes for a few unimportant bugs:
– We fixed a recent issue that could result in Settings crashing when docking/undocking your device. This issue may have also impacted Action Center launch performance.
– We fixed an issue impacting the performance of the Printers & Scanners section of Settings loading.
– We fixed an issue resulting in the Other People section under Storage Settings not displaying the correct size used.
– We fixed an issue that could result in Windows Update history in Settings saying a Cumulative Update required a reboot, despite it already being installed. This occurred when a Feature on Demand had installed while the cumulative update was originally pending reboot.
– We fixed an issue that could result in the Photos app crashing when interacting with HEVC images.
Source: Windows Insider Blog.
Fast Ring Insider builds are previews for version 20H1, which will be released in about half a year, in Spring 2020. Thinking about how long the intervening test / preview period we still have before general availability occurs, is it really the right decision to release some simple bug fixes as a full feature upgrade, putting Insiders through an hour or two long upgrade process every few days? In my case, on a relatively fast HP laptop, the 19028 upgrade last night took almost three hours.
The Windows Insider team has already successfully tested build upgrades as cumulative updates. Slow Ring Insiders got their 19H2 build upgrades as cumulative updates, which are relatively fast and painless. Why can’t the same CU method be used in Fast Ring upgrades, when the new build really contains no new features, just a few simple bug fixes?
In my, of course strictly personal opinion, releasing a new build every few days just to deliver a few bug fixes is not a good idea, not correct policy. IMO, a full feature upgrade should only be used to deliver new features.
I implore the Insider Team to exercise some common sense (and some sense of scale, scope and installation effort), when delivering new builds and bug fixes.
Author: Kari Finn
A former Windows Insider MVP, Kari started in computing in the mid 80’s writing code for VAX / VMS systems. Since then, he’s worked in a variety of IT positions. He specializes in Windows image capture, customization, repair and deployment as well as Hyper-V virtualization. Kari is a proud Team Member at number #1 Windows site TenForums.com.