Skip to content

Commit 1fc0fee

Browse files
author
Simonx Xu
authored
Merge pull request #8936 from simonxjx/simon-3
AB#5865: CreateTsMedia (for a bootable media for CMG) fails
2 parents 402640f + 9e7d15a commit 1fc0fee

File tree

2 files changed

+43
-0
lines changed

2 files changed

+43
-0
lines changed
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
title: Can't Create Bootable Media with Errors 80004005 and 0x8004101d
3+
description: Fixes an issue in which you can't create bootable media with errors 80004005 and 0x8004101d in Microsoft Configuration Manager (current branch, version 2409).
4+
ms.date: 05/20/2025
5+
ms.reviewer: kaushika, umaikhan
6+
ms.custom: sap:Operating Systems Deployment (OSD)\Task Sequence Media (all types)
7+
---
8+
# Can't create bootable media with errors 80004005 and 0x8004101d
9+
10+
_Applies to:_   Configuration Manager (current branch, version 2409)
11+
12+
## Symptoms
13+
14+
In Microsoft Configuration Manager (current branch, version 2409), you can't create bootable media when selecting a cloud management gateway for a management point.
15+
16+
The following error is logged in the **SMSProv.log** file:
17+
18+
```output
19+
Failed to get MP installation directory path
20+
~*~*~D:\dbs\sh\cmgm\1213_044837_0\cmd\1b\src\SiteServer\SDK_Provider\SMSProv\ssptspackage.cpp(3101) : GetTSMediaAdditionalInfo failed due to error 80004005
21+
~*~*~GetTSMediaAdditionalInfo failed due to error 80004005
22+
```
23+
24+
Additionally, the following error is logged in the **CreateTSMedia.log** file:
25+
26+
```output
27+
Error invoking WMI method SMS_TaskSequencePackage.GetTSMediaAdditionalInfo (0x8004101d)
28+
StageCertificate::RetrieveTokenForMediaCert() failed. 0x8004101d
29+
```
30+
31+
## Cause
32+
33+
This issue occurs because the SMS provider isn't in the same location as the management point. In Configuration Manager (current branch, version 2409), the system checks the location of the management point and attempts to use the DLLs available in that location.
34+
35+
## Workaround
36+
37+
Since a management point can't be hosted on a central administration site, you need to create the bootable media on a primary site. Additionally, ensure that all Configuration Manager providers are in the same location as the management point.
38+
39+
## Status
40+
41+
Microsoft is working on a resolution and will update this article when it's available.

support/mem/configmgr/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -251,6 +251,8 @@ items:
251251
href: os-deployment/in-place-upgrade-task-sequence-not-continue.md
252252
- name: Apply Driver Package task fails with error 80070057
253253
href: os-deployment/apply-driver-package-task-error-80070057.md
254+
- name: Can't create bootable media with errors 80004005 and 0x8004101d
255+
href: os-deployment/cannot-create-bootable-media-error-80004005-0x8004101d.md
254256
- name: Computer hangs during an OSD task sequence in debug mode
255257
href: os-deployment/computer-hangs-task-sequence-debug-mode.md
256258
- name: Dynamic Media can't get management point locations

0 commit comments

Comments
 (0)