Windows 10 version 1903 declared “ready for broad deployment”

Topic

New Reply

Yes, you read that right. In spite of the horribly fumbled CVE-2019-1367 IE patch. In spite of the known bugs. Microsoft is recommending that business
[See the full post at: Windows 10 version 1903 declared “ready for broad deployment”]

6 users thanked author for this post.

Fred, Great Lake Bunyip, Chris B, Microfix, abbodi86

Reply | Quote

Replies

Well, I say: good luck with this one!

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903#634msgdesc

Reply | Quote

Didn’t it got declared previously (when they started pushing it to 1803)?

2 users thanked author for this post.

Fred, Microfix

Reply | Quote

Not as far as I know. The update is dated yesterday – and it was tweeted about six hours ago.

https://twitter.com/WindowsUpdate/status/1177458748563968001

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

MSFT is obviously pushed for time with the release of W10 v1909 (october update?) imminent, suppose they have to declare it fit (whether it is or not). This doesn’t bode well for the next feature update/service pack initial release. It certainly doesn’t relay confidence for me and probably other end-users..

Windows - commercial by definition and now function...

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

Not like Microsoft sets the bar that high anymore. If you don’t get a blue screen it’s ready for prime time !

2 users thanked author for this post.

Great Lake Bunyip, lanceboil

Reply | Quote

It would be very helpful if someone could post, or point a link to, the latest advice on how to control updates in 1903. The normal controls of deferring quality updates by 2x days and deferring feature updates by 2xx days have disappeared in 1903, favour a simple “Pause by up to 35 days” and PKCano separately advised it will not come back. I am unsure how best to control the updates to follow Woody’s Defcon advice.

Many thanks

Chris
Win 10 Pro x64 Group A

Reply | Quote

[woody]

The current advice is here:

https://www.computerworld.com/article/3437019/tomorrows-patch-tuesday-time-to-block-windows-automatic-update.html

Next advice will come when I figure out what in the %$#@! the settings to do control 1909.

• This reply was modified 5 years, 8 months ago by woody.

3 users thanked author for this post.

Fred, Great Lake Bunyip, Chris B

Reply | Quote

1903 has been stable for me. Quality deferrals set to 14 days…no issues.

Reply | Quote

I agree with Microfix, above. The only reason that Microsoft is declaring version 1903 ready for broad deployment is because the 1903 “Fall upgrade” is about to be released; and if they don’t make this declaration now, it might have to wait months longer to see what happens with the release of the “Fall upgrade” and its yet to be determined problems. For myself, a non-gamer, personal home user, no servers or networks other than my home wi-fi router, however, Version 1903 has been the most stable and easiest to update version of Windows 10 so far on my HP Omen 15.2 inch laptop with a 7th generation Intel Core i7 7700 HQ processor and 8 Gb of ram and an 128 Gb SanDisk SSD with 1 Tb fixed hard disk data drive and NVidea graphics card. The few event errors and warnings that I still deal with seem to all be associated with me having a no-password administrator log-on straight to the desktop and repeated audit failures whenever launching any browser, even Edge. Nuisance events, in other words.

 

Reply | Quote

[bbearren]

I’ve been running 1903 without issue since its release, keeping it fully updated with whatever Windows Update has to offer, with the exception of using group policy to block driver updates, and I’ve not had any issues.  Today I got Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4517211).

If Windows 10 is installed on 500,000,000 PC’s and 1,000,000 users are having problems, that only amounts to 0.2%.  What percentage of users having problems would it take for Microsoft to re-think their business model?

If a success rate of 98% is acceptable, that means (assuming 500 million Windows 10 PC’s) that 10,000,000 Windows 10 users with problems still falls within that 98% acceptable rate.  If the actual number of Windows 10 PC’s is higher than 500 million, I still have to think that Microsoft is going to follow their business model as long as the success rate meets their criteria.

Zero Defects is simply not achievable in any very large, diverse user base, which means that there is quite likely an acceptable rate of failure stipulated as a target.  I don’t know that its 98%, but I’m reasonably certain that it’s not 100%.

As soon as 1909 is available, I’ll upgrade to it on the A side of my dual boot, and see if my re-configured installation on the B side will reject it.  I got Cumulative Updates KB4515384 and KB4517211 on the B side today.  I’ll keep y’all posted.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

• This reply was modified 5 years, 8 months ago by bbearren.

2 users thanked author for this post.

b, Barry

Reply | Quote

[EP]

for me I’ve already upgraded some machines to 1909 using the “leaked” ESD downloads for 1909 (which were recently posted on MS’s servers). I had v1909 build 18363.356 and used the KB4517211 update from the Catalog to update that to build 18363.387.

• This reply was modified 5 years, 8 months ago by EP.

Reply | Quote

It’s officially released via WSUS, nothing leaked 🙂

1 user thanked author for this post.

woody

Reply | Quote

[Barry]

Thank you bbearren. I have been wondering how to respond to Woodys obviously over the top comment and i think you put it perfectly.

 

Barry
Windows 11 v23H2

• This reply was modified 5 years, 8 months ago by Barry.

1 user thanked author for this post.

b

Reply | Quote

Not sure which comment is over the top. 🙂

1 user thanked author for this post.

Fred

Reply | Quote

“Hard to tell if it’s a declaration of stability,”
……….
“This announcement has nothing to do with 1903’s stability,”

Reply | Quote

All I know is that since Windows 10 released, I’ve had far fewer issues with mainstream Linux distributions like Debian and Ubuntu, and many more issues with Windows. I do think that each new release of Windows 10 is an improvement, but Microsoft could sure be doing a lot better. The issues are more likely to be annoyances or performance regressions than show-stoppers, and most users are simply able to put up with them, or don’t use their computer in a complicated enough way to trigger the breakages.

Reply | Quote

woody wrote:

Not sure which comment is over the top. 🙂

Nevertheless : QED for post 1966797

* _ ... _ *

Reply | Quote

Which post is that Fred?

cheers, Paul

1 user thanked author for this post.

Fred

Reply | Quote

https://www.askwoody.com/forums/topic/the-inside-story-on-win10-rollouts-the-machine-learning-engine-that-throttles/#post-1966797

The searchengine in the right bar doesn’t work,

Greetings, fred

* _ ... _ *

Reply | Quote

Fred wrote:

The searchengine in the right bar doesn’t work

That would depend on what/how you are searching…

Reply | Quote

1966797

the post Paul T  naar vroeg

* _ ... _ *

Reply | Quote

There is no facility to search for Lounge content by post # – it’s just not part of the infrastructure. Searching by content is the way to go 🙂

Reply | Quote

At a home office, multiple machines using Win10 1803.   We moved to 1803 after it had stabilized for six months, and it’s been a reasonably stable choice.  We expect to move up to a new version in this coming December when 1803 support ends.  The current Windows release environment does not look good for selecting a newer supported version.  1809 is ruled out.  1903 seems very troubled, with significant new issues each month (eg such as HP network printer problems which would affect us).   And because  1909 is characterized as a service pack to 1903, this ‘last hope’ of 1909 being a solid new version to roll out seems very wobbly, since it will not have sufficient time to stabilize by December.  We did not expect this level of monthly effort reviewing and selecting updates when we decided to move from 8.1 to 10.

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

Why is 1809 ruled out? It had a lot of troubles when it was released, but seems to be quite stable nowadays. It would only give you a few months extension though.

Reply | Quote

[EP]

the 1809 release became much more stable when MS declared that one “business ready” or “ready for broad deployment” around the end of March 2019. MS released “1809 V2” ISOs & ESDs with build 17763.379 (KB4489899) and that version was solid unlike the “original” 1809 release with build 17763.1 back in early October 2018 which had the user file deletion problem.

• This reply was modified 5 years, 8 months ago by EP.

1 user thanked author for this post.

abbodi86

Reply | Quote

“Even for those of us who regularly attend IT-focused conferences and keep up with deployment news, managing a Windows-based organization in this new era can be confusing. For those who are simply using Windows for day-to-day-business, the changes can appear unexpectedly. And the realization that tried-and-true workflows no longer apply isn’t sitting well with some IT pros.” – Ed Bott.

That was 2017.

Microsoft states that 89% of enterprise clients and 47% of small and medium size business are now in full production on W10.

That statement by Ed Bott applied to large, medium and small businesses. However, small and medium size businesses do not have an IT department to discus and manage a mandatory deployment, so they specifically rely on ‘READY’ to mean ‘TOTALLY STABLE’. The larger issue though is that this deployment is in the last quarter of the year – no business wants to have to deal with any instability at year end. With known and unknown issues still outstanding, this has the potential to go beyond confusion to disillusionment.

Reply | Quote

Can unknown issues be outstanding? Ready means guaranteed problem-free?

Reply | Quote

The way I see it, if it ain’t broke why fix it. I’m currently happy with 1803. Two out of my three laptops have had at least one issue with a feature update, some of those where rather benign and others were a pain. When 1803 is no longer supported, then and only then will I have a need to update to 1903.

IGS

Reply | Quote

for me I will still use 1803 even beyond the November 2018 support cut off date since I’m using a higher edition of Win10 1803 like 1803 education, which gets support until November 2019.

Reply | Quote

Add 1 to both of your years?

Reply | Quote

2018? I believe you meant November 2019 which is when support for 1803 may end.

IGS

Reply | Quote

sorry my mistake – I meant to say “November 2020” for 1803 education end of support – I no longer can edit that previous post since I was unable to change it in time

meantime after the 1903 V2 ISOs came out in early October, there’s this recent Tweet by Zac Bowden that 1909/19H2 GA (public release) may happen either in late October 2019 or sometime in November 2019

Reply | Quote