Configuration Manager OSD task sequence fails with error code 0x80004005

When deploying operating systems with Configuration Manager (SCCM/ConfigMgr), administrators may encounter the dreaded error code 0x80004005. This generic failure can be particularly frustrating because it doesn’t point to a single root cause—it often arises from issues such as missing drivers, boundary misconfigurations, or network connectivity problems during the task sequence. Understanding how to interpret log files like smsts.log and systematically narrowing down potential causes is key to resolving this error and ensuring smooth OS deployment across your environment.

You may encounter the following error during OSD.

An error occurred while retrieving policy for this computer (0x80004005). For more information, please contact your system administrator or helpdesk operator.

As mentioned above, the error code 0x80004005 is a generic error code, which means Access Denied. There may be a number of reasons behind this, and you should analyze smsts.logto understand the exact reason behind this error code.

Time Sync Issue

Error in smsts.log

SyncTimeWithMP() failed. 80072ee7.TSMBootstrap 25-4-2018 18:02:191501 (0x0580)
Failed to get time information from MP: MPServerName

If you see the above errors in smsts.log then it can be related to a time sync issue

Check the date and time on the client machine BIOS. You can press F8 in the Windows PE screen to open a command prompt and validate the date and time from the command line. In case of a time issue, correct the time and retry the Task sequence.

DNS Issue

Error in smsts.log

unknown host (gethostbyname failed)

sending with winhttp failed; 80072ee7

Failed to get client identity (80072ee7)

The above error indicates DNS-related issues. You can launch the command prompt by pressing F8 and validate the following things.

• Check if an IP address has been assigned to the machine by the DHCP server.
• Check if you can ping the Management Point using the Management Point server FQDN.

If you have used Dynamic media while creating the USB boot disk, then try Site-based media and select the management point client reporting to.

The self-signed certificate has expired

The above issue also happens due to expired self-signed certificates. Follow the steps below to check the self-signed certificate expiry date.

• Open the Configuration Manager console
• Navigate to \Administration\Overview\Site Configuration\Servers and Site System Roles
• Select the Site System in the top right pane
• Right-click on Distribution Point in the bottom right pane and select Properties
• In the Distribution Point Properties windows, go to the Communication tab and validate the Self-signed certificate date.

Related Posts:

• SCCM Application Deployment Failed with Error 0x87d01106 | ConfigMgr
• SCCM Client Installation Failed With Error Code 0x87d00215
• PXE-E99: Unexpected network error – SCCM OSD
• Configuration Manager OSD task sequence fails with error code 0x80004005
• MECM OSD Task Sequence Failed with Error 0x80072EE7
• SCCM Client Push Installation Failed with Error 0x800706ba
• Failed to Add Update Source for WUAgent of type (2) and id ({ID). Error = 0x80004005
• SCCM OSD – Domain Join Failed with Error code 0x54b on HP Elitebook 840 G8
• ccmsetup failed with error code 0x87d00227
• Fix Application Deployment error 0x87d00213 in ConfigMgr
• CMG Connection Point Status Disconnected | SCCM | ConfigMgr
• CMG Setup – Subscription ID drop down not populating
• CMG Setup – Error when granting Contributor permission to the Azure AD app
• Failed to connect with DP – Error Code 0x8004100e | ConfigMgr | SCCM
• SCCM Client Installation Failed with error 0x87d0027e
• ConfigMgr OSD – PXE Troubleshooting
• SCCM WSUS sync error – Sync Failed – WSUS server not configured
• SCCM Software Distribution Troubleshooting