Windows 10 October 2018 Update rollout now paused

Cliff S said:

Here is a wallpaper I mader for this occasion.
It's called"Windows 10 October 2018 Update Black Screen of Death Metal"(BSODM for short)

Only true metal heads will be able to read it though
Attachment 207433

krzemien said:

So how about MS releasing 1903 (or whatever) being a cumulative fix update fixing all bugs seen to date - rather than concentrating on adding nonsensical and frankly speaking pointless features that most customers do not care about?

It's a good idea but will never happen.

CountMike said:

Why wouldn't one fix work for all ? Unless of course they shmuck something else up ??

I guess that all depends on what was added and or removed from build to build? Stuff is depreciated and stuff is added. I'm not entirely sure one patch fits all (builds) in this case? I don't really know and I doubt Microsoft will tell you.
IMHO, the stop messing with it date, and the release it to the public dates are too close together. Or so it seems to me anyway.

kado897 said:

Unfortunately there is no such thing as bug free code. Systems are just too complex for that.

Alright, that might have come out a bit wrong. As a software developer myself, I know there exist no such thing as completely bug-free code.

What I meant to say is that known issues should be resolved before release.

slicendice said:

Alright, that might have come out a bit wrong. As a software developer myself, I know there exist no such thing as completely bug-free code.

What I meant to say is that known issues should be resolved before release.

I can agree with that.

alphanumeric said:

I guess that all depends on what was added and or removed from build to build? Stuff is depreciated and stuff is added. I'm not entirely sure one patch fits all (builds) in this case? I don't really know and I doubt Microsoft will tell you.
IMHO, the stop messing with it date, and the release it to the public dates are too close together. Or so it seems to me anyway.

Well, I figured that there is definite path any changes should go thru, Skippy>Fast>Slow>RTM (Pre-realese) and only then to unsuspecting public. Enough steps to filter thru.

kado897 said:

I can agree with that.

Great! And I'm 100% certain there are more known issues than MS let's us know. I'm talking from experience based on old releases.

CountMike said:

Well, I figured that there is definite path any changes should go thru, Skippy>Fast>Slow>RTM (Pre-realese) and only then to unsuspecting public. Enough steps to filter thru.

There are also Canary builds that feed into the Fast Ring.

slicendice said:

Alright, that might have come out a bit wrong. As a software developer myself, I know there exist no such thing as completely bug-free code.

What I meant to say is that known issues should be resolved before release.

Indeed they should but what I don't get is why this only effects some users and not others. Look at my specs , I have a quite old system and without any problems.