Fix Task Sequence Error 0x80004005 in ConfigMgr

Task sequence error 0x80004005 in Configuration Manager (ConfigMgr) is a generic failure that usually means the operating system deployment (OSD) step couldn’t complete due to a permissions issue, network problem, or a missing configuration. This guide walks you through the most common causes and fixes, from checking logs to adjusting deployment settings, so you can get your task sequence running again.

What You’ll Need

Access to the Configuration Manager console (usually as an administrator)
Permissions to modify task sequences and deployment settings
Access to the site server’s logs (or the client’s logs if available)
The task sequence media or boot image used for the deployment

Step-by-Step

Identify the exact failing step. The error 0x80004005 is generic, so you need to find which step in the task sequence failed. Open the smsts.log file (located in %temp%\smstslog on the client, or X:\Windows\Temp\SMSTSLog during WinPE). Search for the last error code or the step name that appears just before the failure.
Check the deployment’s access settings. In the Configuration Manager console, go to Software Library > Operating Systems > Task Sequences. Right-click your task sequence and select Properties. Go to the Advanced tab and ensure that “Allow this task sequence to be run without network access” is set appropriately. If your task sequence needs to access content from the distribution point, that option should be unchecked. Also, verify that the deployment’s Deployment Settings allow the task sequence to run on the target collection.
Verify the boot image and distribution point. If the failure occurs during the “Apply Operating System Image” or “Apply Driver Package” step, the boot image or the content might be corrupted or not fully distributed. In the console, go to Monitoring > Distribution Status > Content Status. Find your boot image and task sequence content, and check that all distribution points have a status of “Success”. If not, redistribute the content.
Check the network access account. If the task sequence needs to access network shares (e.g., to copy files or run scripts), the Network Access Account must be set correctly. Go to Administration > Distribution Points, right-click your distribution point, select Properties, and go to the General tab. Ensure the network access account is specified and has the correct permissions on the share.
Examine the smsts.log for specific error details. The log often shows a more specific error before the generic 0x80004005. Look for lines like “Failed to get client certificate” or “Access denied”. Use that to narrow down the issue. For example, if it’s a certificate issue, check the boot image’s certificate settings.
Reset the task sequence cache. Sometimes stale cache can cause failures. On the client machine, stop the Microsoft Management Agent (SMS Agent Host) service, delete the contents of C:\Windows\System32\ccmcache, and restart the service. Then retry the task sequence.
Try a different boot image or media. If you’re using PXE or boot media, the boot image might be outdated or corrupted. Create a new boot image or update the existing one, and ensure it’s distributed to all distribution points. Also, if you’re using USB media, recreate it with the latest media creation tool.
Check for antivirus or firewall interference. On the client, temporarily disable any third-party antivirus or firewall that might be blocking the task sequence from accessing the network or writing files. If the issue resolves, add exceptions for the ConfigMgr client and the task sequence process.
Verify the task sequence variables. If your task sequence uses custom variables, ensure they are set correctly. A missing or misnamed variable can cause a step to fail. Check the task sequence’s Variables tab and any collection or device variables that might override them.
Update the Configuration Manager client. If the client is outdated, it might not support certain task sequence features. Update the client to the latest version that matches your site version.

Common Mistakes

Ignoring the smsts.log – The generic error code is useless without the log. Always check the log first.
Not checking distribution point status – Content that hasn’t been distributed or is pending will cause failures.
Using a network access account with insufficient permissions – The account needs read access to the content share.
Forgetting to update boot images after a task sequence change – Boot images are separate from task sequences; they need to be updated if you change the task sequence or its content.
Assuming it’s a network issue – While network problems are common, the error can also be due to local file system issues or permissions on the client.

Tips

Always use the latest boot image – Make sure your boot image includes the latest drivers and updates, especially for new hardware.
Test with a simple task sequence – Create a minimal task sequence that just applies an image and runs a command to isolate the issue.
Enable verbose logging – In the task sequence, add a step to set the SMSTSLogLevel variable to 1 for more detailed logs.
Use the Task Sequence Debugger – ConfigMgr has a built-in debugger that lets you step through the task sequence to see exactly where it fails.
Keep your site updated – Microsoft regularly releases hotfixes for OSD issues. Ensure you have the latest update rollup installed.

Troubleshooting

If the steps above don’t resolve the issue, try the following:

Check the execmgr.log – This log shows the task sequence execution status and might give more details.
Verify the client’s time zone – A mismatched time zone between the client and the site server can cause certificate and authentication failures.
Test with a different client – If possible, try the task sequence on a known-good machine to determine if it’s a hardware-specific issue.
Review the site server’s logs – Check the MP_Location.log and MP_ClientIDManager.log for any errors related to client registration or location requests.
Use the Configuration Manager Support Center – This tool can collect logs and diagnostics that can be sent to Microsoft support if needed.

Frequently Asked Questions

What does error 0x80004005 mean in task sequences?

It’s a generic error meaning “Unspecified error”. It’s not specific to ConfigMgr; it’s a Windows error that indicates a failure at a low level. You need to look at the smsts.log to find the actual cause.

Why does the task sequence fail only on some computers?

This usually points to a hardware or driver issue. The boot image might be missing drivers for that specific model, or the machine has a different storage controller that isn’t recognized.

Can a firewall block the task sequence?

Yes, if the client can’t reach the distribution point or the management point, the task sequence will fail. Ensure that the necessary ports (typically 80/443) are open for the ConfigMgr client.

How do I find the exact step that failed?

Open the smsts.log and look for the last step that started before the error. The log will show the step name and the time it failed. You can also use the Task Sequence Debugger to step through and see the failure in real time.

Is there a way to skip a failing step?

Yes, you can set the step’s “Continue on error” option to true. However, this is not recommended as it can lead to a broken OS deployment. It’s better to fix the root cause.

Does the error occur during PXE boot or after the OS is applied?

If it occurs during PXE boot, it’s likely a boot image or network issue. If it occurs after the OS is applied, it’s more likely a driver or configuration issue within the task sequence.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →