How to repair SCCM Offline Servicing: Error Failed to apply updates with Schedule Updates

Since SCCM 2012 there is the Schedule Updates option that allows us to update a reference image with KBs that we have previously synchronized in Configuration Manager. But sometimes we may fail to apply an update and because of this fails to disassemble the image.

This will prevent us from continuing to use the Schedule Updates option until we manually remove the image from the Windows Server installed on the Primary Server. Therefore, in this article we are going to see how to fix the Error Failed to apply updates in SCCM.

Error SCCM Offline Servicing

This post is a guide on how to repair SCCM’s Offline Servicing feature so that you can continue injecting updates into images after the “Failed to apply one or more updates” error.

To determine if this is your problem, you can read the OfflineServicingMgr.log. This log will be in the Logs folder within the System Center Configuration Manager installation on your Site Server (Primary Server). The error should look something like this:

Fix SCCM Offline Servicing error

As you can see, the DISM process is not able to disassemble the previous image to which we tried to inject the KBs (possibly because the installation failed). To resolve this issue, we will need to open a CMD with administrator permissions:

And run the following command: dism.exe /cleanup-wim

This command will look for all images that are on all Windows Server partitions (so you don’t need to switch partitions from the CMD).

Then we can see the images mounted with the command: dism.exe /get-MountedWiminfo

And unmount the images with the command: dism.exe /unmount-Wim /MountDir:<mountDir> /commit</mountDir>

Optionally, we can check the folder ConfigMgr_OfflineImageServicing where the image was mounted to make sure it is no longer locked and we can delete it. If you don’t, the next Schedule Updates process will do it automatically.

Check the repaired SCCM Offline Servicing log

Now we will need to re-launch the Schedule Updates on the image and follow the OfflineServicingMgr log.log to verify that you can already mount the new image and apply the updates correctly to the reference image: