failed adding boot image windows MECM

Question

failed adding boot image windows MECM

Anonymous

Hi team, I get the below error when trying to add the boot.wim file. This happening in version 2103. anyone advice? ![132467-boot.png][1] [1]: /api/attachments/132467-boot.png?platform=QnA

3 answers

Your answer

Answer 1

Hi anonymous user,

I have test it in my environment, and it succeed, please refer to the screenshot:

In an environment that has Windows Assessment and Deployment Kit (ADK) installed and up-to-date on the server that hosts the SMS Provider, you can't manage boot images by using Configuration Manager. We could check SMSProv.log, it records WMI provider access to the site database.

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Limitless Technology 39,926

Hi there,

The first step would be to check your remaining disk space. Configuration Manager provides two default boot images: One to support x86 platforms and one to support x64 platforms, so check whether you are using the right architecture. You can check the below link for more info

https://learn.microsoft.com/en-us/mem/configmgr/osd/get-started/manage-boot-images
https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/error-managing-boot-images

Hope this answers all your queries, if not please do repost back.
If an Answer is helpful, please click "Accept Answer" and upvote it : )

Limitless Technology 39,926 Reputation points

2021-09-16T14:39:24.16+00:00

Can you mount a different WIM or happens with all? Is the WIM stored in a UNC? Is there any security software that can block or filter the access to it? Can you access to the UNC manually form the MECM server and the DP?

This could be an issue with the ADK for Mount Images, please reinstall the package with: WimMountAdkSetupAmd64.exe /Install

(default folder: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64 , but can be different)

On the other hand I would recommend taking a look at the SMSProv.log and %WINDOWS%\Logs\DSIM\dism.log for more information.

Answer 3

Anonymous

Hi @Amandayou-MSFT

I am not looking to upload an winPE boot file. I tested it also and it works.

What I want is to upload the Windows 10 boot.wim file.
But then I get the error message like mention.
How could I fix this?

Amandayou-MSFT 11,156 Reputation points

2021-09-24T05:56:18.847+00:00

Hi，

I test it in my environment, and it's the same as yours. The boot.wim of iso could not be used as a boot image in sccm, but only as a winpe.wim inside ADK.

Best regards,
Amanda
Anonymous

2021-10-10T20:44:04.503+00:00

HI @Amandayou-MSFT ,

could you explan to me why I only need to use a iso from ADK?
I am not getting it
Amandayou-MSFT 11,156 Reputation points

2021-10-11T07:48:56.37+00:00

Hi,

Thank you for your asking the question. As far as I know, ConfigMgr utilizes several products for managing/deploying, such as ADK, WDS, Web Server. For boot images, currently, we can extract them from ADK (actually, it is auto-extracted and imported into ConfigMgr when ADK is installed) and customize them.

Regarding the confusion encountered, the .wim extracted from the .iso file is a windows image file, however, it is not a boot image that CofigMgr can recognize, resulting the error we have seen above.

Best regards,
Amanda

Share via

failed adding boot image windows MECM

3 answers

Your answer