No, it is not his opinion only. This update is not an update as such. This "update" should be run manually every time after all updates or hotfixes got installed. This also means if you integrate updates and hotfixes this so-called update should be run as run-once or something.
This is what M$ says: The System Update Readiness Tool is used to resolve inconsistencies in file data or registry data. When file data or registry data is inconsistent, your computer may be unable to install updates from Windows Update. After the System Update Readiness Tool is installed, you can install updates from Windows Update on your computer. The System Update Readiness Tool scans for inconsistencies in your computer as it is being installed. It typically takes less than 15 minutes to run the scan. However, the tool might take significantly longer on some computers. Although the progress bar may seem to stop, the scan is still running and you should not cancel the update. It fixes issues in the Windows Servicing Store for future updates or service packs as well software which will probably be prevented from being installed without this kind of update.
I have 14/03/2012 07:59 633,534 Windows6.1-KB999159-x86.msu <assemblyIdentity name="Microsoft-Windows-DriverFrameworks-UserMode" version="6.1.7601.22039" processorArchitecture="x86" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <assemblyIdentity name="Microsoft-Windows-DriverFrameworks-UserMode.Resources" version="6.1.7601.22039" processorArchitecture="x86" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> In last update 27/07/2012 20:53 1,065,217 Windows6.1-KB2685813-x86.msu <assemblyIdentity name="Microsoft-Windows-DriverFrameworks-UserMode" version="6.1.7601.22002" processorArchitecture="x86" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <assemblyIdentity name="Microsoft-Windows-DriverFrameworks-UserMode.Resources" version="6.1.7601.22002" processorArchitecture="x86" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> Which is 'better' ?
Definitely the last one (KB2685813). Despite the update version being lesser than KB999159, the files the update updates are actually newer. These are Windows 8 components for Windows 7. KB999159 is basically Windows 8 RP 8400, and KB2685813 is Windows 8 RTM 9200. The same goes with KB999158 and KB2685811, KB2685811 is the one that should be used. In actual fact, KB2685811 and KB2685813 (and the superseded KB999158 and KB999159) may be separate updates, but they should both be installed together. As KB999158 and KB999159 are superseded they are no longer required. They MUST be uninstalled before installing KB2685811 and KB2685813.
i ignored 2647753-v3 if somebody likes this faulty update ask. i think it was the publishing of 2647753-v3 and 2712808 that causes the problems on x64. maybe also 2713128 solves the problem. (2712808 and 2713128 supersed parts of 2647753) I had no problems on my x64 computers using 2647753-v2 which was installed some months ago.
new is v3 (sometimes i forget the version numbering) paced in the "OLD for BAD" folder on my server interesting 2578113 -v2: for terminal server amd64_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.1.7601.22024_none_9caf238bfc7ac045.manifest amd64_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.1.7601.17866_none_9bfc6f82e37b8fab.manifest -v1: for cluster server amd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.1.7601.21772_none_1f47632fcceae532.manifest never saw a update change like that. maybe thats the reason MS removed 2578113-v2 from the hotfix server 2578113-v1 is superseded with 2685891 so it is not needed anyway.
Komm, you forgot the KB2703157 (IE8) in the "removed" liste from your changelog and remove it in the IE8 folder
If you miss anything, let me know: x64: 17.08.2012 Added: KB2520487-v3 KB2673042 KB2693010 KB2695321 KB2703811-v2 (Additional/RSAT) KB2704372-v6 KB2704377-v5 KB2706051 KB2719306 KB2719375 KB2722727 KB2722729 KB2723248 KB2724133 KB2724137 KB2724629 KB2725604 KB2726399-v2 KB2727101 KB2727324 KB2727330 KB2727941 KB2727998 KB2729608 KB2729670 Windows6.1-KB2732072.reg KB2732072-v2 KB2732595 KB2732618 KB2732840 KB2732846 KB2733563 KB2733955 KB2733994 KB2734410 Removed: KB2519944 KB2520487-v2 KB2577550 KB2582203-v2 KB2633205 KB2653810 KB2612966 KB2659493 KB2661641 KB2664888-v2 KB2683817 KB2686921 KB2688892-v2 KB2699817 KB2701275 KB2707319 KB2708549 KB2708625 KB2714030-v2 KB2716163 KB2722392 ------------------------------ x86: 17.08.2012 Added: KB2520487-v3 KB2673042 KB2693010 KB2695321 KB2703811-v2 (Additional/RSAT) KB2704372-v6 KB2704377-v5 KB2706051 KB2719306 KB2719375 KB2722727 KB2722729 KB2723248 KB2724133 KB2724137 KB2724629 KB2725604 KB2726399-v2 KB2727101 KB2727324 KB2727330 KB2727941 KB2727998 KB2729608 KB2729670 Windows6.1-KB2732072.reg KB2732072-v2 KB2732595 KB2732618 KB2732840 KB2732846 KB2733955 KB2733994 KB2734410 Removed: KB2519944 KB2520487-v2 KB2577550 KB2582203-v2 KB2612966 KB2633205 KB2653810 KB2659493 KB2661641 KB2664888-v2 KB2683817 KB2686921 KB2688892-v2 KB2699817 KB2701275 KB2707319 KB2708549 KB2708625 KB2714030-v2 KB2716163 KB2722392 7zip is being prepped. KB947821-v24 will be uploaded a little later.
I compared the two repo, and if I have not made a mistake in your repo McRip: Added: 2724781, 2727118, 2728738, Removed: 2633127, 2685867, 2686857, 2686867, 2691442, 2696718 komm: Added: Removed: KB2714030-v2, EDIT: Updated, Tell me, if I'm wrong not in the changelog (Removed), but not found on the repo
I'll upload the updated Superseded/old update remover once any amendments, if necessary, are made, and as its 6am Saturday morning here, when I'm actually at home later to do it