Microsoft unexpectedly declares Win10 1809 ready for business

[woody]

This with a list of acknowledged bugs almost as long as my arm. Article coming in Computerworld. Yeah, I think somebody read Susan’s Hey 1809, we need
[See the full post at: Microsoft unexpectedly declares Win10 1809 ready for business]

4 users thanked author for this post.

abbodi86, GreatAndPowerfulTech, PhotM, Lars220

[PhotM]

You don’t say….. Susan, can have an impact????  Get out :)))

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

[anonymous]

Are they really trying to move most of the intelligent users away from Windows? Is this to concentrate only on the big bucks enterprises?

[b]

woody wrote:

This with a list of acknowledged bugs almost as long as my arm.

Do you have really short arms? Five or six obscure issues?

Anything outstanding that affects most people?

1 user thanked author for this post.

Barry

[woody]

I have extraordinarily short arms. 🙂

The point is that most of these bugs were introduced in earlier updates. It’s hard to imagine why MS felt compelled to promote 1809 to CBB when the fixes for most of those bugs must be in the can by now.

Why not wait until the second cumulative update for March?

1 user thanked author for this post.

Great Lake Bunyip

[warrenrumak]

Most of the bugs you mentioned are also in 1607, 1709 and 1803.  Upgrading to 1809 will neither introduce nor fix those bugs.

 

2 users thanked author for this post.

woody, b

[Noel Carboni]

b wrote:

Anything outstanding that affects most people?

Since the beginning of the year I have been personally using Windows 10 v1809 every day on a powerful Dell workstation, doing complex and intense engineering work such as software development, automated product testing, graphics work, terabytes of networking… – and I can’t say I’m running across anything that makes it seem “not ready” for use. In the grand scheme I probably use only a small portion of the hundreds of millions of lines of code in Windows, but for my engineering work it’s hanging together just fine.

Is it possible the definition of “operating system” is so different amongst different folks that some see nothing but trouble while others see nothing but acceptable operation?

Is it possible my workstation, sporting error correcting hardware and fast CPU/GPU hardware and tweaked for performance, is running Windows better or more stably than others’ systems?

Don’t get me wrong; the current Windows 10 IS pretty bloated – there are at least twice as many processes running at any given time than are warranted by the results. But it’s not more unstable.

I’m having trouble explaining the gulf between the reasonable results I’m getting and what others are describing as pretty bad as exaggeration or hype alone. What am I missing?

For those of you with trouble, what is actually going wrong? Looking for real experiences here.

-Noel

[lurks about]

Noel, I think what you will find is most users probably experienced minor, if any problems with any W1o release. But the problems that were seen by some where genuine show stoppers of an extremely serious nature. Problems that were often reported to MS but ignored. Also, the complaints are frequency of new problems, their severity with W10 releases, and the fact that often something that was working correctly before does not after. It seems like W10 never really reaches a state were it is really stable and reliable as major new bugs are introduced with great regularity. Also, there appears to be a major difference between W10 enterprise and W1o home/pro for stability. Since most are probably using home/pro they taking the brunt of the situation.

2 users thanked author for this post.

phaolo, Great Lake Bunyip

[Noel Carboni]

No version of any major OS has ever been without bugs, including some show stoppers (hint, I have a MacBook Pro too). It’s the nature of the beast. There have been outright failures and data losses with prior Windows releases going all the way back.

IMO Win 10 may now be being given a bad reputation more because of accumulated bad behavior by Microsoft than actual reliability issues people are experiencing with the software itself.

Performance, however, does indeed suffer from the extreme bloat the OS is delivered with. That alone MAY be a good reason to hold back from updating… Between when I first turned my new workstation on and now I’ve reduced the time I have to wait for a compile and link of a big piece of software by more than 30% just by tweaking the OS – and I think there’s more to be had. People do care whether their computer systems get their work done.

-Noel

[Mr. Natural]

It’s all Susan’s fault!   🙂

I guess you could say at least someone is listening…..

Red Ruffnsore

[Zaphyrus]

This is not ok, not at all, why now when 1903 is about to get released?

I am not an expert, I am a novice at best that barely understand how Windows works, but even I can tell feature update release dates are a burden to Microsoft and us.

Just someone who don't want Windows to mess with its computer.

[anonymous]

It is OK. Keep in mind that many stay one release (or more) behind deliberately and leave others to test the newest release.

[Zaphyrus]

It is not ok, why?  Only people that know the real deal about feature updates know its dangers

however most people aren’t even aware of  what upgrading their OS means  and stay in the current version.

Just someone who don't want Windows to mess with its computer.

3 users thanked author for this post.

AlexEiffel, lanceboil, doriel

[rc primak]

This is not ok, not at all, why now when 1903 is about to get released?

I think you just answered your own question. They want the most recent Feature Update (1809) to be “ready for business” before releasing (RTM) the current Feature Update (1903 or 19H1). The cadence must be respected, at least internally.

-- rc primak

1 user thanked author for this post.

JCCWsusser

[Zaphyrus]

it’s a rethoric question.

Just someone who don't want Windows to mess with its computer.

1 user thanked author for this post.

rc primak

[zero2dash]

I’ve been using it at work for the last several months with no issues.

Not using it at home yet – the deferral period starts now, I assume. Looks like I’ve got 120 more days of 1803…

[b]

I think the other line which changed at Windows 10 update history today may also be slightly significant:

Windows 10, version 1809 rollout status as of March 28, 2019
Available for any user who manually selects “Check for updates” via Windows Update.

I.E. no longer anything there about “phased rollout”.

I think this may mean that (again) only “seekers” will get 1809, from today until phased rollout of 1903.

3 users thanked author for this post.

Great Lake Bunyip, rc primak, woody

[abbodi86]

Yes, 1809 still not broadly available for non seekers

4 users thanked author for this post.

Great Lake Bunyip, rc primak, woody

[radosuaf]

1809 seems to be Windows ME of XXI century :).

MSI H110 PC MATE * Intel Core i5-6402P * 2 x 8 GB Corsair Vengeance LPX DDR4 2133 MHz * Aorus Radeon RX 570 4GB * Samsung 840 EVO 250GB SSD * Western Digital Blue 1TB HDD * Seagate Barracuda 1TB HDD * DVD RW Lite-ON iHAS 124 * Creative X-Fi XtremeGamer PCI * Windows 10 Pro 2004 64-bit

1 user thanked author for this post.

Cybertooth

[JCCWsusser]

abbodi86 wrote:

Yes, 1809 still not broadly available for non seekers

If I’m reading the tea leaves correctly, this will happen Tuesday April 2.

1 user thanked author for this post.

rc primak

[EP]

Mary Jo Foley of ZDNet has a similar story on this:
https://www.zdnet.com/article/microsoft-officially-designates-windows-10-1809-as-ready-for-broad-deployment/

1 user thanked author for this post.

woody

[woody]

It’s a good article. (As usual.)

The one thing both of us missed is the importance of this:

We will continue to communicate for future releases the transition from targeted to broad deployment status.

John is saying that, in the future, we WILL get notification of the transition from SAC-T to SAC, CB to CBB, or whatever new terminology they come up with. In plain English, in the future, Microsoft is going to give the go-ahead when they think a new version has been thoroughly tested.

That’s important, IMHO. And good news.

3 users thanked author for this post.

Elly, rc primak, radosuaf

[AlexEiffel]

Yes, that catched my attention, and the fact that it implies they will continue to announce the SAC moment, but there won’t be anything technical behind that supports it.

Personally, I don’t care to not have a deferral setting based on SAC designation anymore, since I will use more delay anyway and based on Microsoft’s past performance regarding the moment to announce a version is SAC, I don’t think we loose much.

I understand it helps people have a general idea when Microsoft think the job they have done is good enough for business. But to me, SAC designation is a minimum date, at best. I still had someone call me with a non working home computer after the forced update last week.

1 user thanked author for this post.

rc primak

[anonymous]

Microsoft became a joke in matter of reliability, bu hey: it’s not my reputation… 😀

[anonymous]

If Microsoft wants to take its jolly time with its upgrades, then they’re absolutely fine by my book to do so. Get things right and ship a polished product…

Unfortunately, looks like they didn’t after seeing Susan’s post. Ugh. Here we go again, the update cadence and the bass drum ringing in my ears.

[anonymous]

In fairness, the Windows Deployment Services bug doesn’t only affect 1809 (Server 2019). It goes right back to 2012 R2, maybe earlier.

[John]

Don’t know the exact figures but I think a lot of Win 10 devices have yet to install 1809 for whatever reason. I can’t say that I have any issues myself, so for me the focus is on the 1903 feature update coming. Not surprising that 1809 is still a mess and for Microsoft to certify it finally for business is more a formality then confidence its finally smoothed out the rough edges. Sort of like, OK 1903 is around the corner, we’d better put a fork in 1809 and call it good.

2 users thanked author for this post.

rc primak, JCCWsusser

[woody]

A lot of 1803 machines have not installed 1809 simply because Microsoft hasn’t pushed 1809 on them.

The vast, vast majority of Win10 users (not attached to domains) don’t know and don’t care to know about all of this folderoll. The admins running domains know about it, but are just as twice-burned and twice-shy as the rest of us.

1 user thanked author for this post.

Great Lake Bunyip

[agoldhammer]

I was forced into Windows 10 when Adobe quite supporting Lightroom running under Win 8.1  This was in early January and I installed Ver 1809 directly from the MSFT download site.  Installation was a breeze and I’ve not seen any issues with applications that I routinely use.  I was pleasantly surprised by how little disk space the Win 10 application takes and so far it has been rock stable.  I’m running the Pro version with updates delayed.

1 user thanked author for this post.

Noel Carboni

[Noel Carboni]

Good to hear I’m not alone in finding it to “just work”.

-Noel

[JCCWsusser]

woody wrote:

We will continue to communicate for future releases the transition from targeted to broad deployment status.

John is saying that, in the future, we WILL get notification of the transition from SAC-T to SAC, CB to CBB, or whatever new terminology they come up with. In plain English, in the future, Microsoft is going to give the go-ahead when they think a new version has been thoroughly tested.

That was one of the things I put into the recent survey. I must not have been the only one.

2 users thanked author for this post.

warrenrumak, woody

[Mr. Natural]

And lo and behold, this morning I see 1809 v.2019-03B available for offering in WSUS.

Red Ruffnsore

2 users thanked author for this post.

Great Lake Bunyip, woody

[AlexEiffel]

I am not sure if we should rejoice if indeed, Susan was listened to in the sense that it maybe made Microsoft declare 1809 SAC although it is maybe not ready if you feel more like Woody about it.

The thing is, Microsoft should declare a version business ready when it is and if it takes time, we should not pressure them into doing so too early and then complain it isn’t business ready after they do. I understand that was not Susan’s point because Microsoft previously said they would not announce it anymore.

So we can rejoice that maybe Susan got an ear and now Microsoft will continue to announce when a version is business ready, but I’m not sure if we should be happy or not that Microsoft declared 1809 ready when Woody said it might still not be for whatever reason that might be acceptable or not (pressure because the new version is around the corner, because people expects Microsoft to improve on their delay to announce it so they don’t think the WaaS model is getting worse…).

I also wonder if indeed, someone at Microsoft got aware of Susan’s wish, it is a nice side-effect of swallowing the Windows Secrets crowd.

And I will end by asking again, why Microsoft thinks that twice a year for feature updates is a great idea. It seems to me it only puts too much pressure on them on many fronts. What is the benefit for them? And who really needs those new features that badly? If they only released once a year and supported their versions 30 months for everyone, things would be much easier for everybody.

5 users thanked author for this post.

Great Lake Bunyip, Noel Carboni, abbodi86, woody, JCCWsusser

[Noel Carboni]

Back a while I predicted that by causing everyone to live with 6 month constant feature update madness for a while, extending that to a year would feel like a breath of fresh air.

I don’t think a year is long enough. 2 might be acceptable, but hey, I have an idea: How about a feature update every 3 years, and support for 10?

-Noel

3 users thanked author for this post.

AlexEiffel, JCCWsusser, lurks about

[JCCWsusser]

Noel Carboni wrote:

I don’t think a year is long enough. 2 might be acceptable, but hey, I have an idea: How about a feature update every 3 years, and support for 10?

What a great idea! I’m surprised they’ve never thought of it before. 🙂

2 users thanked author for this post.

AlexEiffel, woody

[anonymous]

I’m still on 1803. I have not checked updates for months due to 1809 being secretly hidden in there if I “check for updates” and sometimes in WUShowhide I see 14307 something that one that hides that little trick into upgrading the update assistant nad forcing 1809 or so on ya.

My computer’s been safe from 1809 for months now. I am gonna wait and see how 1903 varies and if that’ll be safe to install once there’s the “greenlit” that it’s safe, secure and won’t harm my laptop or OS or anything.

 

[EP]

newly refreshed 1809 ISOs available from the Microsoft Windows 10 downloads page:

Win10_1809Oct_v2_English_x64.iso (for 64bit)
Win10_1809Oct_v2_English_x32.iso (for 32bit)

these contain build 17763.379

2 users thanked author for this post.

Great Lake Bunyip, woody

[woody]

Those are the latest, released last Patch Tuesday.

1 user thanked author for this post.

Great Lake Bunyip

[Author]

Posts