Windows 7 SP1 Convenience Rollup

[Arthur]

so mount wim, install service stack pack, then unmount & commit wim, then re-mount wim, install rollup pack, unmount & commit wim? (rinse & repeat for each msu) from what you said I take it that would work?

Nope! That won't work since you would still be using Windows XP.

 

DISM is known to be problematic on XP...

 

http://forums.mydigitallife.info/threads/45005-Simplix-Pack-to-update-Live-Win7-System-Integrate-hotfixes-into-Win7-distribution

 

 

I tried the method you suggested (but on a computer running a recent version of Windows) and it didn't make any difference. There were still SFC errors after Windows 7 had been installed.

 

It also took significantly longer to integrate the updates. Over an hour IIRC.

[7point5]

#$%$ I didn't know about the XP compatibility problem thx for the update

 

I tried the method you suggested (but on a computer running a recent version of Windows) and it didn't make any difference. There were still SFC errors after Windows 7 had been installed.

not sure I understand - you mean you tried using dism from a non-XP windows & it still didn't work?!? which windows was it?

 

(and which windows is dism compatible with then?)

Edited June 1, 2016 by 7point5

[Arthur]

you mean you tried using dism from a non-XP windows & it still didn't work?!? which windows was it?

Correct. I was using Windows 10.

 

The problem myself and @mrwoberts had is pictured in post #24. The updates integrate fine, but with SFC errors within Windows 7 once it has been installed so something isn't quite right.

[7point5]

Correct. I was using Windows 10.

 

The problem myself and @mrwoberts had is pictured in post #24. The updates integrate fine, but with SFC errors within Windows 7 once it has been installed so something isn't quite right.

so basically a windows 7 install.wim can only be updated from within an already existing windows 7 OS??? +_+

 

(btw what's an SFC error & when's it noticed? before or after booting with the updated wim?)

Edited June 1, 2016 by 7point5

[Arthur]

so basically a windows 7 install.wim can only be updated from within a windows 7 OS??? that sux :/

That's not right either. I don't think I explained it well.

 

You can integrate Windows 7 updates into Windows 7 .wims using DISM (or the PowerShell equivalent) on Windows 7, 8.1 and 10 (but not XP).

 

It's also possible to integrate Windows 10 updates into a Windows 10 .wim on Windows 8.1 and 10 (but not 7 or XP).

 

Like @mrwoberts, before the Windows 7 SP1 Convenience Rollup was released I didn't have any issues integrating Windows 7 updates into a Windows 7 image on Windows 10.

 

btw what's an SFC error & when is it noticed?

There are many reasons why you might get SFC errors, but in the context of this thread it's caused by something in the Windows 7 SP1 Convenience Rollup as explained here.

 

before or after booting with the updated wim?

After booting with the updated .wim.

[7point5]

alrite I think I get it - basically from any higher-than-7 windows you can edit a windows 7 install.wim file & add all updates to it except the rollup update (only that particular update)?

 

so slipstreaming the windows 7 rollup into a windows 7 install.wim is only possible from within a windows 7? (nothing else not even a more recent windows version like 10?)

[Arthur]

so slipstreaming the windows 7 rollup into a windows 7 install.wim is only possible from within a windows 7? (nothing else not even a more recent windows version like 10?)

No. You can use Windows 7 or higher to integrate the rollup. It's just that the rollup has the SFC issue described above when integrated into an offline Windows 7 .wim image.

[7point5]

It's just that the rollup has the SFC issue described above when integrated into an offline Windows 7 .wim image.

even when doing it from win7?? that's what I'm doing right now (on a win7 virtual machine it's damn slow too)

if so making the wim wont be enough I'll have to test it too. what does an sfc error look like? does it come up during installation or after?

[Arthur]

even when doing it from win7?

Yes.

 

what does an sfc error look like? does it come up during installation or after?

Please re-read posts #53, #55 and #24.

[Arthur]

Microsoft Convenience Update and VMware VMXNet3 Incompatibilities

 

Microsoft recently released a “Convenience Update” patch for Windows 7 and Windows Server 2008 R2 SP1. This update has incompatibility issues with virtual machines running on the VMware vSphere virtualization platform. This incompatibility is confined to one specific configuration scenario – It impacts VMs that use the VMware VMXNet3 virtual network adapter type.

 

VMware is aware of this issue and we are actively investigating the root causes and possible fixes. While this effort progresses, VMware is advising customers to delay applying the Microsoft “Convenience Update” to any virtual machine that uses the VMXNet3 vNIC type.

 

VMware will provide further updates as they become available.

[7point5]

k I didn't notice the link to the other forum

so basically sfc errors harmless & dont prevent windows from running normally that's cool

[mrwoberts]

@7point5 I see you've started another topic

 

here

 

I've answered your questions in the new topic, so shall we keep this topic related to the Convenience rolllup? Cheers

[7point5]

incidentally I noticed that KB2670838 (platform update) is often mentioned by those who install the rollup as one of the packages they include in the streaming

 

and I also noticed (across several forums) that KB2670838 is always added after KB3020369 (the service stack thing)

 

but here's what I noticed:

 

if KB3020369 precedes KB2670838 then KB2670838 takes a horribly long time to add (even though it's only about 10mb)

 

but KB2670838 precedes KB3020369 then KB2670838 takes a short time to add

 

(just happens that KB2670838 was made years before KB3020369 - coincidence?)

 

doesn't that mean that KB2670838 should be integrated before KB3020369?? (does it make a difference)

Edited June 2, 2016 by 7point5

[mrwoberts]

Interesting, I hadn't noticed that.

 

Doh! now the Obsessive Compulsive side of me wants to check that out

 

Edited June 2, 2016 by mrwoberts

[Arthur]

I also notice that KB2670838 was made years before KB3020369 - coincidence?

Read this...

 

http://forums.mydigitallife.info/threads/19461-Windows-7-Hotfix-repository/page262?p=1230845&viewfull=1#post1230845

 

The convenience rollup include almost all the regular updates (General, Security, Hotfixes, .NET 3.5, Features), but not IE updates

 

in addition, it include the updates for most addons or feature packs

only their updates are included, not the feature packs themselves

meaning, you will need to install those packs first, so the rollup can install their updated components afterwards

those are: PlatformUpdate, RDP, WMF4, AD LDS, RSAT, DCA2.0, VirtualPC, WorkFolders, Server Essentials Connector

 

doesn't that mean that KB2670838 should be integrated before KB3020369?? (does it make a difference)

Servicing stack updates (in this case KB3020369) should always be integrated first. The reason should be obvious...

 

The servicing stack includes the files and resources that are required to service a Windows image. This includes the Package Manager executable, the required servicing libraries, and other resources. The servicing stack is included in all Windows installations.

Edited June 2, 2016 by Arthur

[7point5]

then what happens to those who installed the platform update years ago when it came up? should they still install the service stack update or must they skip it? (will it screw up their windows if they install it?) Edited June 2, 2016 by 7point5

[Arthur]

then what happens to those who installed the platform update years ago when it came up?

That's irrelevant in the context of this thread.

 

The majority of this thread has been about integrating the updates into an offline Windows image taken straight from a Microsoft Windows 7 SP1 ISO, not to an existing (online) Windows installation that's been used for years.

[Arthur]

I am glad I didn't bother with the (in)convenience rollup.

 

https://twitter.com/jarwidmark/status/754439717341450240

 

[speckytecky]

What a pity they couldn't just build and issue a SP2 for this well loved product!

[3s-gtech]

Oh joy. I've used it on a few standalone machines, no images. Those machines seemed to do further updates fine, but the installer for the convenience update runs a check for several hours before going through. Actually works out quicker to just install the updates from WSUS. It's pants.

[free780]

All a ploy to jump on Windows 10 / windows 365 ;-) .

[Arthur]

Even more convenience!

 

Further simplifying servicing models for Windows 7 and Windows 8.1

 

In our announcement earlier in May, we introduced a Convenience Rollup update for Windows 7 SP1 and a shift to monthly rollups of non-security updates for Windows 7 SP1 and Windows 8.1. Based on your feedback, today we’re announcing some new changes for servicing Windows 7 SP1 and Windows 8.1. These changes also apply to Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2. (Note: A rollup is multiple patches rolled together into a single update).

 

Why we’re introducing Windows servicing changes

Historically, we have released individual patches for these platforms, which allowed you to be selective with the updates you deployed. This resulted in fragmentation where different PCs could have a different set of updates installed leading to multiple potential problems:

 

• Various combinations caused sync and dependency errors and lower update quality
  
• Testing complexity increased for enterprises
  
• Scan times increased
  
• Finding and applying the right patches became challenging
  
• Customers encountered issues where a patch was already released, but because it was in limited distribution it was hard to find and apply proactively
  

By moving to a rollup model, we bring a more consistent and simplified servicing experience to Windows 7 SP1 and 8.1, so that all supported versions of Windows follow a similar update servicing model. The new rollup model gives you fewer updates to manage, greater predictability, and higher quality updates. The outcome increases Windows operating system reliability, by eliminating update fragmentation and providing more proactive patches for known issues. Getting and staying current will also be easier with only one rollup update required. Rollups enable you to bring your systems up to date with fewer updates, and will minimize administrative overhead to install a large number of updates. (Note: Several update types aren’t included in a rollup, such as those for Servicing Stack and Adobe Flash).

 

Monthly Rollup

From October 2016 onwards, Windows will release a single Monthly Rollup that addresses both security issues and reliability issues in a single update. The Monthly Rollup will be published to Windows Update (WU), WSUS, SCCM, and the Microsoft Update Catalog. Each month’s rollup will supersede the previous month’s rollup, so there will always be only one update required for your Windows PCs to get current. i.e. a Monthly Rollup in October 2016 will include all updates for October, while November 2016 will include October and November updates, and so on. Devices that have this rollup installed from Windows Update or WSUS will utilize express packages, keeping the monthly download size small.

 

Over time, Windows will also proactively add patches to the Monthly Rollup that have been released in the past. Our goal is eventually to include all of the patches we have shipped in the past since the last baseline, so that the Monthly Rollup becomes fully cumulative and you need only to install the latest single rollup to be up to date. We encourage you to move to the Monthly Rollup model to improve reliability and quality of updating all versions of Windows.

 

We are planning to add these previously shipped patches over the next year and will document each addition so IT admins know which KBs have been included each month.

[3s-gtech]

This makes me happy. There will still be 3500 individual Office updates each month, but they tend to be quick to install.

[clockend25]

That's pretty tasty.

[googlemad]

Why do they only decide to do this now?! :/