question

SenhorDolas-2197 avatar image
0 Votes"
SenhorDolas-2197 asked ·

Failed to update boot image after SCCM v2006 update : "File = "..\\sspbootimagepackage.cpp";"

Got the new ADK and PE all installed.

Error in SMSPROV: Failed to copy file '\\SCCM-Server\SMS_CSF\OSD\\bin\x64\ccmcore.dll' to 'C:\WINDOWS\TEMP\BootImages{5A21EF4D-9AFE-493E-AD98-D60123456D54}\mount\sms\bin\x64\ccmcore.dll'

Full error:

Error: The wizard detected the following problems when updating the boot image.

• Failed to insert OSD binaries into the mounted WIM file

The SMS Provider reported an error.: ConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

• Description = "Failed to inject OSD binaries into mounted WIM file (often happens if unsigned drivers are inserted into x64 boot image)";

• ErrorCode = 2152205056;

• File = "..\\sspbootimagepackage.cpp";

• Line = 5482;

• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";

• Operation = "ExecMethod";

• ParameterInfo = "SMS_BootImagePackage.PackageID=\"CSF00005\"";

• ProviderName = "WinMgmt";

• StatusCode = 2147749889;

Little help here cos I am googled out....

Thanks

windows-10-setupmem-cm-generalmem-cm-osd
· 1
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@SenhorDolas-2197

Hope everything goes well.
May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

0 Votes 0 · ·
FionaYan-MSFT avatar image
1 Vote"
FionaYan-MSFT answered ·

@SenhorDolas-2197

  1. May we know that the versions of ADK and PE are the newest like version 2004?

  2. For our"Failed to insert OSD binaries into the mounted WIM file":
    (1) Maybe we could try to delete the boot Images folders manually.
    (2) Use the dism to check if the mounted WIM's exist on the machine.
    (3) Run the Update Distribution Points and it should be completed successfully.
    Please refer to this article to get more details:
    failed to inject osd binaries into mounted WIM file ErrorCode = 2152205056
    Note:This article is not an official Microsoft article.

Hope this could help you.


If the response is helpful, please click "Accept Answer" and upvote it.


· 4 · Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@FionaYan

I have installed the latest version of ADK and PE and rebooted in between.
I also found that solution yesterday and yes I had an old old capture image mounted which I discarded but still I have the issue.
There are no mounted images that I can see (using dism command)
I did find this on the dism log which I am not sure how to fix:

 Failed moving directory: \\?\C:\WINDOWS\TEMP\BootImages\{00D31BA4-CB47-44E3-9AC9-135EF27536AE}\mount\Windows\CbsTemp\20240_51813140\ to temp, will delete in-place instead [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]

Not sure what could be causing this?

0 Votes 0 · ·

@SenhorDolas-2197

For better support, could we provide some related screenshots to see which steps we are pending ?

Have a nice day!

0 Votes 0 · ·

@SenhorDolas-2197

Just checking in to see if there is any update. We haven't heard from you for a few days and would like to know the current status of the problem. Is the problem solved? Do you need any further assistance? Look forward to hearing from you.

0 Votes 0 · ·

@FionaYan

Still the same issue - I can't even import a wim image as I get the same error...

anything you can do to escalte internally?

0 Votes 0 · ·
FionaYan-MSFT avatar image
0 Votes"
FionaYan-MSFT answered ·

@SenhorDolas-2197

Could we try to create a custom boot image by using MDT?
1. If the boot image could be created successfully,maybe we need to uninstall and reinstall our ADK.
2. If the boot image could not be created successfully,maybe our SCCM environment and then we could get the further step.
Here are some useful article for you to refer to:
create a custom windows pe boot image with configuration manager
how to create boot image using mdt for sccm

Hope this could help you.


If the response is helpful, please click "Accept Answer" and upvote it.



· 3 · Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@SenhorDolas-2197

May we know the current status of the question? If there is any chance to try above suggestion? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

Have a nice day!

1 Vote 1 · ·

@FionaYan

We have this resolved. The issue was permission on the \OSD folder.
For some odd reason System was missing from the folders NTFS permissions.
Not sure if this was because of the updates or not.
Now we can import the boot image and reload with the ADK and new sccm client.

Thank you so much for your help with this case.

1 Vote 1 · ·

@SenhorDolas-2197

Thanks for sharing your experience and solution here. We believe this will be very beneficial for other community members who have similar questions.

0 Votes 0 · ·
KeithNail-2538 avatar image
1 Vote"
KeithNail-2538 answered ·

Few things to consider,

Ensure you have removed all extra Drivers before updating using the Reload box.

Also have you restarted the server since the upgrade of ADK / WinPE Add-on?

· Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

StefanGustafsson-9374 avatar image
1 Vote"
StefanGustafsson-9374 answered ·

I was able to resolve my issue with error by deleting this folder C:\Windows\Temp\BootImages

· Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MarkAG-3984 avatar image
1 Vote"
MarkAG-3984 answered ·

Mine was only the MDT boot image, all others updated fine. I was able to fix it by creating a new boot image from the same MDT source file, then once the new one was created I tried updating the failing one and it was successful.

· Share
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.