Task sequence and OS deployment error codes in Configuration Manager: a quick reference

A failed task sequence leaves you one hex code in a dialog and a long smsts.log. This quick reference lists 44 codes you meet in Configuration Manager OS deployment (OSD), with the official meaning, the usual cause during a deployment and the first thing to check, grouped by where the failure happens.

How to read these codes#

The code appears in three places: the error dialog (Task Sequence: <name> has failed with the error code (0x80091007)), the device's deployment status under Monitoring › Deployments, and smsts.log, where the useful lines are. The log moves between phases; the smsts.log guide lists every location and shows how to keep the device on the error with F8. Read upwards from Failed to run the action: the code on screen is often only the last link in the chain.

• 0x8007xxxx: a Windows (Win32) error in HRESULT form. The last four hex digits are the Win32 code, so 0x80070032 is error 50, ERROR_NOT_SUPPORTED.
• 0x80072EE2 to 0x80072F8F: WinHTTP errors 12002 to 12175, raised when the task sequence talks to a management point or distribution point over HTTP or HTTPS.
• 0x80004xxx: generic COM codes such as E_FAIL; 0x80041xxx are WMI codes; 0x80091007 is a cryptography (hash) error.
• NetSetup.LOG shows Win32 codes without the prefix: 0x54b there is 0x8007054B elsewhere.

The engine's summary line logs the code in decimal, for example The task sequence execution engine failed executing the action (Apply Operating System Image) in the group (Install) with the error code 2148077575. Convert it in PowerShell, or use Tools › Error Lookup in CMTrace:

'0x{0:X8}' -f 2148077575                            # 0x80091007
0x80070032 -band 0xFFFF                              # 50
[ComponentModel.Win32Exception]::new(50).Message     # The request is not supported.

Not covered here: PXE-E codes before Windows PE starts (see PXE boot failures) and Windows Setup codes such as 0xC1900101 from the Upgrade Operating System step (see the feature update error codes and upgrading to Windows 11).

Task sequence engine, policy and content#

Files, paths and disks#

Files and paths#

Disks and storage#

Network, management point and HTTPS#

Network and shares#

HTTP and HTTPS (WinHTTP)#

Domain join (NetSetup.LOG)#

Apply Network Settings only writes the join details; Windows Setup joins later, so read C:\Windows\debug\NetSetup.LOG in the new OS.

How to verify a fix#

• Rerun the deployment on a test device. The device shows Success in Monitoring › Deployments, and the final log has no failed actions:

Select-String -Path 'C:\Windows\CCM\Logs\smsts*.log' -Pattern 'Failed to run the action'
# No output = no step failed

• Content codes: the package shows Success for the device's distribution points under Monitoring › Distribution Status › Content Status.
• Network and HTTPS codes: ipconfig /all, nslookup and the date check pass at the F8 prompt before you restart the sequence.
• Domain join: Test-ComputerSecureChannel returns True and the computer object is in the expected OU.

References#

• System Error Codes (0-499), (1000-1299) and (1300-1699) (Microsoft Learn): the Win32 meanings
• Error Messages (Winhttp.h) (Microsoft Learn): the 0x80072xxx meanings
• An error occurred when loading the task sequence (Microsoft Learn): the MDT task sequence error