Windows 10 version 1803 held up because of BSOD

[Jito463]

https://www.theregister.co.uk/2018/04/17/waiting_for_windows_10/

 

It seems that the release-halting bug in the latest Windows 10 update (commonly referred to as the Spring Creators Update) has a high chance of causing BSOD's.

Quote

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 brave soldiers on the Fast ring.

 

"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) on PCs for example," said Sarkar in the post.

Apparently there was some speculation about KB 4100375, but that doesn't seem to be the cause.

Quote

The team at Microsoft has elected to add the fixes in KB4100375 to build 17134.  This includes a patch for PDF security in Edge and the inevitable raft of miscellaneous security updates for the rest of the OS.

 

KB4100375 had been included in the last update for build 17133, indicating that whatever was the cause of the problem lay elsewhere.

Personally, I'm going to be waiting a few weeks (or more) before upgrading to this new build once it's released.  Just in case their crack team of amateur bug-hunters don't catch it, since MS can't be bothered to have a real QA team.

[Tabs]

I can see it now on BBC news at 10 - Newsflash: Bug reporting program finds bug, delays mass release of software.

 

I'm far happier that they are being conservative with the release because they thought it might cause BSOD problems than if they had just gone ahead with it regardless. This is literally the point of the insider preview program.

[Arika]

Windows 10 update released due to bug that causes BSODs. in other news water is wet. more at 11

 

 

[Jito463]

2 minutes ago, Sierra Fox said:

in other news water is wet

Technically, water isn't wet, it just makes any interacting object wet.

[captain_to_fire]

Since Microsoft plans to name it as "Spring Creators Update", are they going to name it "Fall Creators Update" once again if they fail to iron out BSOD-causing bugs in time and release it on September instead?

[Canada EH]

More problems with Windows 10, what is Bill doing?

[Itanium]

I actually tried using the update early about a week ago and it had some mysterious bug where DirectX games such as Radical Heights (and League of Legends, but only for a few seconds) would stay permanently stuck on a black screen and not allow you to CAD/Force Quit at all. Hopefully they're fixing that as well. 

[ScratchCat]

3 hours ago, Jito463 said:

Technically, water isn't wet, it just makes any interacting object wet.

• If a surface is covered by pure ethanol it would be wet.
• If a surface is covered by water it would be wet.
• If a surface is covered by non dry paint, it would be wet.
• If a surface is covered by fresh ink it would be wet.

Hence an object covered by a liquid could be described as wet. From this we can predict that a volume of water 'covered' by more water is wet. Hence water is wet.

 

At least they did not roll out another major update with a bunch of bugs. It is worrying that smaller companies such as Canonical, the makers of Ubuntu, and Mozilla can manage high frequency release schedules while Microsoft, a much larger company, cannot.

[laminutederire]

They halt a release because of a found bug -> screw MS for their lack of QC? Someone explain me this I don't understand that implication at all!

[Kherm]

4 hours ago, captain_to_fire said:

Since Microsoft plans to name it as "Spring Creators Update", are they going to name it "Fall Creators Update" once again if they fail to iron out BSOD-causing bugs in time and release it on September instead?

It's not called the Spring Creators Update, they actually, for some reason, have not publicly disclosed the name of the update. SCU was found on internal documents but they were outdated, it's believed it'll be called 1803 now

[Princess Luna]

It'd be nice if Microsoft just slowed down on these updates and focused on simply improving what's there already.

[TopHatProductions115]

@Princess Cadence But, that wouldn't fit with the new Windows-as-a-Service model that Microsoft is pushing us into  

[Princess Luna]

3 minutes ago, TopHatProductions115 said:

@Princess Cadence But, that wouldn't fit with the new Windows-as-a-Service model that Microsoft is pushing us into  

It still does, they just don't have to compete with Apple to see who updates OS's more frequently

[Xander Cousins]

1 minute ago, Princess Cadence said:

It still does, they just don't have to compete with Apple to see who updates OS's more frequently

Next we will hear Microsoft bricking Ram because why not

[TopHatProductions115]

@Alex Colson Nah - they'll brick SSDs and PSUs first - 4DaLolz  

[Xander Cousins]

@TopHatProductions115 'why does my SSD's and overly priced PSU's not work?' 

 

uhhh we bricked it because we can?

[Master Disaster]

5 hours ago, Canada EH said:

More problems with Windows 10, what is Bill doing?

Trying to solve world hunger and enjoying his billions.

[AlTech]

@Jito463 Your title is incorrect and misleading. Please fix it.

 

Either "Version 1803" or "Build 17133" would be fine.

[Kukielka]

10 minutes ago, AluminiumTech said:

@Jito463 Your title is incorrect and misleading. Please fix it.

 

Either "Version 1803" or "Build 17133" would be fine.

LOL @AluminiumTech complaining about incorrect and missleading titles, that's fkin hilarious.

 

But seriously, why are there like 4 Topics on a bug in a windows 10 update, that did not affect ANYONE at all?

[NelizMastr]

FYI there's already a new build in the RC channel that supposedly fixed the bug, so expect the rollout to still start later this month.

[Jito463]

2 hours ago, laminutederire said:

They halt a release because of a found bug -> screw MS for their lack of QC? Someone explain me this I don't understand that implication at all!

I don't think anyone is upset because they delayed release.  My issue is that they're too reliant on end-users testing their product, rather than testing it more thoroughly themselves.

[Misanthrope]

"A higher percentage of (BSOD)"

 

The underlying message here is that Microsoft considers there is a percentage for them that's actually acceptable in the case of automatic updates.

[laminutederire]

Just now, Jito463 said:

I don't think anyone is upset because they delayed release.  My issue is that they're too reliant on end-users testing their product, rather than testing it more thoroughly themselves.

I think the inherent issue of Windows versus mac is that simply there is no way you'll test your OS on every hardware possible. So you kinda have to go the Linux way and push betas to hunt for bugs. Issue then is that I suspect there are some legacy badly written part of the OS still remaining in Windows that forces them to workaround those (instead of just deleting them). That pruning job should alleviate more hardware specific bugs, as the clearest and most coherent it is, the easier you'll find reproducible bugs.

[laminutederire]

Just now, Misanthrope said:

"A higher percentage of (BSOD)"

 

The underlying message here is that Microsoft considers there is a percentage for them that's actually acceptable in the case of automatic updates.

I think they meant after the update

[Misanthrope]

1 minute ago, laminutederire said:

I think they meant after the update

So did I: if it's not an opt-in update or a security update, if it's just incremental features 0% should be the only acceptable percent: we're paying customers, not fucking guinea pigs.