I ran into a challenge recently with a customer during what I intended to be a routine SCCM version update. The update process began as expected, with the necessary update package being downloaded from Microsoft and the cab file extracted successfully to its temporary location.

However, the update appeared to be stuck in a loop, never able to perform the prerequisite check and eventually install. Looking into the CMupdate log showed the unpacking of the update was failing with the error:

“CopyFileExW failed for E:\SCCMContentLib\FileLib\C251\xxxxxxxx to \\?\E:\Program Files\Microsoft Configuration Manager\CMUStaging\PACKAGEGUID\redist\DoincInstall.exe
FileCopy Failed: 0x800704c8″

This error code indicated that “the requested operation couldn’t be performed on a file with user-mapped section open.”

To try and troubleshoot the issue the following steps were taken:

  • Disabled AV applications running on the server.
  • Imported update cab from a known working instance of SCCM.
  • Utilizing Process Explorer to identify any processes locking the file.
  • Reviewing system and SCCM logs for clues on recent changes that might have influenced this behavior.
  • Verifying permissions, disk space, and network configurations.
  • Confirming all services running and running under system context.
  • Utilizing the built-in CMUpdateReset tool included with SCCM.
  • Confirming all applicable registry entries exist and are correct.
  • Confirming all applicable tables and database entries exist and are correct.

Even after all that effort the exact cause of the issue was still unclear.

The workaround

With no clear understanding of what was causing the automated process to fail, the workaround of manually copying the update files from the EasySetupPayload directory to the CMUStaging directory was performed using the following steps:

  1. Identify the failing updates GUID in the SCCM console. (This can be done easily by displaying the Package GUID column in the ‘Updates and Servicing’ tab in the SCCM console)
  2. Locate the corresponding update package folder within the EasySetupPayload directory.
  3. Open the folder and copy the entire contents.
  4. Paste them into the corresponding location within the CMUStaging directory, maintaining the intended file structure.
  5. Proceed with the update installation as usual.

Admittedly, whilst this did not fix the root cause of the issue, it did allow the customer to update their SCCM version to a version that is now in support and provide a workaround to future updates.

Published On: March 22nd, 2024 / Categories: ConfigMgr, Notes from the field /

One Comment

  1. Sean Huggans 16 April, 2024 at 4:21 pm - Reply

    Ran into this with the same update ID: D3D0214-F4DC-4664-B6BB-997E381B7C9D

Leave A Comment

Subscribe to Receive the Latest Updates

Get our latest recommendations, advice and offers direct to your inbox.

We won’t share your details – but you can read more in our Privacy Policy.