As Build 17133 progressed through the rings, we discovered some reliability issues we wanted to fix.
"In certain cases, these reliability issues could have led to a higher percentage of BSOD [Blue Screen of Death] on PCs, for example".More news: South Africa backs Morocco for 2026 SWC
The delay also appears to have given Microsoft more time to think about its Windows 10 updates naming scheme. Microsoft has decided against fixing the bug in a repackaged final update and has released a new beta build instead.
If build 17134 reaches the necessary criteria, this will be the build that rolls out to the public later this month. The only said changes come in the form of fixes from last week's Cumulative Update (KB4100375) and few general fixes for the overall OS. The recent RTM version was dropped from release candidate status due to a blocking bug that caused PCs to more frequently go into BSODs.More news: US rescue team recovers bodies of missing Indian and his daughter
Supremo of the Windows Insider programme, Dona Sarkar, dropped a hint last night as to what might have occurred with the release of build 17134 to the courageous soldiers on the Fast ring. Microsoft has not revealed the exact reason for the blocking bug, or why it was discovered at the last moment.
"This just reinforces that Windows Insiders are critical to helping us find and fix issues before releasing feature updates to all our customers", the Insider team adds.
Past releases have shown that even smaller Windows updates result in an increased number of bugs and issues that Windows users experience after installation.More news: United States tells watchdog Russian Federation 'may have tampered' with Douma attack site