Update cannot-create-bootable-media-error-80004005-0x8004101d.md

Author: Simonx Xu

support/mem/configmgr/os-deployment/cannot-create-bootable-media-error-80004005-0x8004101d.md

@@ -1,6 +1,6 @@
 ---
 title: Can't create bootable media with errors 80004005 and 0x8004101d
-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).
+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).
 ms.date: 05/16/2025
 ms.reviewer: kaushika, umaikhan
 ms.custom: sap:Operating Systems Deployment (OSD)\Task Sequence Media (all types)
@@ -11,7 +11,7 @@ _Applies to:_   Configuration Manager (current branch)
 
 ## Symptoms
 
-In Microsoft Configuration Manager (current branch - version 2409), you can't create bootable media and select a cloud management gateway for a management point.
+In Microsoft Configuration Manager (current branch, version 2409), you can't create bootable media when selecting a cloud management gateway for a management point.
 
 The following error is logged in the **SMSProv.log** file:
 
@@ -21,7 +21,7 @@ Failed to get MP installation directory path
 ~*~*~GetTSMediaAdditionalInfo failed due to error 80004005
 ```
 
-The following error is logged in the **CreateTSMedia.log** file:
+Additionally, the following error is logged in the **CreateTSMedia.log** file:
 
 ```output
 Error invoking WMI method SMS_TaskSequencePackage.GetTSMediaAdditionalInfo (0x8004101d)
@@ -30,8 +30,8 @@ StageCertificate::RetrieveTokenForMediaCert() failed. 0x8004101d
 
 ## Cause
 
-This issue occurs because the SMS Provider isn't located in the same location as the management point. In Configuration Manager (current branch - version 2409), the system checks the location of management point and attempts to use the DLLs available in that location.
+This issue occurs because the SMS Provider isn't located in the same location as the management point. In Configuration Manager (current branch, version 2409), the system checks the location of management point and attempts to use the DLLs available in that location.
 
 ## Resolution
 
-Since a management point can't be hosted on a central administration site, you must create the bootable media on a primary site. Additionally, ensure that all Configuration Manager providers are located in the same location as the management point.
+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 located in the same location as the management point.