Fix SCCM Task Sequence Error 0x80070032

This article aims to provide a solution to fix SCCM Task Sequence Error 0x80070032. Error code 0x80070032 is a common issue that occurs during the SCCM OSD.

A task sequence deployment could fail due to several reasons. Whenever a ConfigMgr task sequence fails, it displays an error code. This error code and the smsts.log file are important for troubleshooting the issue.

Knowing the error code isn’t enough, you also need to translate the SCCM error code to error message. Luckily, ConfigMgr error lookup tools will help you to convert the error codes to messages.

When you use any of the error lookup tools to translate the error 0x80070032 or error 80070032, the output is “The request is not supported“. Not all error codes can be translated with error lookup tools.

Don’t worry, the solution provided in this article should help you to resolve the task sequence error 0x80070032. If you find something else worked for you, let me know in the comments section.

Fix SCCM Task Sequence Error 0x80070032

The SCCM task sequence error 0x80070032 occurs when the task sequence fails to detect a valid NTFS drive. If the drive is Bitlocker enabled, the task sequence considers this drive as unsupported and results in error code 0x80070032.

The error 0x80070032 appears during the failed to stage WinPE Code(0x80070032). The task sequence halts and doesn’t go any further. Let’s understand why the task sequence fails with error 0x80070032 and the solution for it.

Explanation: Consider a laptop that has been previously imaged using a task sequence and the C: drive is encrypted and Bitlocker enabled. When you attempt to re-image this same laptop, the task sequence fails to stage WinPE on the machine as the C: drive has an unsupported file system. Thus, it marks the device as “unsupported” and therefore unavailable to WinPE.

“The active system partition on a MBR system must be NTFS” – This error might occur when you try to install an operating system on an entirely new desktop or laptop. Most hardware suppliers provide a pre-installation environment to install the OS. However, this pre-installation environment is present on a non-NTFS file system.

To find the error 0x80070032 details, you must first locate the smsts.log file and review it. The location of SMSTS.log file changes during the operating system deployment. So ensure you grab the log file from the correct location.

Navigate to the X:\WINDOWS\TEMP\SMSTSLog directory, copy smsts.log to a USB device or network share.

Read: How to copy SMSTS.log during task sequence failure

To review the smsts.log, you can either use CMTrace log viewer tool or other ConfigMgr log file viewers. Open smsts.log and scroll to the end of the file where you’ll see lines similar to the following:

The active system partition on a MBR system must be NTFS
Failed to prepare the system partition for staging.
The request is not supported. (Error: 80070032; Source: Windows)
Failed to stage WinPE.
Code(0x80070032) ThreadToResolveAndExecuteTaskSequence failed. Code(0x80070032)

Now that you know the issue is not with the task sequence but with the drive itself, you can use Disk part Commands to clean the drives. DiskPart commands help you to manage your PCs drives (disks, partitions, volumes, or virtual hard disks)

Read: Fix Task sequence has failed with the error code 0x800700A1

To resolve error 0x80070032, perform the following steps.

• Wait for the task sequence to fail with the error 0x80070032.
• Press F8 on the machine that failed to build to open a Command Prompt.
• Type diskpart
• Type select disk
• Type clean
• Type exit to close the Command Prompt
• Click Finish on the Task Sequence Wizard screen to reboot the machine and build it as normal.

Here is a nice guide on how to use DiskPart commands for SCCM OSD Troubleshooting.