Most of us approaching Microsoft to dump a latest and biggest chronicle of a final chronicle of Windows yesterday. The rarely expected chronicle 1803, Redstone 4 — that many of us have been contrast for weeks — looked prepared to go … until it wasn’t.
Rumors are drifting but, as of this writing, a tangible means for a check isn’t public.
Microsoft, of course, has never committed to a recover date. Or a build number. Or even a hokey “Spring after Fall Creators Update” character name, for that matter. (I’m still plugging for “Terry Myerson Swansong version” though doubt it’ll benefit traction.)
Instead of a new version, all we got was a small patch, KB 4100375, that lifted a build series from 17133.1 (which was expelled to a Fast ring on Mar 27) to 17133.73. The official blog post, co-authored by Dona Sarkar and Brandon LeBlanc, says:
UPDATE 4/10: We have expelled KB4100375 (OS Build 17133.73) to Windows Insiders using Build 17133 in a Fast, Slow, and Release Preview rings. This refurbish includes a following peculiarity improvements (no new OS features):
Addresses a PDF confidence emanate in Microsoft Edge.
Addresses an emanate that, in some instances, prevents Internet Explorer from identifying tradition controls.
Security updates to Internet Explorer, Microsoft Edge, Microsoft scripting engine, Windows kernel, Microsoft graphics component, Windows Server, Windows cryptography, and Windows datacenter networking.
Which seems formally generic, though it leaves a lot of shake room — and positively no reason for a delay.
The download is coyly labeled “Cumulative Update for Windows 10 Version Next.”
Zac Bowden, stating on Windows Central, attributes a check to a “blocking bug” — which, in normal English, usually means “a bug so bad that Microsoft figured they improved stop a rollout”:
According to my sources, over a weekend Microsoft found a restraint bug that, while apparently rather rare, is impactful adequate to reason a recover until a emanate is fixed. … Thanks to feedback from Insiders in a Fast, Slow, and Release Preview rings, this bug was held before rollout began.
Which is rather remarkable, since “Windows Insider” beta testers have had 17133.1 for dual weeks — Fast ring got it on Mar 27, Slow ring on Mar 30, and Preview ring on Apr 10. Hard to know how it could take dual weeks to learn a bad bug.
Bowden goes on to tweet:
Not certain if bug was bound in 17133.73 or if it’ll come in another patch. RS4 will expected start rollout in a integrate weeks now.
Microsoft, of course, is mum.
My theory — and it’s usually a theory — is that Microsoft found some dispute with this month’s Patch Tuesday stand that blew dual weeks of Fast ring contrast out of a water.
Got a improved guess? Join us on a AskWoody Lounge.
Don’t forget to block a forced upgrade to Win10 chronicle 1803, when and/or if it’s released.