Task Sequence Error 0x80070490: Fixes That Work

Task sequence failures with error 0x80070490 (HRESULT: 0x80070490) mean Windows could not find the specified file or component during deployment. This error typically appears in System Center Configuration Manager (SCCM) or Microsoft Endpoint Configuration Manager (MECM) when a task sequence tries to access a package, driver, or boot image that is missing or corrupted. The fix usually involves verifying distribution points, refreshing the boot image, or clearing the task sequence cache.

What the Error Means

Error 0x80070490 translates to ERROR_NOT_FOUND in Windows. In the context of task sequences, it indicates that a referenced item—such as a driver package, application, or operating system image—cannot be located. This often happens when the task sequence was updated but the changes were not fully replicated to all distribution points, or when a package was deleted without removing it from the task sequence.

Common Causes

Stale distribution points: The content is not updated on all DPs, so the client cannot download it.
Corrupted boot image: The Windows PE boot image used for the task sequence is damaged or outdated.
Package reference issues: The task sequence points to a package that no longer exists or has been renamed.
Client cache problems: The Configuration Manager client on the target machine has a corrupted cache.
Network or boundary issues: The client cannot reach a distribution point because of network problems or boundary group misconfiguration.

Step-by-Step Fixes

Try these fixes in order. Most cases are resolved by the first two steps.

Verify distribution point status: In the Configuration Manager console, go to Monitoring > Distribution Status > Content Status. Check if the content associated with your task sequence shows any errors. If content is not installed, redistribute it.
Update distribution points: Right-click the affected package, boot image, or driver package and select Update Distribution Points. Wait for the update to complete before retrying the task sequence.
Refresh the boot image: If the error occurs during the “Apply Operating System” step, update the boot image to the latest version and redistribute it. Also ensure the boot image is compatible with the client architecture (x86 vs. x64).
Clear the client cache: On the target machine, open the Configuration Manager control panel (from \<SMS_SERVER>\SMS_CLIENT or via the software center), go to the Cache tab, and delete cached content. Then retry the task sequence.
Check boundary groups: Ensure the client is in a boundary group that has a distribution point assigned. If not, add the client’s subnet or site to the appropriate boundary group.
Recreate the task sequence: As a last resort, create a new task sequence and manually add the steps. This eliminates any hidden corruption in the original sequence.

How to Read the Error Logs

The smsts.log file is your best diagnostic tool. It is located at %TEMP%\SMSTSLog\smsts.log on the client. Look for lines containing “0x80070490” and note the step that failed. The log will show which package or file was being accessed when the error occurred. For example, you might see Failed to find file: D:\_SMSTaskSequence\Packages\ABC00001\script.ps1. That tells you the package ID and the missing file.

Prevention Tips

Always update distribution points after making changes to packages or boot images.
Use a maintenance window for task sequence deployments to avoid conflicts.
Monitor distribution point health regularly using the built-in reports.
Keep the boot image updated with the latest Windows ADK and Configuration Manager version.

Frequently Asked Questions

Does error 0x80070490 affect Windows 10/11 installations?

Yes, it can occur during in-place upgrades or OSD (Operating System Deployment) when the task sequence references a missing driver or package. The fix is the same: ensure all referenced content is available on the distribution points.

Can I ignore this error if the task sequence completes?

No. If the error appears but the task sequence continues, it may be a warning, but the underlying issue (missing file) can cause unpredictable behavior later. Always resolve it.

Why does the error appear only on some computers?

This usually indicates a distribution point issue—some clients are getting content from a DP that has the file, while others are hitting a DP that doesn’t. Verify that all DPs have the latest content.

How long does it take to update distribution points?

It depends on the size of the content and the number of DPs. Small packages take minutes, but large OS images can take hours. Use the Monitoring node to track progress.

Is there a way to avoid this error during deployments?

Use the “Download content locally” option in the task sequence’s deployment settings. This forces the client to download all content before starting, which can bypass some DP issues but increases deployment time.

When to Contact Support

If you have tried all the above and the error persists, check the smsts.log for any other error codes. If you see a different code alongside 0x80070490, search for that specific combination. If you are still stuck, contact Microsoft Support with the log files. They can help identify if the issue is a known bug in your Configuration Manager version.

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 →