Comment Microsoft has followed its accidental issuance of Windows Insider with a kind of reluctant explanation: something changed and bad things happened. Soz
The publication, in a community forum, came after the software giant gave its army of unpaid testers an unexpected kick in the form of an unproven internal compilation of Windows 10 over the Windows Insider network .
The explanation does little to reassure intrepid testers that the Windows team has a lot of process control and, frankly, it is not a good aspect for the program, which depends on the goodwill of its participants.
You have 10 days
What happened? "A configuration change allowed this compilation to be released on several rings simultaneously, including external rings."
What should you do? If you installed the device, it is up to you to undo the Microsoft speed increase by rolling backwards as soon as possible.
The clock does not stop.
The company warns that lucky users of build 18947 have about ten days to do it (possibly less if Storage Sense is enabled), otherwise, getting rid of accidental broadcasting will be much more difficult.
If the installation is still pending, then a pause, restart and resume should take care of things.  To summarize, the Windows Insider program has three (sometimes four) rings. There is a preview of the version, where users can review the fixes for the current version of Windows 10 (in this case, the May 2019 update, also known as 19H1). Then there is the Slow Ring, which currently enjoys the next version of Windows 10, which will be released in October and is known as 19H2. Finally, there are the Fast and Skip Ahead rings, which are playing with Windows 10, 20H1 next year.
On July 24, Microsoft "unintentionally" sent an unproven internal version of 20H1 to all the rings, starting them at 19H1. and 19H2 in the year 2020 through the scaly code.
While some were happy to get a preview of the interface ideas that bounced in the bowels of Redmond, others were very impressed. After all, while Windows Insiders understand that all compilations are previewed, those rings exist to mitigate the risk.
Waving a red flag
The incident raises some awkward questions.
What exchange control, if any, is the team. Using that allowed someone to make the change? It is assumed that the slow ring is getting the equivalent of cumulative updates: how did a full compilation get there? Could the same thing happen with the regular Windows Update channel? What exactly has been done to ensure that this does not happen again?
And, of course, what do you do if you can't go back?
Memo to Microsoft: Windows 10 is broken and corrections cannot wait
The incident is, in the first place, an example of the quality problems that have beset the Windows team have not disappeared, even after the horrors of the October 2018 Update. Secondly, it is more evidence that, at best, the Windows Insider team really needs to work a little more on its communication or, worse yet, that you don't think there is a problem.
We suggest the team carefully examine how Cloudflare handled an incident that destroyed a part of the Internet. Or even verify how the Azure gang has dealt with its own TITSUP.
And then think if you simply say "we have made the necessary remediation in our Flighting service and we have implemented additional changes to help prevent this from happening in the future" is really enough after Windows Insiders PCs all over the world have been blocked due to a mysterious "configuration change". ®
Balance consumerization and corporate control.