SCCM (now Microsoft Configuration Manager) error 0x80070032 during operating-system deployment usually means WinPE cannot use the destination volume as a valid file system. The target may be offline, unformatted, corrupt, encrypted, or missing the NTFS volume that Configuration Manager needs to copy its WinPE files to C:.
Start with SMSTS.log and identify the exact task-sequence step before changing partitions. Inspecting the disk and bringing it online is normally safer than recreating or formatting it; those destructive actions should be used only when the deployment design authorizes erasing the device.
As an Amazon Associate I earn from qualifying purchases.
What error 0x80070032 means in SCCM
In the operating-system-deployment scenario, 0x80070032 is a symptom rather than a complete diagnosis. Microsoft’s System Center troubleshooting guidance associates “Failed to run task-sequence 0x80070032” with the absence of a valid file system: the target can be corrupt, encrypted, unformatted, or otherwise inaccessible. A disk that has gone offline can produce the same result.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The task sequence must be able to copy WinPE files to C:. That prerequisite requires an NTFS partition. If the sequence reaches a storage-preparation step and the intended volume is unavailable or has another file-system state, the generic error is returned even though the underlying cause differs.
#1 Best Overall
The same code can occur at different points in a sequence. A failure in preinstallation storage preparation calls for a different remedy from a later failure caused by WinPE networking or a task-sequence condition. The step name and the log entries immediately before the error are therefore more useful than the hexadecimal code alone.
First, preserve evidence and assess data-loss risk
Before using DiskPart, decide whether the device is meant to be wiped. Partition recreation and formatting can permanently remove an existing Windows installation, recovery partition, user files, or a deployment-specific layout. If the computer contains data that must be retained, stop at inspection and involve the deployment owner or data-recovery process.
Record the following while the failure is visible:
- Whether the sequence was started from PXE, boot media, or an already installed Configuration Manager client.
- The exact task-sequence step and the action immediately preceding the error.
- The disk number selected by the deployment, the firmware mode (UEFI or legacy), and the intended partition layout.
- Whether the target volume is encrypted and how the sequence is designed to handle that encryption.
- Whether the failure affects one device or multiple devices using the same boot image or task sequence.
This information prevents a common mistake: cleaning the wrong disk because the number shown in WinPE differs from the number an administrator expected.
Read SMSTS.log before changing the disk
Configuration Manager records task-sequence activity in SMSTS.log. Microsoft documents CMTrace, OneTrace, and Support Center as suitable viewers for Configuration Manager logs. Open the log from the failing environment and inspect the error together with the preceding entries, the step name, disk-selection messages, and any network or encryption messages.
What to look for
- Storage wording: messages about formatting, partition selection, copying files to
C:, a missing volume, or an inaccessible file system point toward the target disk. - Offline or inaccessible disk: entries showing that the selected disk or volume cannot be opened support an online-state problem.
- Encryption: messages indicating that the volume is locked or unavailable mean that the sequence’s encryption handling must be checked before formatting.
- Network activity: failures connecting to a management point, distribution point, or other task-sequence service suggest WinPE networking rather than a bad file system.
- Step context: the same HRESULT at a different step may have a different cause, so do not apply a storage fix solely because the code matches.
Save a copy of the relevant log section before retrying. A successful retry can overwrite the most useful evidence from the failed run.
Rank #2
Inspect the target disk in WinPE
Use a command prompt in the WinPE environment and inspect the disk without making changes first. DiskPart’s output is authoritative for what WinPE can currently see; it may differ from the layout shown by the installed operating system.
- Start DiskPart and list all disks.
- Select the disk that the task sequence is intended to deploy to.
- Display detailed disk information, including whether it is online and whether it is read-only.
- List volumes and inspect the intended Windows volume.
- Confirm that the volume has the expected drive letter, size, partition type, and file system.
diskpart
list disk
select disk <disk-number>
detail disk
list volume
select volume <volume-number>
detail volume
exitReplace the angle-bracketed values with the numbers displayed on that device. Do not assume that disk 0 is always the correct target. If the expected disk is absent from list disk, the issue is below the task sequence—such as storage-controller visibility or firmware configuration—and formatting commands will not solve it.
Recommended Free Tools
Fix an offline disk without erasing it
If detail disk shows that the intended disk is offline, bring it online and inspect it again:
diskpart
list disk
select disk <disk-number>
online disk
detail disk
list volume
exitUse this only after verifying the disk number. An online disk can still contain a corrupt, encrypted, or unformatted volume, so rerun the volume inspection and review SMSTS.log after the state changes. If the disk repeatedly goes offline, investigate the hardware, storage-controller mode, firmware, cabling, or a policy that is taking the disk offline rather than repeatedly rerunning the sequence.
Repair an invalid or missing NTFS volume
If the deployment is authorized to erase the target and the inspection confirms that the required Windows volume is absent, corrupt, or unformatted, recreate the partition layout defined by the task sequence. The exact layout depends on firmware mode and the organization’s design; do not substitute a generic layout for a sequence that expects separate system, recovery, or data partitions.
Recreate partitions with DiskPart
The following is an illustrative destructive workflow. It removes the selected disk’s partition information. Confirm the disk number, backup requirements, firmware mode, and approved layout first.
diskpart
list disk
select disk <disk-number> rem verify this number before continuing
clean
convert gpt rem use only when the deployment requires GPT/UEFI
create partition primary
format fs=ntfs quick
assign letter=C
exitUse convert mbr instead of convert gpt only when the approved deployment requires an MBR/legacy layout. If the task sequence itself creates partitions, you may need to clean the disk and allow that sequence step to recreate its designed layout rather than manually creating a single partition.
Quick-format an existing C: volume
When the correct partition already exists and the deployment specifically permits formatting it, Microsoft’s troubleshooting example uses:
echo y | format c: /qA quick format removes the file-system structure and makes existing files inaccessible; it is not a data-preserving repair. If the volume contains required data, do not run it. After formatting, verify that the volume is NTFS, assigned the expected letter, and visible in WinPE before rerunning the sequence.
Check encryption and volume access
An encrypted or locked target can look like an invalid file system to the task sequence. Confirm which encryption state the deployment expects at this stage: for example, whether the volume should be unlocked, temporarily decrypted, or intentionally replaced. Check that WinPE has the access required by the sequence and that a protection policy is not relocking the disk during startup.
Rank #4
Do not use clean or format as a way to bypass encryption unless wiping that device is explicitly approved. If the log identifies an encrypted volume but the sequence is supposed to preserve it, correct the encryption-handling step or credentials instead of destroying the partition.
Rule out WinPE networking when the log points there
Storage preparation is the most common interpretation of this error in this scenario, but Microsoft’s guidance also notes that network failures can prevent task-sequence communication. When SMSTS.log shows that the disk is usable and the failure occurs while contacting Configuration Manager infrastructure, test WinPE networking instead of repartitioning.
- Check the cable or wireless deployment method and confirm that the device is connected to the expected VLAN and subnet.
- Verify that the WinPE session received the network configuration required to reach the management and content locations.
- Add the correct Windows network drivers to the WinPE boot image when the adapter is not detected or cannot communicate.
- Update the boot image distribution used by PXE or boot media after changing its driver content, then test the updated image on a small set of devices.
A network-driver change is a boot-image or infrastructure change, not a per-device disk repair. Keep the original image available so you can roll back if another deployment begins failing.
Use the task-sequence debugger to isolate the failing step
Current-branch Configuration Manager includes a task-sequence debugger. Deploy the sequence in debug mode to a small test collection and step through execution until the exact action that produces 0x80070032 is identified. The TSDebugOnError variable can start debugging automatically when an error occurs.
Free tools Windows power users keep installed
One-click scans. No signup required.
Debugging is particularly useful when the log shows a valid disk but the sequence is selecting the wrong volume, applying an unexpected partition rule, or failing only after a conditional step. Change one condition at a time, record the result, and avoid testing a destructive partition action on production devices.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose the least destructive remedy
| Observed condition | First action | Data-loss risk | Scope of change |
|---|---|---|---|
| Disk is offline | Verify the disk number and use DiskPart to bring it online | Low if only the online state is changed | Single device |
| Expected NTFS volume exists and is readable | Correct the task-sequence disk or volume selection and debug the failing step | Low | Task sequence or device selection |
| Volume is encrypted or locked | Apply the deployment’s intended encryption-handling process | Variable; avoid formatting unless wiping is approved | Device and encryption policy |
| Volume is unformatted or corrupt and the device may be erased | Recreate the approved partition layout or quick-format the required NTFS volume | High; existing data can be destroyed | Single device or deployment design |
| Disk is usable but communication fails in WinPE | Check VLAN/subnet and add the correct network drivers to the boot image | Low for the device; image changes affect future deployments | Boot image and network environment |
How the fix differs by deployment stage
PXE deployment
Capture the PXE boot image and the task-sequence step where the error appears. If the disk is visible but the sequence cannot contact Configuration Manager, prioritize the WinPE network adapter, VLAN, subnet, and boot-image driver checks. If the disk is offline or lacks NTFS, follow the storage inspection path.
Boot-media deployment
Use the same DiskPart and log checks, but verify that the boot media contains the current boot image and required drivers. A stale or incomplete image can make a device’s storage or network hardware appear unsupported even though the task sequence is correct on another medium.
Installed-client execution
When the sequence starts from an existing Windows client, preserve the client log and determine whether the failure occurs during a reboot into WinPE. The destination disk may still be encrypted or occupied by the existing installation; do not format it until the wipe-and-reinstall intent is confirmed.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Retry and verify the deployment
- Correct only the condition identified by the log and inspection.
- Close the command prompt or reboot WinPE if required so the new disk state is visible to the task sequence.
- Start the sequence again on the test device or approved collection.
- Confirm that the partition step creates or finds the intended NTFS volume and that WinPE files can be copied to
C:. - Watch the next several steps rather than stopping after the original error disappears; a wrong partition layout can cause a later boot or recovery failure.
- Save the new
SMSTS.logif the retry fails and compare the first failure’s context with the second run.
A blind rerun does not repair an offline disk, unlock an encrypted volume, create an NTFS partition, or add a missing WinPE driver. Retry only after the relevant state or configuration has changed.
Preventing repeat 0x80070032 failures
- Document the intended disk number, firmware mode, partition layout, and encryption state for each deployment design.
- Make the task sequence’s partition and format steps explicit, with separate test and production versions where possible.
- Keep WinPE storage and network drivers current for the hardware models you deploy.
- Test PXE and boot media independently; they may use different boot images or driver sets.
- Use a small collection and the task-sequence debugger when changing conditions, disk variables, or boot-image content.
- Train operators to inspect
SMSTS.logbefore running destructive DiskPart commands.
Optional shortcut
As an optional shortcut after you have identified the Windows-side condition, Outbyte PC Repair can address some common Windows issues, including broken system elements, invalid redirects, shared DLL files, settings that contribute to CPU, RAM or disk load, temporary and cache files, privacy warnings, vulnerability checks, and app-crash logging. It complements antivirus software rather than replacing it, results vary, and it cannot repair every SCCM task-sequence failure. It runs on Windows 11, 10, 8 and 7, with a category-based free trial of at least two days followed by a paid subscription.
Bottom line
For SCCM 0x80070032, read SMSTS.log first, then verify that the intended disk is online and exposes the NTFS volume required for WinPE files on C:. Correct encryption or WinPE networking when the log identifies those causes. Recreate partitions or format only on an approved wipe-and-reinstall device, and use the current-branch task-sequence debugger when the failing step is still unclear.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
