Windows 7 SP1 Convenience Rollup

[mrwoberts]

Okay, I think I've officially given up with this convenient rollup.

Whilst the integration was much quicker, and thank you @Arthur for providing a solution to do that, but I certainly didn't expect to see this post install...

 

 

On inspection of the updates it wanted to install were some dating back to 2014.

So I still have potentially another 70+ updates that need installing - that convenient rollup from MS suddenly seems less convenient than it could have been.

 

I'm going back to the way I was working before this rollup.

 

Am I missing anything @Arthur?

[free780]

Can't you just approve this update in wsus. Then in MDT it should pick it up in a build and capture. Worst cast wusa.exe as an application before windows updates. Seems easier. Offline servicing has always been a bit of a dark art. Particularly because the install.wim from a win 7 sp1 iso has an out of date wua. Most people put office in their image which means that you have to do office updates in the running OS anyway.

[Arthur]

I certainly didn't expect to see this post install. So I still have potentially another 70+ updates that need installing - that convenient rollup from MS suddenly seems less convenient than it could have been.

You're always going to get some because the Convenience Rollup is already out of date.

 

 

As a test I offline integrated the Simplix update pack and still had 144.8 MB of updates to install. There weren't any SFC errors though.

 

UpdatePack7R2-16.5.15.exe /ie11 /WimFile=D:\install.wim /Index=*

 

 

On inspection of the updates it wanted to install were some dating back to 2014.

That's normal and due to the way WU works (or in this case, doesn't work ).

 

I often see SP1 listed but that doesn't mean the entire service pack will be installed again.

 

 

Offline servicing has always been a bit of a dark art.

Especially with Windows 7. Due to the huge number of updates it's a bit of a nightmare (the specific order they have to be integrated makes it trickier too).

 

I think I will let other people cleverer than me figure out how to offline integrate KB3125574 without the SFC errors.

 

@mrwoberts. This post explains why you get the SFC errors.

 

Like @free780 mentioned above you might want to give MDT a try (if you're not already using it?). It does make the process of creating images a lot easier. More so if you fully automate it.

 

• Building a Windows 7 SP1 Reference Image using MDT 2013 Update 2
  

At this stage I think upgrading to Windows 10 will be more convenient!

 

• Building a Windows 10 Reference Image using MDT 2013 Update 1
  

[mrwoberts]

Thanks for the info and pointers to MDT...

 

I guess that I was expecting something more like SP2 with this update so my hopes were a little dashed after going through various tests...

The old updates that need integrating are a little frustrating though, and I'm convinced that MS could have done something to address/include those, but hey, I've no real idea how much development time that would take, or indeed if they want to spend it on an OS that is in the process of being superseded.

 

I have a fairly decent system already in place to deploy 7 but I was really hoping that this rollup would have made things simpler; yes, it some ways it does, but for what it's worth I'll stick with what I currently have for the coming academic year, which may well be the last for Windows 7 in the schools I support.

 

It's a huge help to read about the testing and subsequent solutions that edu-geekers come up with, so thanks again.

[synaesthesia]

Is it *that* much work to just recreate your image, fully updated?

[A9_IT]

Here are the direct links to those updates...

 

KB2775511 - An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1

[b]KB2732673[/b] - [i]"Delayed write failed" error message when .pst files are stored on a network file server that is running Windows Server 2008 R2[/i]
[b]x64[/b]: http://download.windowsupdate.com/c/msdownload/update/software/htfx/2013/11/windows6.1-kb2732673-v4-x64_801bb11beb007464927d0988992005f63899dab2.msu
[b]x86[/b]: http://download.windowsupdate.com/c/msdownload/update/software/htfx/2013/11/windows6.1-kb2732673-v4-x86_259e505f27ff6feadd21da21ba52e2d4682741ae.msu

[b]KB2728738[/b] - [i]You experience a long logon time when you try to log on to a Windows 7-based or a Windows Server 2008 R2-based client computer that uses roaming profiles[/i]
[b]x64[/b]: http://download.windowsupdate.com/c/msdownload/update/software/htfx/2013/11/windows6.1-kb2728738-v3-x64_22e4457734ff8c995a3637f95ea7848de7956a0d.msu
[b]x86[/b]: http://download.windowsupdate.com/c/msdownload/update/software/htfx/2013/11/windows6.1-kb2728738-v3-x86_ab45e3a08d2ccf2d7049230be68d46f8bce20170.msu

[b]KB2878378[/b] - [i]OpsMgr 2012 or OpsMgr 2007 R2 generates a "Heartbeat Failure" message and then goes into a greyed out state in Windows Server 2008 R2 SP1[/i]
[b]x64[/b]: http://download.windowsupdate.com/d/msdownload/update/software/htfx/2013/12/windows6.1-kb2878378-v2-x64_eb7f7ae83a8d77ba88b228e058fc9c152c211e7a.msu
[b]x86[/b]: http://download.windowsupdate.com/d/msdownload/update/software/htfx/2013/12/windows6.1-kb2878378-v2-x86_06e4de0fece85661cdd00f7fe176401511985ac4.msu

 

KB3020369 - April 2015 servicing stack update for Windows 7 and Windows Server 2008 R2 (prerequisite for the Convenience Rollup)

[b]x64[/b]: http://download.windowsupdate.com/d/msdownload/update/software/updt/2015/04/windows6.1-kb3020369-x64_5393066469758e619f21731fc31ff2d109595445.msu
[b]x86[/b]: http://download.windowsupdate.com/d/msdownload/update/software/updt/2015/04/windows6.1-kb3020369-x86_82e168117c23f7c479a97ee96c82af788d07452e.msu

 

KB3125574 - Windows 7 SP1 Convenience Rollup

[b]x64[/b]: http://download.windowsupdate.com/d/msdownload/update/software/updt/2016/05/windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu
[b]x86[/b]: http://download.windowsupdate.com/d/msdownload/update/software/updt/2016/05/windows6.1-kb3125574-v4-x86_ba1ff5537312561795cc04db0b02fbb0a74b2cbd.msu

 

KB2647954 - The PIN dialog box does not appear or you are presented with all the certificates in the store when you try to access a WebDAV server in Windows 7 or in Windows Server 2008 R2

https://support.microsoft.com/en-gb/kb/2647954 (Download link 404s for me for some reason?)

 

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

From what I read the convenience rollup update supersedes KB2775511 according to Michael Niehaus

 

https://blogs.technet.microsoft.com/windowsitpro/2016/05/17/simplifying-updates-for-windows-7-and-8-1/#comment-4176

[mrwoberts]

Is it *that* much work to just recreate your image, fully updated?

 

You're right, I think I overreacted following my testing of the rollup.

 

I'm aiming to create an updated 'Gold' image for 7, quite probably the last one, and get it tested before the mass roll-out, ready for the new academic year. I'd already spent a few days solid getting updates integrated and tailoring the image when this rollup came along; somehow I convinced myself that I needed to start all over again and so inject this rollup instead.

 

In all the excitement (I'm easily pleased), I forgot that this was not branded as a SP2, and I would always need to add updates, as others pointed out above.

What I meant to say is that I may just stick with what I was working on before this rollup, although I'm still tempted to give it one last shot, along with the subsequent 70+ updates, since as you say, it isn't that much more work. Plus, there is the added bonus of a smaller wim, and a less disk space required post deployment.

 

Have a good half term all.

[7point5]

I spoke too soon. I didn't see it at first, but I scrolled back up in my PowerShell window and noticed the following error message.

 

WARNING: Add-WindowsPackage failed. Error code = 0x800736b5
WARNING: An error occurred applying the Unattend.xml file from the .msu package.

 

Not that it should make any difference but I was using the Mount-WindowsImage, Add-WindowsPackage, Dismount-WindowsImage cmdlets to do the integration, rather than DISM directly.

 

 

Windows 10 Pro (x64) - Build 10586.318.

 

@mrwoberts. The prerequisites section of KB3125574 mentions this...

 

 

 

I should have RTFM!

unfortunately the service stack update is irrelevant

 

I got a similar error when trying to slipstream the rollup using dism ("an error occurred applying the unattend.xml blahblah" + error 0x80070052 + error 82 "the directory or file cannot be created")

 

and yup I'd first applied the previous msu (service stack update) and it slipped in fine yet the same command line with the rollup msu failed

 

and the iso is authentic (verified with md5 & sha1 hashes) it's win7 pro 64bit, so is the dism app (also got if from Microsoft website: WAIK)

 

 

and btw applying the updates manually (in succession, service stack then rollup) works, tested in virtual machine

 

but I can confirm that it's impossible to slipstream the convenience rollup onto a windows 7 disc

those t...s at Microsoft made sure of that

Edited June 1, 2016 by 7point5

[mrwoberts]

but I can confirm that it's impossible to slipstream the convenience rollup onto a windows 7 disc

 

Not one to give up, I did some more testing and I think I've come to the same conclusion, that the rollup is best applied post deployment.

This isn't too bad I suppose, and I'm currently working on a plan of action to do all this with (zero-ish) touch.

 

If I have anything of use, I'll reply back.

[7point5]

Not one to give up, I did some more testing and I think I've come to the same conclusion, that the rollup is best applied post deployment.

yup but actually it can ONLY be applied post-deployment

 

especially since that error message makes no sense (wtf is that 'unattend.xml' file?)

[mrwoberts]

yup but actually it can ONLY be applied post-deployment

 

Well, I have to say that I was able to integrate it without the problem that you experienced, but this is perhaps indicative of the hit-miss aspect to this update. It would have been far simpler (in my naive understanding) for MS to have released SP2 as a media refresh. Still, I'm not going to loose any more sleep over this, particularly as I there are some very clever/helpful folks out there working on a best case solution to deploying a fully-updated image.

 

To see if I can help you with this error, could you perhaps provide us with a clear explanation of your method of integrating and installing... as much detail as you can include.

For example, what is your Host OS, what version of DISM are you using...

 

I'm using Windows 10 Pro x64

DISM 10.0.10586.0

 

I had to *uninstall* my AV (Bit Defender) to be able to work with my 7x64 image. Bizarrely, just disabling the scanning engine didn't work.

 

My DISM commands to slipstream the rollup are.

 

:: Servicing stack
DISM   /image:d:\offline  /add-package  /packagepath:d:\updates\Windows6.1-KB3020369-x64.cab


:: Platform Update
DISM   /image:d:\offline  /add-package  /packagepath:d:\updates\Windows6.1-KB2670838-x64.cab

:: IE11 + Cumulative update
DISM   /image:d:\offline  /add-package  /packagepath:d:\updates\Windows6.1-KB2841134-x64.cab
DISM   /image:d:\offline  /add-package  /packagepath:d:\updates\Windows6.1-KB3154070-x64.cab

Finally, the Rollup...
DISM   /image:d:\offline  /add-package  /packagepath:d:\updates\Windows6.1-KB3125574-v4-x64.cab

 

But, I may well stick to applying the Servicing stack and rollup online, and instead, integrate other updates I'm missing offline.

[7point5]

^ ok so in your list I only used the 1st & last packages (service stack + rollup). never heard of that KB2670838 but apparently it got a looot of bad reputation (breaks a lot of configs) so dunno if I should download that one or not

 

also my files are both msu (is cab better??)

 

anyway host OS is XP SP3 32bit - that's the only reason to upgrade to 7 I guess - I hesitated to say this cause I know most ppl are gonna say that this is the reason it didn't work (but then why did the 1st package integrate without a hitch & only the 2nd package fail to integrate? both are authentic btw)

 

 

as for DISM I'm using the one from this: https://www.microsoft.com/en-ca/download/details.aspx?id=5753

 

 

and I'm using the command lines described there: The Last Windows 7 ISO You?ll Ever Need: How to Slipstream the Convenience Rollup

 

(I gave the directories the same name & path so I could just copy-paste each line into a single-line .bat file which I edit between each step. the only difference is the C: which I replace with the drive letter of my external hard drive)

[themightymrp]

That version of DISM doesn't mention XP as a supported operating system. You hate to mention it, but this is most likely your issue

[Arthur]

anyway host OS is XP SP3 32-bit

I would save yourself the trouble by skipping 7 and going straight to 10.

[7point5]

windows 10 too recent, don't trust it yet plus wanna avoid the adware in it atm ^^

 

That version of DISM doesn't mention XP as a supported operating system. You hate to mention it, but this is most likely your issue

figured the OS would be blamed

 

prob is if it was the OS then wouldn't the app just crash?

 

like anything from "program has to terminate cause xxx.dll wasn't found" to "this is not a valid win32 application"?

 

instead everything works fine & the error message appears to be more about the package than about the app used to install it

[themightymrp]

Looking at the error you are getting (0x80070052), do you have enough drive space and permissions on the file structure? Also, could it be referencing a file location that is 64bit only?

[7point5]

Looking at the error you are getting (0x80070052), do you have enough drive space and permissions on the file structure?

the drive I'm working on is 250gb NTFS so that should be enough

 

and I'm always logged on as admin on windows XP ^^

 

Also, could it be referencing a file location that is 64bit only?

alrite that I'll admit I don't understand what that means

(I know that memory blocks above 2gb can't be addressed in a 32bit OS cause of the way binary works but that's about it)

 

the first .msu package is only 10mb it takes little time for the addpackage command to work & it integrates fine

the next .msu package is almost 500mb now that's big but surely that can't big enough for an app to fail??? (also dism doen't crash, just says that an error occurred. I'm able to unmount the whole thing normally afterwards)

[themightymrp]

I'm probably barking up the wrong tree with the 64bit file location thing. To be honest I haven't used 32bit Windows for quite some time!!

[mrwoberts]

^ ok so in your list I only used the 1st & last packages (service stack + rollup). never heard of that KB2670838 but apparently it got a looot of bad reputation (breaks a lot of configs) so dunno if I should download that one or not

 

The historical problems with KB2670838 were mostly related to graphics card software, and the occasional bsod with ie10... I've never knowingly had problems with that update over the past couple of years. Also, it is a pre-requisite for IE11, so you'll need that if you intend to use IE.

 

also my files are both msu (is cab better??)

 

I don't know whether they are better, but I have previously come across reports of .msu files not working, whereas the extracted .cab file does. Try it.

 

(I gave the directories ... the only difference is the C: which I replace with the drive letter of my external hard drive)

 

If I understand that statement correctly, you are using an external hard drive during the integration??? Is that where the .wim resides, or is that the mount folder? Either way, I would avoid including an external hard drive in this process. Try to do the whole job on the C drive if you have enough space. Maybe the permissions problem is related to the exHDD.

 

Another possible test could be to run a Windows 7 (x64) PE disc, which includes the DISM command, and try out your integration in that. The files can all stay on your internal C drive, and be accessed as normal from the PE environment.

[7point5]

The historical problems with KB2670838 were mostly related to graphics card software, and the occasional bsod with ie10... I've never knowingly had problems with that update over the past couple of years. Also, it is a pre-requisite for IE11, so you'll need that if you intend to use IE.

firefox & opera here ^^ I know IE could be needed in the future so maybe gonna keep it (although, is IE11 necessary or IE10 enough? tbh I don't even know what version of IE comes with win7 SP1)

 

I don't know whether they are better, but I have previously come across reports of .msu files not working, whereas the extracted .cab file does. Try it.

7zip says that each msu file has 2 cab files (a big one & a small one, I reckon the small one ain't necessary to extract?)

 

If I understand that statement correctly, you are using an external hard drive during the integration??? Is that where the .wim resides, or is that the mount folder?

both. just like in that link:

http://www.howtogeek.com/255540/the-last-windows-7-iso-youll-ever-need-how-to-slipstream-the-convenience-rollup

 

except that c: is replaced with the external drive letter

Either way, I would avoid including an external hard drive in this process. Try to do the whole job on the C drive if you have enough space. Maybe the permissions problem is related to the exHDD.

 

but if it's permissions then wouldn't 1st package fail to integrate??? (let alone any reformat attempt)

 

anyway I'll try using a partition on one of my fixed drives to see if this works. also at the same time work on cab files only that way test 2 theories at once

 

 

Another possible test could be to run a Windows 7 (x64) PE disc

never heard of

if that thing's downloadable then I'll try

Edited June 1, 2016 by 7point5

[7point5]

k so using a local (internal) drive failed, using cab instead of msu also failed, same error messages. gonna try find that windows 7 PE whatever that is (hope it won't do damage or something)

 

btw in the log file the error appears to be these lines:

 

2016-06-01 18:44:32, Info CBS Appl: Evaluating package applicability for package Package_for_KB3125574~31bf3856ad364e35~amd64~~6.1.4.4, applicable state: Installed

2016-06-01 18:51:20, Info CBS Failed to extract files from cabinet Windows6.1-KB3125574-v4-x64.CAB [hrESULT = 0x80070052 - ERROR_CANNOT_MAKE]

2016-06-01 18:51:20, Info CBS Failed to extract all files from cabinet Windows6.1-KB3125574-v4-x64.CAB [hrESULT = 0x80070052 - ERROR_CANNOT_MAKE]

2016-06-01 18:51:20, Info CBS Failed to extract all files from cabinet Windows6.1-KB3125574-v4-x64.CAB [hrESULT = 0x80070052 - ERROR_CANNOT_MAKE]

2016-06-01 18:51:20, Info CBS Failed to add package: Package_for_KB3125574~31bf3856ad364e35~amd64~~6.1.4.4 [hrESULT = 0x80070052 - ERROR_CANNOT_MAKE]

2016-06-01 18:51:20, Info CBS Failed to prepare starting packages [hrESULT = 0x80070052 - ERROR_CANNOT_MAKE]

2016-06-01 18:51:20, Error CBS Failed to process single phase execution. [hrESULT = 0x80070052 - ERROR_CANNOT_MAKE]

 

so it's an extraction error - what the hell? I can install that package perfectly fine manually (in virtual win7 64 SP1) as long as the servicing stack package is installed beforehand. yet the same install fails in dism

 

also what exactly's it trying to extract? it's like files are missing in the archive yet the rollup file is authentic (I checked the SHA1 hash)

 

so wtf???

[mrwoberts]

Why don't you just run your integration commands (DISM) inside your VM and save the headache. I'm assuming you're wanting to create an offline-updated image/iso... ??

[7point5]

I thought of that

 

it's just that my hardware ain't exactly top of the line (4 gb ram, limited to just above 3 gb on XP. can put maybe 1.5gb max on the VM and maybe give it 2 of my 4 cores hopefully that won't slow down my rig to a crawl). could take hours to process & success is still uncertain

I'd also have to give the VM write permission on the shared folder (I normally keep host <-> guest communication one-way, host to guest only)

 

but I guess I don't have much choice now (that "windows PE" method someone mentioned looks awfully complicated)

Edited June 1, 2016 by 7point5

[Arthur]

windows 10 too recent, don't trust it yet plus wanna avoid the adware in it atm ^^

Download ShutUp10. Problem solved!

 

4GB RAM is fine for Windows 10. You would also be able to use the full 4GB rather than just 3-3.5GB.

 

figured the OS would be blamed. prob is if it was the OS then wouldn't the app just crash?

It's impossible to integrate recent cumulative updates into offline Windows 10 images on a computer running Windows 7, so it's not hard to imagine XP would have similar issues with Windows 7 updates and images.

 

Nothing would crash btw. You would just see errors in your DISM log and the updates wouldn't be integrated.

 

I don't think you are going to get anywhere using XP.

Edited June 1, 2016 by Arthur

[7point5]

Download ShutUp10. Problem solved!

 

4GB RAM is fine for Windows 10.

 

 

It's impossible to integrate cumulative updates into offline Windows 10 images on a computer running Windows 7, so it's not hard to imagine XP would have similar issues with Windows 7 updates and images.

 

Nothing would crash btw. You would just see errors in your DISM log and the updates wouldn't be integrated.

 

I don't think you are going to get anywhere using XP.

wait one - so what if instead of trying to add 1 package after another in the same mounting session, I do it separately?

 

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?

Edited June 1, 2016 by 7point5