New update options for Windows 10, version 1703

FrgMstr

Just Plain Mean
Staff member
Joined
May 18, 1997
Messages
55,532
Is it me, or do you feel more stupid for reading this?

With the release of Windows 10, we simplified the servicing process by moving to cumulative updates, where each update released contains all the new fixes for that month, as well as all the older fixes from previous months. Today, most organizations deploy these cumulative updates when they are released on the second Tuesday of every month, also called “Update Tuesday.” Because these updates contain new security fixes, they are considered “Security Updates” in Windows Server Update Services (WSUS) and System Center Configuration Manager.

Based on feedback from customers, we are making some adjustments to the updates that we are releasing for Windows 10, version 1703 (also known as the “Creators Update”). With these changes, we will routinely offer one (or sometimes more than one) additional update each month. These additional cumulative updates will contain only new non-security updates, so they will be considered “Updates” in WSUS and Configuration Manager.
 
Riddle me this Batman..

What belongs to you, but is used by others?



Your data.. and your ass!!

grab-em.jpg
 
This is weird. If the non security updates are not important, why would I need to rush to install them out of the normal patch Tuesday time period...

I would think the opposite should have been done, where security patches are split out from the normal patch Tuesday so they can be installed quickly.
 
That is pretty confusing...

It looks very similar to what they are doing today... Offering one update with security only and one with all updates.

The image they show basically looks like non-security updates can be just delayed a month. Can't remember what the "security only" updates of today would do if you only deployed them each month (I deploy the full update each month). Maybe the big "difference" is that they are changing the classification? oh for the love of god they need to add a .Net product classification already.

Personally I really like the one patch a month deal, we have had some small issues but nothing to horrible so far, at least not more than the piece-mail method. I think eventually vendors will provide software that is more isolated to avoid most issues with updates. This also forces us to stay current which in the long run is actually better for us.
 
I couldn't finish reading the article because while doing so I reached a point where I became too dumb to read.
I am glad I am not the only one that felt that way.
 
So, this allows for select non-security fixes to be delayed by one month - with those select non-security fixes being installed the next month in the primary cumulative update.

This is a total sham - yet is sadly on par for Microsoft since Satya Nadella took over.
 
So... they're gonna bundle all the updates up into one update that happens on the second Tuesday, henceforth dubbed "Update Tuesday" when you will get your updates herein referred to as "updates"

Unless there is a different update required, that they will release outside of "Update Tuesday" making the updates as needed, these special updates not coming up "Update Tuesday" will be referred to as "updates"
 
This is weird. If the non security updates are not important, why would I need to rush to install them out of the normal patch Tuesday time period...

I would think the opposite should have been done, where security patches are split out from the normal patch Tuesday so they can be installed quickly.

There ya go using common sense! You're never going to understand NadellaSoft with that attitude and elevated level of knowing what should be reasonable *wags finger*
 
Guess everyone that press release has gone trough thought "I must be too dumb to understand, but I'm sure it makes sense" So noone dared to throw it back for revision.
 
Sounds like they are splitting the updates and security updates into two branches of updates, so we can only deploy security updates and choose whether or not to release non-security updates. If that's the case, I think it's a good idea. I currently only push security updates out through WSUS.
 
I'm too dumb to understand their way of thinking, so I just tried to reason the graphic attached. Do I understand correctly that every cumulative update contains every previous update? So what happens in 2 years? Updates the size of 3GB each?
Or maybe they think that users will always install next Windows version that have most of the updates slipstreamed...
What will happen with updates for LTSB version that are supposed to be able to stay on the same version for years?
 
Sounds like they are splitting the updates and security updates into two branches of updates, so we can only deploy security updates and choose whether or not to release non-security updates. If that's the case, I think it's a good idea. I currently only push security updates out through WSUS.

They only split non security updates for the current month, but BOTH of the next month's updates contain ALL the updates from the previous month. So, if you chose not to install non-security updates one month, you're going to have to install them the next month in order to choose to not install the non-security updates for that month.

Effectively, it only allows for a particular month's non-security updates to be delayed by 1 month - but the next month will require them to be installed, while also giving another option to delay just that new month's non-security updates by one month.
 
So they are moving Windows over to the same update model they have been using for Exchange and Sharepoint for the last decade? Got it, I am not overly upset by this.
 
I'm too dumb to understand their way of thinking, so I just tried to reason the graphic attached. Do I understand correctly that every cumulative update contains every previous update? So what happens in 2 years? Updates the size of 3GB each?
Or maybe they think that users will always install next Windows version that have most of the updates slipstreamed...
What will happen with updates for LTSB version that are supposed to be able to stay on the same version for years?

I also am wondering this, but I suppose I will find out in the coming weeks when I go to update the machines around here.
 
Is it just me, or did Microsoft steal that chart from Infographics 101? There is a time and a place to use cumulative charting... this is neither of those.
 
They only split non security updates for the current month, but BOTH of the next month's updates contain ALL the updates from the previous month. So, if you chose not to install non-security updates one month, you're going to have to install them the next month in order to choose to not install the non-security updates for that month.

Effectively, it only allows for a particular month's non-security updates to be delayed by 1 month - but the next month will require them to be installed, while also giving another option to delay just that new month's non-security updates by one month.
Well at least you get some wiggle room to pull the plug if something screws up.
 
When I was at school we laughed about how some of the morons in our classes would one day be running companies.
The reality is sad.

What happened to making a simple task simple?
Updates labelled as critical, security, gui change, ... A decent description saying what it does.
Then let us choose what to install.
There can be pre-requisites to install newer updates, it would be simple to state which previous updates are needed and even automate it with a single click.

But no.
They want to make it annoying, difficult, hard to follow and near impossible to understand.
Not just for us, but I bet the majority of their own employees will struggle in the same way.
They got lost in the Starwars universe somewhere on the dark side...
The more you tighten your grip, the more systems will slip through your fingers.
lol.
 
Updates labelled as critical, security, gui change, ... A decent description saying what it does.
Then let us choose what to install.

That's crazy talk. Your not one of those Linux people are you. :)
 
So they are moving Windows over to the same update model they have been using for Exchange and Sharepoint for the last decade? Got it, I am not overly upset by this.
The difference being that Exchange/Sharepoint won't have the very definition of the word "updates" focus-grouped, recategorized and reimagined to "better align with core longterm engagement values" and "build deeper user connections" where next thing you know..

iQIF2Yz.png


.. the system is downloading useless crap you didn't ask for, after (naively) presuming that "Important updates only" meant important updates only. And after more multi-week focus grouping among Branding & Engagement Tiger Teams, it wouldn't be decided that the Next Update® to Sharepoint/Exchange would make the useless crap that users are ignoring uninstallable, as a way of "resharpening focus to generate increased opportunity across a more effective portfolio and bringing Windows fans engagements they love!".
 
Last edited:
I also am wondering this, but I suppose I will find out in the coming weeks when I go to update the machines around here.

The client downloads and installs only the new parts of the update it needs. Most update methods support this, one of their enterprise deployment solutions SCCM will support this very soon (if not already, can't quite remember very close)

When I was at school we laughed about how some of the morons in our classes would one day be running companies.
The reality is sad.

What happened to making a simple task simple?
Updates labelled as critical, security, gui change, ... A decent description saying what it does.
Then let us choose what to install.
There can be pre-requisites to install newer updates, it would be simple to state which previous updates are needed and even automate it with a single click.

But no.
They want to make it annoying, difficult, hard to follow and near impossible to understand.
Not just for us, but I bet the majority of their own employees will struggle in the same way.
They got lost in the Starwars universe somewhere on the dark side...
The more you tighten your grip, the more systems will slip through your fingers.
lol.

The old select the update method was massive, cumbersome and ultimately lead to update issues since they had something like 50k different patch configurations to test against. People were hanging themselves with all the options and then blaming MS. Vendors pile on the crap as well... "just don't install that patch..." No... you fix your freaking app.

I won't disagree that this article was written poorly but having 2-3 patch options each month is better than 30 imo.

Just like the transition from XP to Vista, vendors will have get their stuff straight as well to ensure their apps are just as agile.

Now that I think about this more, I like this idea.. You now have the option to roll back a patch and deploy only the security version if you run into app compatibility issues.
 
The client downloads and installs only the new parts of the update it needs. Most update methods support this, one of their enterprise deployment solutions SCCM will support this very soon (if not already, can't quite remember very close)



The old select the update method was massive, cumbersome and ultimately lead to update issues since they had something like 50k different patch configurations to test against. People were hanging themselves with all the options and then blaming MS. Vendors pile on the crap as well... "just don't install that patch..." No... you fix your freaking app.

I won't disagree that this article was written poorly but having 2-3 patch options each month is better than 30 imo.

Just like the transition from XP to Vista, vendors will have get their stuff straight as well to ensure their apps are just as agile.

Now that I think about this more, I like this idea.. You now have the option to roll back a patch and deploy only the security version if you run into app compatibility issues.

I extended the old select update method to remove the huge number of configurations.
A simple change will fix it and make it very easy to use.
 
Windows fucking 10, lol. :yuck:

I rolled back to Win7 last week for the last time having tried that idiotic creators update.

holy_svchost_win10_batman.png


Compared to what I have now...

much_better.png


I read the rationale, but at the end of the day this change uses up more ram/resources and ultimately only benefits Microsoft developers.

Mass Effect Andromeda just came out, and it's Directx 11. I've no actual reason to use this piece of shit OS. The only fools enjoying Windows 10 are AMD bitches desperate for irrelevant Directx12 benchmarks. :hilarious:
 
Last edited:
Mass Effect Andromeda just came out, and it's Directx 11. I've no actual reason to use this piece of shit OS. The only fools enjoying Windows 10 are AMD bitches desperate for irrelevant Directx12 benchmarks. :hilarious:

LOL! 10 has been great for gaming on my sig rig.
 
Windows fucking 10, lol. :yuck:

I rolled back to Win7 last week for the last time having tried that idiotic creators update.
I read the rationale, but at the end of the day this change uses up more ram/resources and ultimately only benefits Microsoft developers.

Mass Effect Andromeda just came out, and it's Directx 11. I've no actual reason to use this piece of shit OS. The only fools enjoying Windows 10 are AMD bitches desperate for irrelevant Directx12 benchmarks. :hilarious:
LOL!
You mean you don't miss all of the non-existent DirectX12 and Game Mode benefits.
What are you, a commie.
 
One thing that I'm not okay with in Windows 10 is that I can't choose what updates get applied without a more expensive edition or wsus. With the shit they rolled into win 7 and 8 in back porting, that's a problem.
 
I extended the old select update method to remove the huge number of configurations.
A simple change will fix it and make it very easy to use.

Adding "dependencies" while certainly would help organize the mess that was/is supersedence and provide more understanding. What you would end up with is exactly what they are doing now... in order to install this update you have to install last months update.

Again, I agree they are not explaining a simple thing well.. Right now is the simplest update method they have ever done. Install Win10 May updates, either Full or Security, done simple. The next month install June updates, either Full or Security... done.

The problem I saw before was companies (both end user and vendor) would rely heavily on the ability to not deploy a patch, most would not quickly fix said issue. Usually the fire would get IT racing around to figure out what the issue was, once found and removed... a mention "we should" to fix the root cause would occur and then focus and resources would shift back to the fire of the day forgetting to follow up on root cause.

Fixing a security or patch compatibility issue is low priority in most places I have worked vs ongoing efforts that improve actual business functions/sales etc. Sad but its true, I have found.

I am finding it nice that can we tell our customers this is the way it works, you HAVE to fix your issue soon or you will be in a worse position with 0 updates. They then are more willing to put pressure on THEIR software vendors, before they wouldn't do this if all you had to do was exclude "one little patch".

A dental software company we use literally changed their mind on Win10 support within a month after we put pressure on our customers, and they then put pressure on the vendor. Apparently we weren't the only ones. This same behavior will force vendors into better practices to make their apps and to quickly fix them.

Yes I know there will be some nasty updates/mistakes, but the way I look at it MS has to do this. Their OS won't support them forever and the bigger all in one patching is becoming the norm.
 
Adding "dependencies" while certainly would help organize the mess that was/is supersedence and provide more understanding. What you would end up with is exactly what they are doing now... in order to install this update you have to install last months update.
It would be very different to what we have now, which is not by any means preferred.

There would be the ability to select updates granularly and make a decision based on good foundation while having the groundwork removed if previous updates were missing.
We wouldnt be forced to download unnecessary bundles of data that were only created to reduce our ability to choose.
The current method is the opposite of a win on multiple levels for the consumer.
 
"Based on feedback from customers"... We decided to do what we wanted to do despite the feedback.

I agree, we complain to microsoft, refuse to pay their bill for services that are lacking.

Windows fucking 10, lol. :yuck:

I rolled back to Win7 last week for the last time having tried that idiotic creators update.

holy_svchost_win10_batman.png


Compared to what I have now...

much_better.png


I read the rationale, but at the end of the day this change uses up more ram/resources and ultimately only benefits Microsoft developers.

Mass Effect Andromeda just came out, and it's Directx 11. I've no actual reason to use this piece of shit OS. The only fools enjoying Windows 10 are AMD bitches desperate for irrelevant Directx12 benchmarks. :hilarious:

DUDE!, Not cool! I'm an AMD Bitch (Ryzen!) and I ain't lovin that windows 10 Shit from hell.
I didn't return to windows 7, I'm in Linux for my 37th day consecutive... I've never used Linux as a desktop Operating system before 1st of march 2017.... now I'm almost two months later and haven't booted win10 in 37 days due to playing GTA5...

I can't say I miss Windows, even though the Interface still needs getting used :)

The Xeon still runs windows 7 though.
 
Back
Top