Do you need to test cumulative updates?

Topic

New Reply

I just stumbled across this video made by Microsoft back in November, that discusses how Microsoft rolls out cumulative updates internally. It’s… st
[See the full post at: Do you need to test cumulative updates?]

9 users thanked author for this post.

WildChild, AlexEiffel, abbodi86, Charlie, GreatAndPowerfulTech, Kirsty, Mr. Austin, geekdom

Reply | Quote

Replies

[_Reassigned Account]

Well no surprise to most of us. Personally I think after Balmer left the focus turned past Windows to cloud systems and has never revisited that decision.

• This reply was modified 3 years, 9 months ago by _Reassigned Account.

1 user thanked author for this post.

WildBill

Reply | Quote

[Susan Bradley]

Given that CSS (CSS is what Microsoft calls customer support) is also in the next room, it’s a little easier for them to get support on the line.  I am definitely starting/working on the Askwoody Windows Health dashboard this weekend.

Susan Bradley Patch Lady/Prudent patcher

• This reply was modified 3 years, 9 months ago by Susan Bradley.

6 users thanked author for this post.

WildBill, abbodi86, woody, Kirsty, Mr. Austin, geekdom

Reply | Quote

The only surprise is that they’re admitting to something we’ve all known for years. This is the reason they release the update “preview.” I love that they call it “application compatibility” testing as opposed to “find our s**** ups” testing. “Beta” testing is itself a euphemism, so they’ve eupemized a euphemism (along the way to euthanizing quality control).

GaryK

4 users thanked author for this post.

wavy, Charlie, woody, Mr. Austin

Reply | Quote

“euthanizing quality control” – I love that 😉

1 user thanked author for this post.

gkarasik

Reply | Quote

Not excusing the behavior, but…
This is exactly why they rely on the telemetry data that users are so paranoid to opt out of.
Testing a patch vs a million hardware and software configurations is not something any company can do.

Again, not excusing the behavior, just trying to put some reason and sense behind the practice.

6 users thanked author for this post.

access-mdb, WildBill, Barry, bbearren, Microfix, Mr. Austin

Reply | Quote

And that telemetry data is available only AFTER the damage is done.

Reply | Quote

Agreed, but it should theoretically/hypothetically prevent other users with a similar hardware/software combination from getting nailed with a bad update. (Or so I hope.)

Reply | Quote

zero2dash wrote:

Not excusing the behavior, but…
This is exactly why they rely on the telemetry data that users are so paranoid to opt out of.
Testing a patch vs a million hardware and software configurations is not something any company can do.

Again, not excusing the behavior, just trying to put some reason and sense behind the practice.

This is true if you think quality testing must cover millions of computers and find/fix every conceivable error. But it doesn’t, and no one expects it to do that. People do have a right to expect a reasonable amount of testing on the majority of configurations, and they have a right to expect that an update won’t trash their clients businesses. Not every client has the resources to have sandbox systems. The perfect is the enemy of the good, but the current Microsoft isn’t even producing good.

GaryK

Reply | Quote

woody wrote:

To date, we haven’t seen application compatibility issues with this approach.

That speaks volumes, methinks.

I’m sure we live in a parallel universe.

What was the last application compatibility issue you saw in the real world?

Reply | Quote

Both of the major bugs in this month’s Cumulative Update.

Reply | Quote

Which applications are affected?

Reply | Quote

woody wrote:

Both of the major bugs in this month’s Cumulative Update.

What percentage of the installed base indicates “major” bug?

In my view, a minor bug affects some users, while a major bug affects most users, and by “most” I mean more than 51%.

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

We were all once "Average Users". 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.

Computer Specs

1 user thanked author for this post.

Barry

Reply | Quote

Excellent points, I agree.
I think that’s one of the issues with people reporting an issue with Win10.
You have a billion installs at this point, and mathematically in order to have something truly be “widespread”, you’re talking about millions (or tens of millions) of users. Problem is, the evidence just isn’t there.

I know the jargon is easy to use, but it’s just not correct in this sense.

Reply | Quote

“Major” isn’t the same as “widespread”. A “widespread” bug is one that affects a sizable percentage of the userbase. A “major” bug is a big oopsies that does serious, unwanted, or startling damage. Having an update cause your system to fail to boot into your proper profile is what I’d consider a “major” bug; it’s going to give end-users a panicked heart attack when they see it.

2 users thanked author for this post.

Nibbled To Death By Ducks, David F

Reply | Quote

bbearren wrote:

In my view, a minor bug affects some users, while a major bug affects most users, and by “most” I mean more than 51%.

I would say a major bug is any that has substantial negative impact when it manifests, regardless of how many people are affected.  If a bug wipes out your user folder, it’s a major bug, even if you’re the only one who ever saw it.  A bug can be both major and rare, by this definition.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon (and Win 11)

Reply | Quote

[geekdom]

Regarding this matter, we have reached the age of “It’s your misfortune and none of my own.”

• Backup your files.
• Backup your system.
• Create a restore point.
• Apply update.
• Check afterward to see that files, folders, and software are intact.

We are all beta testers.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

• This reply was modified 3 years, 9 months ago by geekdom.

3 users thanked author for this post.

Lars220, WildBill, GreatAndPowerfulTech

Reply | Quote

This is sad, just sad.

Suppose a non computer nerd, small business user has auto updates enabled, is on the road and about to make a presentation only to discover that his/her laptop applied an update while having breakfast and now the needed presentation application has compatibility isses and crashes.

1 user thanked author for this post.

Bengalensis

Reply | Quote

Pretty amazing that MSFT would not have caught any of the issues with the software updates even if they had tested them.  Boy, that is REAL Quality control, … me thinks not.  I just hope Boeing does not implement MSFT’s strategy to save money. ….or did they:)

Reply | Quote

WildChild wrote:

I just hope Boeing does not implement MSFT’s strategy to save money. ….or did they:)

Boeing doesn’t have to implement Microsoft’s strategy, it’s enough that they use Windows OS and patches.

Reply | Quote

Truly appalling, but then I spent some time in QA/QC working with Defense Contract Administration Service (DCAS) in ancient times, and my standards might be a bit higher…but to me, this is awful.

Well, they might have saved enough money to upgrade the Cricket Court…

https://www.geekwire.com/2017/heres-microsoft-building-cricket-field-middle-redeveloped-campus/

I mean, they have to have their priorities in order, right?

Chin-Chin!

Win7 Pro SP1 64-bit, Dell Latitude E6330, Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Greenhorn
--
"Nine out of 10 doctors say Acid Reflux is mainly caused by computers."

Reply | Quote