No previews of Monthly Rollups

Topic

New Reply

The English translation is up on InfoWorld Woody on Windows, Signs point to Microsoft’s imminent release of Windows 7 “Service Pack 3” As MrBrian note
[See the full post at: No previews of Monthly Rollups]

Reply | Quote

Replies

From yawns to relief to cheers, thanks, Woody! 🙂

Reply | Quote

Do you think this is because they’re going to start integrating older fixes and all that into the rollups so they want to focus on that for now rather than making new fixes?

Reply | Quote

Watch out everyone for the Preview of the March Monthly Rollups. This is supposed to be the first big one, something like KB3125574.

Reply | Quote

That’ll be coming out the third Tuesday in February – or Feb. 21, the day after President’s Day in the US.

Reply | Quote

Entirely possible.

Reply | Quote

Hello Woody,

As Susan Bradley has now given her imprimatur to the January security updates, it looks like the Big Board is about to be displaying a status change.

“I… I don’t know exactly how to put this, sir, but are you aware of what a serious breach of security that would be? I mean, he’ll see everything, he’ll… he’ll see the Big Board!” … “Gentlemen, you can’t fight in here! This is the War Room!” (With apologies to Stanley Kubrick; sorry, but I just couldn’t resist.)

Reply | Quote

Mumble mumble… precious bodily fluids… mumble…

Reply | Quote

Not to mention fluoridation (and Cobalt Thorium G).

Reply | Quote

They won’t add all previous fixes at onces 🙂
they said it won’t reach KB3125574 level up until second half of 2017

besides, Monthly Rollup will not have .NET 3.5.1 fixes like KB3125574 😉

Reply | Quote

This new rollup model is boring, i lost the joy of experimenting individual updates 😀
the preview rollup still have a part of the fun

Reply | Quote

Windows 10 updating model may keep you busy instead. 🙂
Here is something interesting about Delivery Optimization which is not quite explained in detail in other places. The article is related to WSUS/SCCM, but it has wider scope than only WSUS/SCCM.
https://blogs.technet.microsoft.com/windowsserver/2017/01/09/why-wsus-and-sccm-managed-clients-are-reaching-out-to-microsoft-online/

Reply | Quote

I didn’t say the newer version of KB3125574 🙂
And Microsoft’s implementation keeps changing, so we may or may not see the .NET 3.5.1 included in the Rollup which would be more natural than bundling with 4.x, taking in consideration that in Windows 7, .NET 3.5.1 is built-in.

Reply | Quote

Thanks
I personally disable DO on sight 🙂

Reply | Quote

Woody, if the March Rollup or what will come later is supposed to be the SP3, how would you classify this largely unknown rollup?

https://support.microsoft.com/en-us/kb/2775511

Abbodi convinced me that this rollup is completely superseded by KB3125574 and Microsoft’s Michael Niehaus claims the same without much detail. This is not reflected in the supersedence as per Catalog.

But at its time of release, KB2775511 was considered “Service Pack 2”. I would call it now in perspective “Service Pack 1.5” 🙂

Reply | Quote

My “Group B” Win7 SP1 systems are just fine.

I happily avoided the 3125574 Convenience Rollup and will also avoid any future Convenience Rollups or “Service Pack” style updates.

However, it’s plausible that the ham-fisted bully on the block may require them as a prerequisite for future Security Only Updates. I guess I’ll cross that bridge when I come to it.

Reply | Quote

The question is HOW do you disable DO/WUDO?

Set to HTTP only (value 0) seems not to disable completely and the only “good” values would be Simple (99) which keeps the DO mechanism except for reporting back to the Cloud services or Bypass (100) which reverts apparently to BITS. Value 100 would be the true disabling of DO and reverting to previous mechanism, but does anyone have clear information about what each value does or does not?
The information available seems to be very limited and confusing.

Reply | Quote

Susan Bradley recommended installing 3212646 Security Update on Win7 systems. I have now tried three times. It keeps saying that it is unable to install the update. (><)

(I am a securities updates only Win7 gal.)

Reply | Quote

Fascinating. I have no idea how it fits into the long-term scheme of things, but Abbodi knows this stuff cold.

Reply | Quote

I turn off “Get updates from other location..” in Settings, then i set the bypass policy
https://technet.microsoft.com/en-us/itpro/windows/manage/waas-delivery-optimization

btw, when setting the registry values manually, you need to set it as decimal 🙂

reg add HKLMSOFTWAREPoliciesMicrosoftWindowsDeliveryOptimization /v DODownloadMode /t REG_DWORD /d 100 /f

Reply | Quote

So you use Bypass. 🙂
Thanks, this is what I use now, but I have always questioned the value of Simple (decimal 99) and also HTTP (decimal 0) – the last one being the only one available before 1607 which gave a similar effect.

Reply | Quote

I think KB2775511 is largely forgotten now, KB3125574 is the new star… for a while.

Reply | Quote

I don’t think Susan Bradley is into Security Only patches, but rather into Monthly Rollups, like almost everyone in the industry, with only one notable exception 🙂

Reply | Quote

Guilty as charged. 🙂

Reply | Quote

😀 😀 😀

Reply | Quote

Okay. She does rollups. However, she recommended this rollup because it there is a security issue being patched, which is why I am bothering. It shows on my important updates.

Is anybody else finding it won’t install, or is it likely unique to my setup? Between Ms Adobe, seems like I spend a third of my computer time installing and battling with these never ending updates.

Reply | Quote

For me it’s was just a Hotfix Rollup since the beginning, similar to our July 2016 Rollup 🙂

as for the supersedence, i have one detail that you might not like 😀

KB2775511 is “programmatically” replaced by KB3125574, but it’s not superseded bit by bit, hotfix KB2728738 is needed to complete the supersedence

if you check KB2775511 article, you see that 3 hotfixes are proposed to be installed after it
https://support.microsoft.com/help/2775511
2732673 & 2878378 are included in KB3125574, but 2728738 is not
even though the fixed Profsvc.dll is included with KB3125574, but mentioned registry value is not
https://support.microsoft.com/help/2728738

that’s it 🙂

Reply | Quote

Possible mistake in article: “First Tuesday: All Office patches (typically there are many), both security and nonsecurity, appear on the first Tuesday of each month.”

However, from https://blogs.technet.microsoft.com/office_sustained_engineering/2016/03/28/upcoming-change-to-the-release-schedule-for-non-security-updates/:
“Updates with the Security classification will continue to release on second Tuesday as usual.”

Reply | Quote

You’re right. Thanks!

Reply | Quote

you shouldn’t avoid 3125574.

Reply | Quote

Searcher, why not? Group B folks have not been installing rollups (except those that are .Net rollups). Wouldn’t installing this rollup turn us into Group A??

Reply | Quote

The Convenience rollup KB 3125574 (I call it “Service Pack 2”) is entirely optional. If you’re keeping up on patches, you don’t need or want it.

Reply | Quote

woody, thank you for the reassurance, as I have been keeping up on patches . . . thanks to you 🙂

Reply | Quote

Woody, I think, this is little bit different situation. I can imagine, that MS simply said> there is nothing nonsecurity, we would like to patch on Dec/Jan.

But, installing new PCs and whats strange, ALSO November nonsecu rollup is not detected to install.

If its true – MS simply does not improve anything nonsecurity in Dec/Nov, still new computers, installed from sratch – should detect (WinUpdate) last missing nonsecurity patch from November (3197869) – and it doesnt…

Strange, strange, strange. And few days later, MS start their PR about “old Win7”

Reply | Quote

But there was a Monhtly Rollup in November…

Reply | Quote

I know.
But for unknown reason, this November Rollup is not offered to install in computer (lets say) last updated in September….. whats confusing (that is THE thing, I am reporting).

When this happened to me in Dec, I was thinking: Wow, they have found some major bug in previous Rollup and canceled Dec Qua Rollup and stop propagating November one, but now, in January…. it sounds to me like> Look, you looser user, Windows 7 is old, upgrade and silently canceled Quality Rollup even those, they have been released in Nov/Oct.

For those, patching every month, this effect is not vissible. In November they installed NovemberRollup, so they are not missing it in Dec. Personally, since Win10Upgr s**t, I have decides to make full offline copy of available patches every month, so lets say, I can install Win7SP1 ver Sep, ver Oct, ver Nov, etc…. and every month, I am not testing suggested patches they are “differental” (between months), but like brand new PC/Win right now. And thats how I found, that something nasty is happening.

Reply | Quote

Care to explain the status more clearly? 🙂
Preview rollups will not be shown if there is a higher Security rollup is available

Reply | Quote