Different number
yours
Windows 7 Service Pack 1 6.1.7601.17640 / 6.1.7601.21755 (2011 / Multi)
KB982861: Internet Explorer 9.0 9.4.8112.16434
what we're looking for is
9.4.8112.16443
(Yeah - I get dyspraxic about this time of night, as well! :))
I have someone else looking for the patch as well - he may even have it already, but not be close to his main box.
I found this log from another website. I think it matches what we are lookng for 9.4.8112.16443
I went and downloaded KB2744842 x64 for Windows 7, but the cab file contains manifests for 9.4.8112.16450
I don't know how Microsoft numbers there updates, would it be as simple as looking for a KB a few revisins back?
WindowsUpdateAgent.
2012-11-18 14:12:39, Info CBS Appl: detect Parent, Package: Package_for_KB2744842~31bf3856ad364e35~x86~~9.4.1.0, Parent: Microsoft-Windows-InternetExplorer-VistaPlus-Update~31bf3856ad364e35~x86~~9.4.8112.16443, Disposition = Detect, VersionComp: EQ, ServiceComp: EQ, BuildComp: EQ, DistributionComp: GE, RevisionComp: GE, Exist: present
2012-11-18 14:12:39, Info CBS Appl: detectParent: package: Package_for_KB2744842~31bf3856ad364e35~x86~~9.4.1.0, parent found: Microsoft-Windows-
Life is fun when you start looing at update versioning :)
I have downloaded and extracted every IE9 x64 update I can find - without success.
This could mean that you have a withdrawn update installed (my guru has also been unable to find the files), or that you have some secondary IE-related program installed.
What do you have listed in the Internet Options > Manage Add-ons listing??
Noel,
Attached is my IE add-on screenshot.
If this patch doesn't seem to be very popular or even available, couldn't we just delete all references to it from the registry? Is that another approach you would recommend taking?
Life is never that simple, unfortunately - just removing the registry entries involved is likely to seriously break 'something'
I've been occupied the past 48 hours, so haven't had much opportunity to continue the search - I *will* find it (eventually!)
Shout at me every so often, in case I get side-tracked :)
Okay so I was able to track down IE9-Windows6.1-KB2675157-x64.msu
And does contain some manifests with 9.4.8112.16443 so i copied over the manifests and packages and re-ran SURT tool and I think it fixed 6 errors.
Can you download IE9-Windows6.1-KB2675157-x64.msu and see if there is anything I missed?
Thanks
By the way the way I found that patch was using this link
Microsoft Security Bulletins
I kept rolling back to the previous Cumulative Security Update for Internet Explorer until I found the one that contained 9.4.8112.16443 files
The interesting thing about that CheckSUR report is that all the files were replaced by the ones from CheckSUR itself, rather than the ones you copied :)
If you loot at the 'fix' lines....
... it shoes the source as being the CheckSUR .cab files.Code:Line 38: (fix) CSI Manifest and S256H Do Not Match CSI File Replaced File: x86_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.16443_none_a7a5a98a6c2d4c7c.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab1.cab Line 44: (fix) CSI Manifest and S256H Do Not Match CSI File Replaced File: wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.8112.16443_none_e381b5efb531f87f.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab1.cab Line 46: (fix) CSI Manifest and S256H Do Not Match CSI File Replaced File: x86_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16443_none_551baf7cf0eec21f.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab1.cab Line 50: (fix) CSI Manifest and S256H Do Not Match CSI File Replaced File: wow64_microsoft-windows-scripting-jscript_31bf3856ad364e35_9.4.8112.16443_none_01bf31e6fe374643.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab1.cab Line 52: (fix) CSI Manifest and S256H Do Not Match CSI File Replaced File: x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16443_none_1a54f6f7bc27cdeb.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab1.cab Line 55: (fix) CSI Manifest and S256H Do Not Match CSI File Replaced File: x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_9.4.8112.16443_none_cd4f1b55f11ea758.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab1.cab
....still hunting
Okay I've made little more progress I am now down to 17 errors. I was wondering how hard it would be to modify the catalog to point back to version 9.4.8112.16421 for the remaining files.
I took the files that match the name except for the version from 9.4.8112.16421 and renamed them and tried to trick the SURT tool into thinking the file versions matched but it's not liking it.
Can you help me go for the next potentially dangerous thing, just so I can get to a point where I can either uninstall IE9 and reload it so that I can then install IE10?
Let me know what you think.
Thanks
Oh, Dear
Not a good thing to attempt!
The CAT/MUM files and associated registry keys are an immensely complex area of interdependencies - and I have no idea what you've done or not done(and I don't understand it well enough to attempt that for myself, either.)
the (w) error lines possibly indicate permissions errors on those files or registry entries - TrustedInstaller must have full permissions.
I'm not sure what the way back would be, either
Quote