Bowden: Windows 10 1803 no longer in RTM status, as beta builds resume

Topic

New Reply

We’re all stamping our feet, waiting for Microsoft to finally release the next version of Windows 10. Now, it seems, we’re in for more waiting. Zac Bo
[See the full post at: Bowden: Windows 10 1803 no longer in RTM status, as beta builds resume]

3 users thanked author for this post.

columbia2011, djbaxter, Mr. Natural

Reply | Quote

Replies

Zac Bowden said. “the company is now compiling new Redstone 4 builds once again in an attempt find a new build that passes the necessary criteria for public release.”

In order to expedite the public release in accordance with Microsoft Standards the appropriate solution is to change the criteria.

Reply | Quote

“passes the necessary criteria for public release” Wowee, considering what Microsoft has been pushing out lately that must have been a new low. It’s getting to be like PC gaming where developers evaluate at what point they can push a game out the door knowing there are issues and release patches later down the road. To scrap a release entirely right before they were going to push it out the door certainly doesn’t bolster my current confidence level with  Microsoft.

Red Ruffnsore

3 users thanked author for this post.

Great Lake Bunyip, HiFlyer, geekdom

Reply | Quote

We’re all stamping our feet, waiting for Microsoft to finally release the next version of Windows 10.

Um, no, not all.

I vote for Microsoft to get it right – very right – before making everyone go through the pain of an OS install.

Thank you, folks at Microsoft, who are digging in and making sure it passes the necessary criteria for public release.

-Noel

10 users thanked author for this post.

Great Lake Bunyip, dononline, Bill C., flackcatcher, HiFlyer, BobbyB, zero2dash, mcbsys, woody, Seattle27

Reply | Quote

Which is completely NOT like them. (And that’s a GOOD thing, for once.)
Maybe the bad PR pile is finally big enough to illicit change? We can dream at least.

2 users thanked author for this post.

flackcatcher, HiFlyer

Reply | Quote

… an attempt to find a new build that passes the necessary criteria for public release.

Okay… first off… “an attempt” is a poor choice of words. Sounds like a try & error and not really reassuring, is it?

I would have phrased it like…

the company is now compiling a new Redstone 4 build that passes the necessary criteria for public release.

But it’s still totally meaningsless without a definition of “necessary criteria”…. criteria for whom?

Somehow I doubt, they mean “a rock-solid and thoroughly tested build”….?

4 users thanked author for this post.

Noel Carboni, flackcatcher, Cybertooth, HiFlyer

Reply | Quote

“…an attempt to find a new build…”

Reminds me of that old story about an infinite number of monkeys with an infinite number of typewriters sooner or later writing all the great works.

OK, some may have to look up what a “typewriter” is.

-Noel

Reply | Quote

I just had an epiphany. Didn’t all this nonsense with Microsoft really take a nose dive around the time the state of Washington legalized marijuana? That explains it! (Did you test the code? UH what? No man, I thought you did!) D’OH!

Red Ruffnsore

4 users thanked author for this post.

Karlston, BobbyB, Cybertooth, HiFlyer

Reply | Quote

Ver 1511 bitlocker bug deja vu

1 user thanked author for this post.

HiFlyer

Reply | Quote

Apologies for the simple question, but I would like to be sure… for the foreseeable future, is it okay to take down the measures for blocking 1803/Spring Creators Update? Since they seem to be doing an overhaul of the update and still have yet to announce a release date…

Reply | Quote

No foot-stamping from this lad. That’s right, I’m in no hurry for 1803. Microsoft can take as long as needed to fix this.

We’re all pretty savvy here, and most folks complain when buggy updates are released. In this case, we should be rejoicing that they’ve aborted the launch. Considering the buggy mess over the last several months, this blocking bug must have been REALLY bad for even Microsoft to pause the roll-out.

Better the bugs you know, than the bugs you don’t.

Reply | Quote

Yikes. And I sat for a day to get the (no longer) RTM build. It installed fine through Windows Update (I usually use either the Media Creation Tool or the Windows 10 Upgrade Tool) and I haven’t noticed that bug. My best guess as to what could be (based on the pretty shallow dive I did to build 17133) are possibly kernel side. There’s a new entry in Windows Defender, which covers protections for the device (Secure Boot, TPM, etc.). In there, there’s an option to isolate the kernel (could it be the protection against Spectre/Meltdown or Hypervisor-based Code Integrity?). Maybe it could be something else in the kernel…

3 users thanked author for this post.

Great Lake Bunyip, flackcatcher, columbia2011

Reply | Quote

If it’s still half baked then give it back to the beta testers. I am in no hurry for it.

Reply | Quote

That’s strange, given how they usually just send out half-baked patches and then scramble frantically during the month to patch their patches. I wish I could say that Microsoft is transitioning to better business practices with this… but I highly doubt it.

Reply | Quote

Not stamping my feet for sure. In fact, I am tired of the chaos Microsoft made of Windows 10. This delay was totally expectable, twice a year upgrading (ie a complete reinstall over an existing version of Windows) is just too much. Happens to no other existing os, with reason. All in all, I wouldn’t bet my business on 10. Too risky, you never know what kind of idiotry they cook up in Redmont. 7 was the last reliable version of Windows, after that it became an unprofessional experment.

Reply | Quote

v17134 released

https://blogs.windows.com/windowsexperience/2018/04/16/announcing-windows-10-insider-preview-build-17134-for-fast/

1 user thanked author for this post.

woody

Reply | Quote