I won't stop it, because I need it for XP, too. Don't worry. But on the server I already replaced it with 4.5.
I started with a new wim that did not have 999158 and 999159 previously installed and reran the updates from then on. Even though KB2685811 and KB2685813 now show the correct file versions from the mounted image (6.2.9200.16384). KUC says bad file version with remove status. The new version should be okay and doesn't need to be removed right?
McRip, Sorry for offtopic! In the process of scanning any new non-public hotfixes after KB2584577, KB2681116 and KB2629462 for Windows XP SP3 is not met?
I don't know why for you it's not OK Me, I integrate hotfix with SoLoR's script modified (offline script)
Anyone know why remnants of removed packages can still be found in a mounted image ( \Windows\servicing\Packages) even after committing the image? Specifically .mum and .cat files of superseded fixes remain in the image. Is this normal? Example KB2425227 Code: Directory of R:\Offline\Windows\servicing\Packages 12/20/2010 12:46 9,150 Package_2_for_KB2425227~31bf3856ad364e35~x86 ~~6.1.1.1.cat 12/20/2010 12:40 2,710 Package_2_for_KB2425227~31bf3856ad364e35~x86 ~~6.1.1.1.mum 12/20/2010 12:46 7,394 Package_for_KB2425227_SP1~31bf3856ad364e35~x 86~~6.1.1.1.cat 12/20/2010 12:40 1,929 Package_for_KB2425227_SP1~31bf3856ad364e35~x 86~~6.1.1.1.mum 12/20/2010 12:46 7,394 Package_for_KB2425227~31bf3856ad364e35~x86~~ 6.1.1.1.cat 12/20/2010 12:40 2,782 Package_for_KB2425227~31bf3856ad364e35~x86~~ 6.1.1.1.mum 6 File(s) 31,359 bytes Directory of R:\Offline\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04 FC295EE} 12/20/2010 12:46 9,150 Package_2_for_KB2425227~31bf3856ad364e35~x86 ~~6.1.1.1.cat 12/20/2010 12:46 7,394 Package_for_KB2425227_SP1~31bf3856ad364e35~x 86~~6.1.1.1.cat 12/20/2010 12:46 7,394 Package_for_KB2425227~31bf3856ad364e35~x86~~ 6.1.1.1.cat 3 File(s) 23,938 bytes Al
Why is 2728738 superseded by 2719375? First of all 2728738 contains 2 packages: Code: windows-profsvc 6.1.7601.22055 usesmbbasedbandwidthandlatency 6.1.7601.22055 2719375 only one: Code: windows-profsvc 6.1.7601.22056 So my first thought was NO. But then PointZero told me he had no usesmbbasedbandwidthandlatency entry in his winsrx folder. That normally means the package is not applicable. And if a package is not applicable and all the other packages are superseded, then the hole hotfix is superseded. But that was not right in this case since usesmbbasedbandwidthandlatency sets the registry value: Code: HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\ProfSvc\Parameters\UseSMBBasedBandwidthAndLatency to 0x00000001 After installation of 2728738 the value is set. So my second thought was NO. What I know was 2719375 is superseding the windows-profsvc part of 2728738. What does 2719375 do? It updates the profsvc.dll to version 6.1.7601.22056. So I take a look at the old an the new dll files. The old one uses the reg value set in 2728738 but the new one does not. MS has change the value the dll looks for from UseSMBBasedBandwidthAndLatencyTo UseSMB1BasedBandwidthAndLatencyIn addition this new registry value is not created automatically. That means even if the old registry value is present, it will not be used if 2719375 ist installed. That let me assume, that the problem described in KB2728738 is solved in 2719375 without the use of a registry value and MS leaves a longstop in the code to fix: whatever. So my third thought is YES. We can summarize: Even, if 2728738 is installed, no package of it is used, as far as 2719375 is installed. Or in other words: 2728738 is superseded by 2719375. BUT: there is a really small possibility, that MS releases a new version of “profsvc.dll” that also uses the old registry value.
Thanks to PointZero who drew my attention to some points. 22.08.2012 Added: KB2733446 Removed: KB2633127-v2 Moved KB2524840 from main folder to Additional/VPC Moved KB2645594 from Addtional/DisableCoreparking to main folder Moved KB2703811-v2 from Addtional/RSAT to main folder
Out of curiosity, why is KUC complaining about KB2685811 and KB2685813 if the most current file versions are installed and 999158 and 999159 were never installed previously? Al
hi Al, I think the answer to your question is in KUC's changelog for ver 0.8.006.007: ... For me it was not possible to integrate 2685811/2685813 correctly into the DVD. So I marked 2685811/3 as DVD prohibited to ensure that the installation works correctly online after system installation. The problem does not occur, if 999158 and 999159 have not been integrated. So you may be able to integrate these updates successfully. But I want to be on the safe side. ... ------------- to all: looks like komm has updated KUC for the newest batch of updates. Click on the link in his his post above to get the new version.
Dumb question: is there a guide or something that tells me how to use burf's "Installer For Windows Updates" script? I think I've done something wrong. Before I used the installer (v26f), I updated WU and it said the only things to install were a couple of office 2010 updates and the malicious software removal tool. All good. Then I got excited and used the installer to install a couple of non-security updates from McRips's repo and then (without restarting!) to remove updates that were no longer required. After restart WU is showing me 7 updates, which I know were previously installed (I kept a close eye on what gets installed on this system). Three of updates are security ones dating from jun-2011 (2544893), feb-2012 (2645640) and may-2012 (2659262). The other non-security updates shown are 2541014, 2647753, 2718704 and 2695962. Has the installer removed too much? Or has WU lost the plot? Or have I hosed my system? Cheers John
You haven't hosed your system, just the opposite. The installer can install any combination of updates, and its not a requirement that you install all updates. Installing all updates is only a requirement if you use the superseded update remover. The updates show in Windowsupdate because Windowsupdate requires that both GDR and LDR versions these files are installed. You can either download them through Windowsupdate or download them manually and run the script over them again with the 'install all updates' (option 1). The script has a list of updates internally that is used to know whether both versions (GDR and LDR) need to be installed or not. If they were already installed it's strange that they should be showing, even if you run the superseded uninstaller without all the latest updates installed. What do you mean by '(without restarting!) to remove updates that were no longer required', as that is not a function of the script. The only function that comes close to that in the installer is the removal of non applicable/non applyable updates, which only removes .msu/.cab update files, and not active files on the system. If an update isn't applicable/applyable, it's just that, 'not for your system', and as such is not needed on your system. kb947821-V24 is another possibility of a need to be run. With both the installer and the superseded uninstaller run properly, these shouldn't be showing (not sure if McRip has all the required updates to hide WU updates in most cases). I hope that wasn't too confusing, I didn't know how best to explain it! The showing of updates in Windowsupdate is actually a bit of an annoyance, as many are superseded and even when installed are completely non-functional, except for not showing in WU. The other annoyance is that for the updates which are still applicable, both the GDR and LDR (if present) versions need to be installed even if the LDR version is the only one needed.