Forum Discussion

dpsmith336's avatar
dpsmith336
Copper Contributor
Feb 04, 2021

Add Operating System Upgrade Package error with CM 2006

I'm running into an issue when attempting to create an Operating System Upgrade Package using the Add Operating System Upgrade Package Wizard. The wizard fails with the following error:

 

• Description = "Failed to rename the file due to error 5";
• ErrorCode = 5;
• File = "..\\sspbootimagepackage.cpp";
• Line = 4941;
• ObjectInfo = "CSspBootImagePackage::ConvertToSingleIndexImage";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;

 

Since "ErrorCode = 5" corresponds with Access Denied, I have reviewed both NTFS and share permissions for the path containing the operating system files, even going as far as granting Everyone Full Control on both NTFS and share permissions and I continue to receive the error.

 

SMSProv.log indicates a failure to overwrite install.wim with the extracted WIM that DISM creates as part of the wizard as shown below:

 

  • Failed to move the file \\MECMServer\OS_Images\Upgrades\sources\{B0959BD1-16BF-4221-A6DB-826244208136}.wim to \\MECMServer\OS_Images\Upgrades\sources\install.wim due to error 5.
  • *~*~..\sspbootimagepackage.cpp(4941) : Failed to rename the file due to error 5~*~*
  • *~*~Failed to rename the file due to error 5 ~*~*

 

A Procmon capture indicates Access Denied with the following, even though DISM can successfully extract the specified index from the WIM file and write back to the path containing the source WIM file:

 

The DISM command that the wizard executes is below:

  • '"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Export-Image /SourceImageFile:"\\MECMServer\OS_Images\Upgrades\sources\install.wim" /SourceIndex:3 /DestinationImageFile:"\\MECMServer\OS_Images\Upgrades\sources\{B0959BD1-16BF-4221-A6DB-826244208136}.wim"'

I suspect that the overwriting of install.wim fails because DISM hasn't released its hold on install.wim before the overwrite is attempted.

 

Any help will be greatly appreciated. Thank you.

4 Replies

No RepliesBe the first to reply

Resources