Install KB2910552 hotfix for ConfigMgr 2012 R2 client during OSD

Microsoft has released a new hotfix that solves some problems that was discovered in ConfigMgr 2012 R2. One of them is the infamous slow download of WIM files during OSD. A specific hotfix for that issue was released earlier, but this new hotfix called KB2910552 includes the same hotfix released earlier and additional fixes. You can read more about this new hotfix here. As I’ve already stated, this new hotfix replaces the hotfix called KB2905002. So if you want to fix the OSD problems in ConfigMgr 2012 R2, the correct hotfix to deploy is KB2910552. This blog post will cover the steps necessary to take in order to install this hotfix for the ConfigMgr client during OSD. The method in this blog post is one that I’ve used for a very long time now and it has proven to be working in any scenario I’ve been using it in. So I highly recommend to install ConfigMgr client hotfixes by using this method.

Installing the KB2910552 hotfix

In this post I’ll not go through the setup wizard of the hotfix itself, but I recommend that you accept to let the wizard create all the packages for you. These packages can be leveraged at a later stage to upgrade clients, stand-alone ConfigMgr consoles and site servers. What we’re interested about going forward, is the actual client msp files (hotfix files) that the hotfix setup puts in a certain location.

Create a hotfix Package

Once you have installed the hotfix, go to the installation location of ConfigMgr. In my lab environment, this is under D:\ConfigMgr. In here there’s a folder called hotfix. Whenever you install a hotfix for ConfigMgr, a subfolder named with the KB article number is created in this location. Open the KB2910552 folder and then the Client folder. In here there’s two folders, each containing a msp file that we’re after. The two files that we’re interested in are placed in the following location:
<ConfigMgr installation location>\hotfix\KB2910552\Client\i386\configmgr2012ac-r2-kb2910552-i386.msp
<ConfigMgr installation location>\hotfix\KB2910552\Client\x64\configmgr2012ac-r2-kb2910552-x64.msp
Now that we know where the files that we need are located, we need to copy these to a folder in the Content Library. In my lab environment, I’ll create a folder that will be used as the source content location for the Package that we’ll be creating. The path to this folder will be:
In this folder, create an i386 and x64 folder and place the correct version of the hotfix files into these folders so that we end up with the following:
1. Open the ConfigMgr console and go to the Software Library node.
2. Expand Application Management, right-click on Packages and select Create Package.
3. Fill in the fields according to the picture below, remember to enter the correct source folder for your environment. Click Next when ready.
4. Select Do not create a program and click Next.
5. On the Summary page, click Next.
6. On the Completion page, click Close.
The package containing the hotfix files has now been created. But before we continue, we need to distribute the package to either our Distribution Points or Distribution Point Groups, depending on how it’s setup. Right-click on the newly created package and select Distribute Content. Complete the wizard before you continue.

Configure the task sequence

We’re now going to edit the task sequence(s) that we use to deploy our desired operating system. First off we’ll create a Run Command Line step that will copy the hotfix file to a local folder. By doing this, we’ll not need to rely on access to certain network shares or worry about credentials and all that. Next we’ll amend the Installation properties field on the Setup Windows and Configuration Manager step, giving it the PATCH parameter pointing to the local hotfix file.
It’s important that you point to the correct version of the hotfix file when you edit the task sequence(s). For example, if you’re deploying Windows 8.1 Enterprise x64 like I’m doing here in this example, you need to configure the steps to reflect the x64 location and file name.
1. Open the task sequence(s) that you use to deploy your operating systems with.
2. Add a new Run Command Line step just above the Setup Windows and Configuration Manager step. Configure it accordingly:
3. Select the Setup Windows and Configuration Manager step and edit the Installation properties field accordingly (add the PATCH parameter):
Note: The path to where the hotfix file is located should be on a single row, in the picture above it looks like it has been split into two rows, but that’s now the case. It should be like the following:


4. Click on OK to save the changes in the task sequence.
The next time that we deploy an operating system by using a task sequence that have these configurations, the ConfigMgr client version should be the following:

Nickolaj Andersen

Chief Technical Architect and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions. Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences such as Microsoft Ignite, NIC Conference and IT/Dev Connections including nordic user groups.


  • Hi,
    How can the speed of the Apply Operating System -step be increased if you apply the Hotfix after that step?
    I know you have to install the OS first before you can install the CM client and apply the patch but this will only fix (increase) the speed of later Application Deployments I assume?

    • Hi Hermke,
      The hotfix has to be applied to your Site servers first. When that has been completed, you should update your boot images to include the hotfix (this is done by updating Distribution Points for the boot images). Now that you’re boot images have been updated, the fix is already included and the task sequence engine will download the image file at normal speed. The patch that you apply in this bost is only for the ConfigMgr client that later will be installed on the machine you’re deploying.

  • Hi, i have installed this hotfix to solve the XP to Windows 8.1 migration, but issue still persists.
    My env is SCCm 2012 R2 and i have installed the hotfix, updated the boot image and completed rest of the steps.
    ANy help would be appreciated.

  • Hi
    You mention that “now we need to copy the files to the content library” in this context what is the content library, something you have defined and created or something mandatorily being created by the sccm install setup. How does the task sequence know the whereabouts of the x64 directory when using the cmd /c copy x64 directory?
    Thanks v much

    • Hi Phil,
      When I refer to the Content Library, it’s in the context of where you’ve stored your content source files. This is something that you manually (or by script) configure when you build a new Primary Site for instance. Since all your Packages, Applications, OSD related data needs their source content to be stored somewhere, I refer to that place as the Content Library.

  • Hi, so I installed this hotfix a while back, and it sped up my “downloading” part of the Apply Operating System task.
    However, for some reason, the “Downloading” part is now back to a crawl, downloading at about 1% every 15 seconds.
    I can’t reinstall the hotfix 2910552 because it says update doesn’t apply.

  • Does it leave behind the C:\Hotfix folder? Wouldn’t you be better of putting them in %deployroot%\Hotfix?

    • Hi Colin,
      Yes it does, but a very simple PowerShell or VBscript can take care of that. The point of this method is to show that you can put it anywhere. If I’m not mistaken, %deployroot% is not in the same location in WinPE and during the online OS, so that would give you problems.

  • Thanks for this! I was getting a task sequence error of 0x80070057 when doing an OSD and it was driving me nuts! Who knew that when you install the update, Microsoft didn’t automatically make these updates for you (or at least update the client so the patch isn’t necessary). Anyway, just thought I’d post my comment with the error so that others out there might find it easier to stumble on your blog like I did.

    • Hi Larry,
      I’m glad that this post helped you with your problem, and thanks for sharing your findings. Community power! 🙂


Categories use cookies to ensure that we give you the best experience on our website.