The documented Configuration Manager (formerly SCCM) code is 0x80070057, not the extra-zero spelling 0X800070057. Before changing a task sequence, confirm the literal HRESULT in the log. Then identify the phase that failed: partitioning or Apply Operating System, Install Application, or MDT task-sequence editing. Each phase has a different evidence trail and fix.
First confirm which error you have
Microsoft documentation and support material use 0x80070057 (also represented as -2147024809) for the Configuration Manager error commonly described as an invalid parameter. The string 0X800070057 contains an additional zero and is not the spelling established in those references. It may be a transcription error, a search-query variant, or a different value copied from a log. Do not assume the two values are interchangeable: open the log, copy the complete hexadecimal value, and note the action that was running when it appeared.
As an Amazon Associate I earn from qualifying purchases.
Configuration Manager is still often called SCCM in deployment teams. The product name changed, but the task-sequence and client log methods below apply to current on-premises Configuration Manager environments. A generic error dialog is not enough to select a repair; the first failed action in the relevant log is.
Free tools Windows power users keep installed
One-click scans. No signup required.
Find the first failure in the right log
Configuration Manager writes operational information to component-specific logs. Microsoft explains that administrators can use these files to troubleshoot issues that occur during deployment and client operation. Search for the first error in time order, not the last line containing 0x80070057; later messages are often consequences of the original failure.
#1 Best Overall
| Situation | Primary evidence | Typical location or viewer |
|---|---|---|
| Task sequence running on a client | smsts.log |
After the Configuration Manager client is installed, C:WindowsCCMLogssmsts.log |
| Other client components | Component-specific logs | C:WindowsCCMLogs |
| Site-server processing | Site-server component logs | C:Program FilesMicrosoft Configuration ManagerLogs |
| Configuration Manager console | Console logs | The console’s AdminUILog directory |
Open the files with CMTrace, OneTrace, or Support Center Log File Viewer so timestamps, error severity, and adjacent entries are easy to compare. Record the deployment ID, device name, task-sequence step, exact HRESULT, and the first component that reports a failure. This short incident record prevents a partition problem from being misdiagnosed as an application problem.
Use the failure phase to choose a repair
| Failure phase | Where to look first | Scope and risk |
|---|---|---|
| Apply Operating System, formatting, or partitioning | smsts.log and the preceding Format and Partition Disk step |
Usually one task sequence or destination disk; correcting a variable or destination is lower risk than changing site settings |
| Install Application | smsts.log plus content, policy, transfer, location, and management-point logs |
Can be a single client, a package, a boundary/location issue, or a wider site-service problem |
| MDT task-sequence creation or editing | Console behavior and registration of BDD_* WMI classes |
Console/integration change; close all consoles before reinstalling extensions |
Fix Apply Operating System and partition errors
An Apply Operating System failure with 0x80070057 commonly means the destination supplied to the step does not match the disk and partition created earlier. Configuration Manager supports four destination patterns. Open the task sequence and compare the destination selection with the immediately preceding Format and Partition Disk action.
1. Next available formatted partition
This option lets the step select the next partition that is already formatted and suitable for the image. Use it only when the partitioning step reliably produces one unambiguous target. If multiple volumes are created, confirm that the expected one is the next available formatted partition rather than a recovery, system, or data volume.
2. A specific disk and partition
When the destination is specified by disk number and partition number, both values must match the layout created by the format step. A disk-number change caused by an additional drive, storage controller presentation, or a different hardware model can make a previously valid sequence point at the wrong object. Verify the numbers in the task-sequence editor and in smsts.log for the actual device.
3. A specific logical drive letter
If the step targets a drive letter, verify that the letter exists at the moment the operating-system image is applied. Drive letters assigned in one phase can differ after reboot or when WinPE enumerates volumes. Ensure the format step and the apply step use the same intended letter and that no other volume has claimed it.
4. A task-sequence variable containing the destination
For a variable-based destination, inspect the variable name, value, and the conditions that set it. A variable that is empty, misspelled, set only in one hardware branch, or overwritten by another step can produce an invalid-parameter result. Check both BIOS and UEFI branches and make sure the branch that actually runs sets the destination before Apply Operating System.
Validate the complete partition chain
- In the task-sequence editor, identify the Format and Partition Disk step immediately before the failure.
- Write down the disk number, partition numbers, drive letters, and any destination variable that step creates.
- Open the Apply Operating System action and compare its destination mode with those values.
- Check conditions for UEFI and BIOS groups. The active firmware branch must create and target the same style of layout.
- Review
smsts.logaround the first partitioning or image-application error to confirm which value the task sequence actually resolved. - Correct only the mismatched destination, then test on a representative device before changing a production sequence.
Do not erase additional disks merely to make the sequence proceed. A destination correction should be based on the logged disk and partition information; otherwise the sequence may apply the image to the wrong volume or destroy data.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #2
Fix Install Application failures
When the failed action is Install Application, the same HRESULT can be emitted after several different subsystems fail. Microsoft identifies stale or corrupted content data, local WMI policy access, management-point or database communication, BITS jobs, network transport, IIS, and post-install evaluation as possible failure domains. Trace the dependency chain in order.
Content and cache evidence
Start with CAS.log, ContentTransferManager.log, and DataTransferService.log. Look for the content ID, download request, retry sequence, and the first transfer or cache error. If content is stale or corrupted, redistribute or refresh the affected application content through your normal Configuration Manager content-management process, then rerun the deployment. A final 0x80070057 without a content ID is not proof that the application itself is malformed.
Policy and WMI evidence
Use DCMAgent.log, CIStore.log, CIStateStore.log, and CIAgent.log to determine whether the client received policy, stored the configuration item, evaluated it, and recorded a compliant or failed state. If the log shows local WMI policy-access errors, resolve that client-management problem before repeatedly reinstalling the application. The first WMI or policy error is more actionable than the task-sequence summary.
Location, management point, and network evidence
Check LocationServices.log and MP_Location.log for management-point and content-location selection. Then compare their timestamps with transfer errors and the task-sequence entry in smsts.log. A client that cannot obtain a valid location can fail before it ever evaluates the installer. Management-point or database communication, network transport, BITS, and IIS problems require different administrators, so identify which component first reports the fault before changing boundaries, services, or application content.
Post-install evaluation
An installer can return successfully and still fail Configuration Manager’s detection or compliance evaluation. Review the evaluation entries in CIAgent.log and CIStateStore.log after the install attempt. Confirm that the deployment’s detection rule describes the version or state the installer actually creates. If evaluation fails, correcting the detection rule is safer than treating the event as a download or partition error.
Install Application investigation checklist
- Capture the application name, content ID, deployment type, device, and task-sequence step.
- Find the first timestamped failure in
smsts.log. - Follow that timestamp through
CAS.log,ContentTransferManager.log, andDataTransferService.logfor content and BITS activity. - Use
LocationServices.logandMP_Location.logfor location and management-point selection. - Use
DCMAgent.log,CIStore.log,CIStateStore.log, andCIAgent.logfor policy, WMI, state, and evaluation. - Change one layer at a time and rerun the same deployment so the new log can prove whether the original failure moved or disappeared.
Repair MDT task-sequence editing and creation failures
If the error appears while loading, creating, or editing an MDT-integrated task sequence rather than while deploying an image, inspect WMI registration. Microsoft documents missing or improperly registered BDD_* WMI classes as a cause of task-sequence loading failures.
- Close every Configuration Manager console window.
- Use Configure ConfigMgr Integration to remove the MDT console extensions.
- Run the task-sequence wizard again to verify whether the loading failure is gone.
- Install the MDT extensions again through the integration process, then reopen the console and recreate or edit the task sequence.
- Check that the
BDD_*classes are registered before importing or modifying additional MDT steps.
Perform this integration repair on a test or administrative workstation first. Reinstalling extensions while consoles remain open can leave a partially loaded snap-in and obscure whether the WMI registration was corrected.
Account for MDT’s retired status
Microsoft’s current MDT troubleshooting guidance says MDT is retired and recommends removing MDT task-sequence steps and integration to prevent corruption. Existing on-premises Configuration Manager operating-system-deployment environments may still contain MDT-integrated sequences, but MDT should not be introduced as a new deployment dependency. Where an existing sequence is failing because of its integration, plan a supported modernization path rather than rebuilding the environment around retired components.
Separate two decisions: restore the immediate deployment by correcting the registered classes or destination, and reduce lifecycle risk by removing retired MDT dependencies when your operating-system-deployment design allows it. A successful short-term repair does not change MDT’s support status.
What not to change while troubleshooting
- Do not edit disk numbers or wipe volumes based only on the generic HRESULT.
- Do not redistribute every application in the hierarchy before identifying the content ID and first transfer error.
- Do not reinstall MDT extensions with an open Configuration Manager console.
- Do not treat the title’s extra-zero code as confirmed until the log shows the exact value.
- Do not judge success by the final task-sequence line; verify that the first failing component now completes and that the deployment reaches the next action.
Interpret the HRESULT without over-reading it
0x80070057 identifies a documented error value, but it does not identify the failing subsystem by itself. The same value can accompany a destination mismatch, a content-transfer problem, a policy or WMI error, or a failed compliance evaluation. Treat the HRESULT as a correlation key: pair it with the action name, timestamp, content ID or destination value, and the component that logged the first failure.
The decimal representation -2147024809 may appear in a support message or script output instead of hexadecimal notation. Normalize both forms in your incident notes, but preserve the original representation and surrounding log lines. This avoids mistaking a conversion or copied search term for a second Configuration Manager error.
Compare remediation paths before making changes
| Remediation path | Best evidence | Typical scope | Change risk | Lifecycle consideration |
|---|---|---|---|---|
| Correct a disk, partition, drive letter, or destination variable | smsts.log and the format step |
One task sequence or hardware branch | Low when the logged values are used; high if disks are wiped blindly | Applies to supported Configuration Manager OSD |
| Repair content, policy, transfer, or location dependencies | CAS.log, ContentTransferManager.log, DataTransferService.log, policy and location logs |
One client, application, boundary, or site service | Start with client or content evidence before changing infrastructure | Applies to supported Configuration Manager application deployment |
| Re-register MDT integration | Console behavior and BDD_* WMI classes |
Administrative workstation or MDT-integrated sequences | Moderate; close consoles and test the integration first | MDT is retired, so plan removal rather than expanding it |
This comparison keeps a local log correction separate from a site-wide service change. It also prevents a console-only MDT problem from triggering unnecessary edits to operating-system partitions or application content.
Build a clean evidence bundle
For a repeatable escalation, preserve the original logs before rerunning the deployment. Include the exact code, device name, deployment or task-sequence identifier, firmware branch, failed action, and timestamps. For an operating-system failure, include the Format and Partition Disk configuration and the destination settings from Apply Operating System. For an application failure, include the application name, content ID, deployment type, and the relevant content, policy, location, and evaluation entries.
Keep one successful comparison when possible. A working device running the same task sequence can show whether the destination variable, selected management point, content ID, WMI policy access, or transfer sequence differs. Do not overwrite the original incident with a later test; label each run so the first-error location can be compared accurately.
Rank #4
When the same code keeps returning
One device only
Compare the affected client’s smsts.log and component logs with a successful device at the same task-sequence step. Differences in destination variables, selected locations, content IDs, WMI policy access, or transfer retries point toward a client-specific issue.
Many devices at one step
If multiple devices fail with the same content or management-point evidence, investigate the shared application, distribution, location, network, BITS, IIS, or site-service layer. Preserve one complete log set before changing infrastructure so the original error remains attributable.
Recommended Free Tools
Only MDT editing is affected
If deployments run but the console cannot load or create MDT sequences, focus on BDD_* WMI registration and the integration-removal/reinstallation procedure. Do not alter partition destinations or application content for a console-only failure.
After the fix, validate the next action
- Run the same deployment or wizard on a representative test device or administrative workstation.
- Confirm that the original action completes, not merely that the dialog disappears.
- Check the new
smsts.logor component logs for the earliest error and verify that the failure no longer occurs at the same timestamp. - For applications, confirm both installation and Configuration Manager detection or compliance evaluation.
- For operating-system deployment, verify that the image was applied to the intended volume and that no unrelated disk was modified.
- For MDT, document the repaired registration and the longer-term plan to remove retired integration.
Validation should be narrower than the initial change. If a destination correction fixed one hardware branch, test that branch before revising every task sequence. If a content refresh fixed one deployment type, confirm that deployment type before changing distribution or management-point settings globally.
A repeatable recovery workflow
- Copy the exact HRESULT and the failed action from the appropriate log.
- Confirm whether the value is
0x80070057or a different code. - Classify the phase as partitioning, Apply Operating System, Install Application, or MDT editing.
- Collect only the logs relevant to that phase and locate the earliest error.
- Correct the smallest matching configuration: destination and variable alignment, content or policy dependency, or MDT WMI registration.
- Run a controlled test on one representative device.
- Compare the new timestamps and first-error location with the original incident.
- Document the corrected value and, if MDT was involved, record a modernization plan because the integration is retired.
This process distinguishes a parameter mismatch from a downstream symptom and limits high-impact changes to the layer supported by evidence.
Reference material and optional tools
The Microsoft Press book System Center: Troubleshooting Configuration Manager can serve as a physical SCCM troubleshooting book or Configuration Manager troubleshooting guide for administrators who prefer a reference volume. The cited edition is older, so use it as a supplement to current Microsoft Learn documentation rather than as a replacement for current product guidance.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte PC Repair is an optional shortcut for common Windows-side problems that may accompany a failing client, such as broken system elements, invalid redirects, shared DLL issues, or application crashes. It can also clean temporary and cache files and provide an app-crash log, but it does not replace Configuration Manager log analysis or an antivirus, and results vary. It runs on Windows 11, 10, 8, and 7; the free trial is offered by category for at least two days, followed by a subscription.
Frequently Asked Questions
Is 0x800070057 the same as 0x80070057?
Not automatically. Microsoft material documents 0x80070057, also shown as -2147024809. Confirm the complete hexadecimal value in the affected log before applying a fix.
Where is SMSTS.log during a task-sequence failure?
After the Configuration Manager client is installed, the normal path is C:WindowsCCMLogssmsts.log. Use CMTrace, OneTrace, or Support Center Log File Viewer. Other client logs are in C:WindowsCCMLogs.
Why does Apply Operating System return 0x80070057?
Compare its destination with the preceding Format and Partition Disk step. Check the selected disk and partition, logical drive letter, or destination variable, and verify that the active UEFI or BIOS branch sets matching values.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhich logs should I check for Install Application?
Start with smsts.log, then correlate CAS.log, ContentTransferManager.log, DataTransferService.log, LocationServices.log, MP_Location.log, DCMAgent.log, CIStore.log, CIStateStore.log, and CIAgent.log around the first failure.
Should I redistribute application content immediately?
Only when the content logs show a stale or corrupted content problem. Identify the content ID and first transfer or cache error before refreshing content; the generic HRESULT alone does not prove the application content is bad.
How do I repair an MDT task-sequence editing failure?
Close all Configuration Manager consoles, remove the MDT extensions with Configure ConfigMgr Integration, rerun the wizard, and then install the extensions again. Check that the BDD_* WMI classes are registered.
Is MDT still supported for new Configuration Manager deployments?
Microsoft’s current guidance says MDT is retired and recommends removing MDT steps and integration to prevent corruption. Repair an existing sequence if necessary, but plan a supported modernization path instead of adding new MDT dependencies.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What does it mean if one device fails but others succeed?
Compare its smsts.log and component logs with a successful device at the same step. Differences in destination variables, content IDs, selected locations, WMI policy access, or transfer retries suggest a client-specific issue.
The Bottom Line
Confirm the literal HRESULT, locate the first failing action, and fix only the matching layer. Align partition destinations for Apply Operating System, trace content and policy dependencies for Install Application, and repair BDD_* WMI registration for MDT editing problems. Remember that MDT is retired, so treat any integration repair as a short-term recovery while planning modernization.
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.
