Windows 7 Hotfix repository

You need to login to view this posts content.

 

I always wondered, why IE10 is offered as Important, while IE11 is merely Optional
although both needs "optional" Platfrom Update, and IE10 is support-ended

 

I noticed the same thing, but if you don't know this, who else would be able to know?

Just guessing.
I think IE10 support-ended as is, it is still offered to Server 2008 R2 for reasons specific to business applications, in general Microsoft Server applications, like CRM, BizTalk, Sharepoint. It doesn't make much sense as browsing from the servers should be minimal, ideally at least, except for configurations like Terminal Server (Remote Desktop Host) or Citrix XenApp.

My point of view is that IE11 is not so much different when compared to IE10, only that it sends a more neutral (not IE like) browser agent string.
For that reason, IE10 is more compatible, while offering essentially the same functionality with IE11.

I am not sure if IE10 is still offered to Windows 7. This is easy to test, by hiding IE11, I only did not test recently.

I think IE11 used to be Optional but now comes as Important on a new installation, without being offered IE10 first.
IE10 is not expired like IE9, so it should still be available.

The Platform Update is another thing. It is Optional by itself, but if you install IE10/11 from Windows Update or even from the IE downloaded installer without the pre-requisites while allowing Internet access, the Platform Update is installed in the background, but in the history is flagged as Important. I know that the history does not matter being just a cache, but this is how it appears.

You are probably right when saying that the difference between the various types of updates, Important (Security & Critical), Recommended and Optional is only cosmetic. In addition, according to WSUS (and Catalog I believe) there are other categories like Updates (no distinction there between Recommended and Optional) or Update Rollups, Feature Packs and Definition Updates (MSE, FEP, SCEP, Defender, but also Office Definitions/Junk Mail filter updates).

Recommended updates have superseded sometimes Security Updates and as such, there should be no difference other than cosmetic.

 

My wondering is from very recent clean install
IE10 still important, IE11 still optional

 

I will do another test soon.
I was under the impression that IE11 is presented as important for new installs only with SP1 right now.

 

I did repeated tests, removed SoftwareDistribution and still the same result.
IE11 comes as Important, by hiding it IE10 comes as Important and by hiding IE10, IE9 is no longer offered as it was expired.
It is not in the Recommended category, Recommended check box is unticked and the Recommended updates are listed under Optional with Italic characters.
Maybe the specs would make a difference:
I am testing with a Windows 7 Enterprise 64-bit with 6GB RAM.
Nothing is installed, except for SP1 (without KB2533552) but the agent 7.6.7600.320 is installed as it cannot be easily avoided, unless installing a later one.

EDIT: I actually had .NET Framework 4.6.2 installed manually as one of the 4.x versions is required for the XenTools I use in the virtual machine.
I don't think this would make a difference though.

 

Well, my tests are all x86 (VM, real machine), and IE11 is in the optional section with Platform Update, both not italic
i'll make a clean x64 install to check for differences

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

KB3172605 is not superseded in any level
it just needs the servicing stack update KB3020369/KB3177467

 

Hmm, you are right (as usual), my fault
KB3177467 is offered only now as is the only one left and needs to be installed by itself.
KB3020369 was not offered because it is superseded by KB3177467.
And after installing KB3177467 I was offered KB3042058, KB3172605 and KB3181988.

 

Without 7.6.7600.320 installed, but a higher version 7.6.7601.19161 installed, WindowsUpdate.log shows

940a78SetupChecking for agent SelfUpdate
2017-01-2114:46:44:887 940a78SetupClient version: Core: 7.6.7601.19161 Aux: 7.6.7601.19161
2017-01-2114:46:44:903 940a78MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2017-01-2114:46:44:919 940a78Misc Microsoft signed: NA
2017-01-2114:46:44:919 940a78MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPACA5.tmp with dwProvFlags 0x00000080:
2017-01-2114:46:44:934 940a78Misc Microsoft signed: NA
2017-01-2114:46:44:934 940a78MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2017-01-2114:46:44:934 940a78Misc Microsoft signed: NA
2017-01-2114:46:44:950 940a78MiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2017-01-2114:46:44:950 940a78Misc Microsoft signed: NA
2017-01-2114:46:44:965 940a78SetupDetermining whether a new setup handler needs to be downloaded
2017-01-2114:46:44:965 940a78SetupSelfUpdate handler is not found. It will be downloaded
2017-01-2114:46:44:965 940a78SetupEvaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
2017-01-2114:46:44:981 940a78SetupSetup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
2017-01-2114:46:44:981 940a78SetupEvaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2017-01-2114:46:44:997 940a78SetupSetup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
2017-01-2114:46:44:997 940a78SetupEvaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2017-01-2114:46:45:028 940a78SetupSetup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
2017-01-2114:46:45:028 940a78SetupSelfUpdate check completed. SelfUpdate is NOT required.

With 7.6.7600.320 installed and with a higher version 7.6.7601.19161 also installed

90866cSetupChecking for agent SelfUpdate
2017-01-2118:26:42:952 90866cSetupClient version: Core: 7.6.7601.19161 Aux: 7.6.7601.19161
2017-01-2118:26:43:030 90866cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2017-01-2118:26:43:061 90866cMisc Microsoft signed: NA
2017-01-2118:26:43:061 90866cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP8CC4.tmp with dwProvFlags 0x00000080:
2017-01-2118:26:43:077 90866cMisc Microsoft signed: NA
2017-01-2118:26:43:077 90866cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2017-01-2118:26:43:092 90866cMisc Microsoft signed: NA
2017-01-2118:26:43:155 90866cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2017-01-2118:26:43:155 90866cMisc Microsoft signed: NA
2017-01-2118:26:43:170 90866cSetupDetermining whether a new setup handler needs to be downloaded
2017-01-2118:26:43:170 90866cMiscValidating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe with dwProvFlags 0x00000080:
2017-01-2118:26:43:186 90866cMisc Microsoft signed: NA
2017-01-2118:26:43:186 90866cSetupSelfUpdate handler update NOT required: Current version: 7.6.7600.320, required version: 7.6.7600.320
2017-01-2118:26:43:186 90866cSetupEvaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
2017-01-2118:26:43:186 90866cSetupSetup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2017-01-2118:26:43:186 90866cSetupEvaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2017-01-2118:26:43:248 90866cSetupSetup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2017-01-2118:26:43:248 90866cSetupEvaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2017-01-2118:26:43:342 90866cSetupSetup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2017-01-2118:26:43:342 90866cSetupSelfUpdate check completed. SelfUpdate is NOT required.

Which means that it works without 7.6.7600.320, but it is still looking for it.
Is it better to allow the installation of 7.6.7600.320 first, or it does not really matter?

 

"SelfUpdate is NOT required" looks pretty clear to me, it doesn't matter or needed

 

Hi @abbodi1406

I can't use automatic update on windows 7. Which offline update should I download and install on windows 7 SP1 to make it up to date?

Back in mid 2016 I read this topic and there was 3 update (kb3020369-x64---KB2670838-x64---kb3125574-v4-x64) to install and make windows 7 sp1 almost up to date. any new cumulativeish! update like those 3? what should I download now instead of them?

Thanks in advance

 

You need to login to view this posts content.

 

Currently, KB3138612 gives good results

but the permanent fix is KB3020369/KB3177467 + kb3172605

 

Sorry for bad portray my problem. by "I can't use automatic update" I mean because of office restriction for using internet, not Windows update error.
But I still can install them offline. so I want new offline updates.

Thanks

​

 

KB3138612 update Wuauclt.exe to 7.6.7601.19161 , but kb3172605 update Wuauclt.exe to 7.6.7601.23453

 

You need to login to view this posts content.

 

You need to login to view this posts content.