Fresh reinstall 7SP1 first run WU offers KB976932 (9.1 mb) WTH????

[Urthboundmisfit]

Hello sevenforum gurus! A brief rundown:

I recently (yesterday) reinstalled 7 Home Prem SP1 with all post SP1 updates added (except KB's 2533552, 971033 MSRT & Visual C++ SP1 Redist & the recently added 2993651 which I've chosen to hold off for the time being) using SIW2's excellent Update-win7v5.CMD & tweaked settings, etc with Wincert's WinToolkit... only things "added" were an addon for DotNet 4.5.2 & some custom themepacks, nothing was removed... so imagine my surprise when running WU/ MS Update I was offered KB976932 @ 9.1 mb (screenshot attached) I unchecked this of course, installed the other 4, rebooted and manually checked WU... KB976932 was gone.

Has anyone else seen/noticed this behavior before, and if so to what do you/did you attribute it to? Ex: possible cause(s). Thanks in advance for the anticipated knowledgeable/logical & yes even whimsical responses I've grown accustomed to here @ sevenforums, like Brink says (paraphrasing) There's no silly questions only silly people who don't ask them.

You guys & gals R. O. C. K - ROCK!

View attachment 331020

 

[ignatzatsonic]

I've seen a few inexplicable things from Windows Update. Usually it's being repeatedly offered an update that is already installed.

That particular update you mentioned looks familiar to my eye, but I can't say if it was one of the updates that I'd previously found peculiar.

I ran a search of my hard drive and find that "windows6.1-KB976932-X64.exe" is the name assigned to Service Pack 1 (903 mb in size).

Hmmmm..........

I would not get feverish over it and would disregard it unless you develop problems. Chalk it up to being one of thousands of things we can't ultimately explain about Windows.

 

[Urthboundmisfit]

...I would not get feverish over it and would disregard it unless you develop problems. Chalk it up to being one of thousands of things we can't ultimately explain about Windows.

Thanks for the reply ignatzatsonic (great handle BTW) that's precisely what I felt then & now... just one of those unexplained glitches you see from time to time... I'm not getting as you say "feverish" over it but being the inquiring, anal-retentive geek that I am I thought I'd relate it here @Sevenforums (the #1 IMHO online resource for everything Win7) to see if it might be a recurring glitch & if so did anyone find a root cause or develop a theory for such.

Thanks again, keep up the good work here!

 

[gregrocker]

It's only 9.1 mb so it's likely the SP1 wrapper which only contains the portions of SP1 which it detects are still missing. This is how SP1 is delivered by WUD: After most of its Updates are pushed through it offers only the still-remaining Updates in a wrapper that adds the SP1 label. It apparently detects rightly or wrongly that 9.1 mb of SP1 has not been supplied yet.

 

[Urthboundmisfit]

It's only 9.1 mb so it's likely the SP1 wrapper which only contains the portions of SP1 which it detects are still missing. This is how SP1 is delivered by WUD: After most of its Updates are pushed through it offers only the still-remaining Updates in a wrapper that adds the SP1 label. It apparently detects rightly or wrongly that 9.1 mb of SP1 has not been supplied yet.

I do believe you're spot on Greg... Notice KB2533552 is also 9.1 mb & is the update that prevents the 0xC0000034 error which is by my understanding an "exclusive" prerequisite for SP1. (see attached) This KB cannot be added to an offline image and was not included in my post SP1 update integrated unattended installation. Guess I'll have to add this one to setupcomplete.cmd to avoid this in the future.

View attachment 331102

ETA: "You must spread some rep around before ... gregrocker again"

 

[gregrocker]

It may be anomalous as I've not seen SP1 come through before when using SIW2's Fully Updated media.

 

[Urthboundmisfit]

It may be anomalous as I've not seen SP1 come through before using SIW2 Fully Updated media.

Same here... I've used SIW literally dozens of times...I run it on a monthly basis & test on VM, never offered KB976932 (SP1) before. I just tested in VM the ISO I used to create the USB I used on my "live" install...same result. The only new variable was the 8/26 OOB KB2993651 security update I purposely left out.

Go figure. Thanks for your attention Greg, always appreciated.

 

[Urthboundmisfit]

It's only 9.1 mb so it's likely the SP1 wrapper which only contains the portions of SP1 which it detects are still missing. This is how SP1 is delivered by WUD: After most of its Updates are pushed through it offers only the still-remaining Updates in a wrapper that adds the SP1 label. It apparently detects rightly or wrongly that 9.1 mb of SP1 has not been supplied yet.

I do believe you're spot on Greg ... Notice KB2533552 is also 9.1 mb ...Guess I'll have to add this one to setupcomplete.cmd to avoid this in the future.

Yep, putting KB2533552 in setupcomplete.cmd eliminates WU offering the KB976932 SP1 wrapper:

View attachment 331169

Thanks again Greg for pointing me in the right direction, You ROCK!

 

[gregrocker]

Good work Urthly one.

 

[misha256]

It seems KB976932/KB2533552 are perfectly valid updates for Windows 7 SP1. As Greg observes, KB976932 is just a wrapper for KB2533552 in this case.

My advice is to let Windows Update install KB976932. While the naming of the update is totally misleading for those who have SP1 already installed, it is nevertheless a valid update.

Test/proof: I installed a fresh copy of Windows 7 SP1 on a virtual machine and did a custom Windows Update selecting KB976932 only. New files relating to KB2533552 were installed, versioned higher than what Windows 7 SP1 comes with out of the box.

Conclusion: It all makes sense when you consider KB2533552 was released after SP1. After a fresh re-install, MS need to get the newer KB2533552 files to you and they're using KB976932 as the vehicle.