We recently discovered an issue that KB2509007 would not install properly if installed at the same time as either KB977203 or KB977384 via the PATCH= option in the "Setup Windows and ConfigMgr" task. We were able to reproduce the issue internally and after some research and investigation, we discovered a fairly easy workaround to the issue. We found that if we installed the affected hotfixes with another hotfix in between, then KB2509007 would install correctly. Since these are popular hotfixes that are frequently installed during a Task Sequence, I wrote up the below article describing the issue and how to work around it.

Note: We are planning to publish the below article as a KB article. If not already available, it should be available soon as KB2673515.


KB2509007 does not install correctly when installed at the same time as KB977203 or KB977384 



When attempting to install KB2509007 along with either KB977203 or KB977384 via the PATCH= option in the "Setup Windows and ConfigMgr" task of an OSD Task Sequence, KB2509007 does not seem to install correctly and the problem described in KB2509007 still occurs.

Attempting to install KB2509007 with either KB977203 or KB977384 via the PATCH= option by using CCMSetup.exe outside of a Task Sequence also produces the same results. However this is not a common scenario as KB2509007 is designed to only fix an issue that occurs during a Task Sequence and therefore is normally not installed outside of a Task Sequence.

Attempting to rerun the KB2509007 hotfix to try and resolve the issue does not fix the problem.



There is a known issue where KB2509007 does not install correctly if either KB977203 or KB977384 are installed at the same time via the PATCH= option of CCMSetup.exe. If KB2509007 is installed at the same time as KB977203 or KB977384, after CCMSetup completes, under the "Components" tab of the ConfigMgr 2007 control panel the "ConfigMgr Software Updates Agent" will show as being updated to version 4.0.6487.2188. However inspecting the DLL that KB2509007 is supposed to replace, Updateshandler.dll, reveals that it has not been replaced and it is at version 4.0.6487.2000 instead of version 4.0.6487.2188.

Please note that KB977203 is rolled into KB977384. This is the reason why the issue occurs when KB2509007 is attempted to be installed with either KB977203 or KB977384.



If another hotfix is installed in between KB977203/KB977384 and KB2509007, and if the hotfixes are installed in the order that they were released, then KB2509007 installs correctly. For example, if KB2263826 (an Asset Intelligence hotfix) is installed in between KB977203/KB977384 and KB2509007, then KB2509007 installs correctly.

An example command line for the "Setup Windows and ConfigMgr" task would be:




where <Package_ID> is the Package ID of the ConfigMgr 2007 client install package. Do not include the brackets (<>) as part of the Package ID. Please note that the KB number (2261172) noted on the MSP file for KB2263826 is different than the actual KB number (2263826) of the article.

The above paths may need to be modified if the Task Sequence cache folder (_SMSTaskSequence) resides on a drive other than C:. The Task Sequence cache folder will usually reside on the drive or partition with the largest amount of free space. It is not recommended to use the variable %_SMSTSMDataPath% as part of the path. This variable initially evaluates while in WinPE and its value can change once the Task Sequence boots into the full OS. This may cause the paths to become invalid.


Frank Rojas
Senior Support Escalation Engineer