SCCM TS Error 0x80070057 during Apply Operating System Image step

One of the user in my community forums reported an OSD issue. When he tried deploying the OS using SCCM the TS failed. He encountered SCCM TS Error 0x80070057 during Apply Operating System Image step.

The user was running SCCM and had setup a simple task sequence for testing purposes. The task sequence failed between partition drive and applying windows.

It loads the PE environment and then begins to run through the steps but fails as soon as it gets to “Apply Operating System”. Looking at the smsts.log file the error was “The / target parameter specifies an invalid target location”. Failed to run the action: Apply Operating System Image.

This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. Below is the screenshot of the error (smsts log file).

SCCM TS Error 0x80070057 during Apply Operating System Image step
SCCM TS Error 0x80070057 during Apply Operating System Image step

 SCCM TS Error 0x80070057 during Apply Operating System Image step

There are more than one resolution to fix this issue.

Resolution 1 – In the Task Sequence the partition check if there is a variable name specified. After setting the variable to OSDisk, which the step “Apply Operating System Image” uses, the task sequence should work fine.

Resolution 2 – Examine the options for each “Format and Partition Disk” step. You’ll see that each one uses a condition based on the task sequence variable that’s set in the “Set variable for format and partition disk”. Just change “…” to the appropriate value. Ensure that ImageOSVer should be set to the version of the OS you are deploying.

Need Assistance?

Send us a message or post your question in forums.

10 thoughts on “SCCM TS Error 0x80070057 during Apply Operating System Image step”

  1. Hello,
    I also received this error trying to image a workstation with USB Media – task sequence. I disabled Secure Boot in the bios to resolve issue.

  2. HI Prajwal, I am facing same issue. I have a 1 Primary Server and another 1 Site Server. Both are Windows Server 2012 R2 Servers with SCCM Version 1706 installed on Primary Server. I am trying PXE boot via SCCM Secondary Site Server but its failing with below error:

    Expand a string: TSManager 27-03-2019 09:32:59 376 (0x0178)
    Command line for extension .exe is “%1” %* TSManager 27-03-2019 09:32:59 376 (0x0178)
    Set command line: OSDApplyOS.exe /image:IN1000BD,%OSDImageIndex% /target:0,2 /runfromnet:False TSManager 27-03-2019 09:32:59 376 (0x0178)
    Start executing the command line: OSDApplyOS.exe /image:IN1000BD,%OSDImageIndex% /target:0,2 /runfromnet:False TSManager 27-03-2019 09:32:59 376 (0x0178)
    !——————————————————————————————–! TSManager 27-03-2019 09:32:59 376 (0x0178)
    Expand a string: WinPE TSManager 27-03-2019 09:32:59 376 (0x0178)
    Executing command line: OSDApplyOS.exe /image:IN1000BD,%OSDImageIndex% /target:0,2 /runfromnet:False TSManager 27-03-2019 09:32:59 376 (0x0178)
    Command line for extension .exe is “%1” %* ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    Set command line: “OSDApplyOS.exe” /image:IN1000BD,2 /target:0,2 /runfromnet:False ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    Found run from net option: 0 ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    Not a data image ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    ApplyOSRetry: ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    TSLaunchMode: PXE ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    Adding logical drive: C: ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    Skipping non-local logical drive: D: ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    Adding logical drive: S: ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    Skipping non-local logical drive: X: ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    TS::Utility::CDisk::FixedDiskToLogicalDrive failed; 0x80070490 ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    CDisk::FixedDiskToLogicalDrive( target.Disk, target.Partition, volume), HRESULT=80070490 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installcommon.cpp,639) ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    Disk 0, partition 2 does not exist or is not a valid volume ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    The requested target could not be resolved to a valid volume on this computer. Check your task sequence to ensure this drive is correct and that it is being created
    The parameter is incorrect. (Error: 80070057; Source: Windows) ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    ResolveTarget( g_Target, g_InstallType == InstallType_DataImage, targetVolume ), HRESULT=80070490 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,483) ApplyOperatingSystem 27-03-2019 09:32:59 1672 (0x0688)
    Process completed with exit code 2147943568 TSManager 27-03-2019 09:32:59 376 (0x0178)
    !——————————————————————————————–! TSManager 27-03-2019 09:32:59 376 (0x0178)
    Failed to run the action: Apply Operating System.
    Element not found. (Error: 80070490; Source: Windows) TSManager 27-03-2019 09:32:59 376 (0x0178)

    • Check your partition steps, BDEdrive or C: (if only) must be set as bootable partition. Maybe you ticked that off? Another good solution for any common OSD problem is to clean the disk with diskpart first, so while being in WinPE, hit F8 -> diskpart -> select disk 0 -> clean -> exit.

  3. Hi Prajwal,

    Thank you for the information above. I am wondering if you can expand on how and where to add the variable in resolution 1. I am finding myself with this problem when using USB media to run my task sequence. The same TS runs fine when I initiate it from the network but when I am running it from the USB I am getting an error in the smsts.log – Failed to run the action: Partition Disk. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows) as you described above. Please let me know if you can provide further details on whether or not this resolution applies to my case and if not can you point me in the right direction.

    Thanks
    Nat

  4. Hi Prajwal Desai.
    I need your support to troubleshotting issue with OS deployment. I am doing in a Hyper-V lab environtment with SCCM 2012 R2. Previously, I captured already Win7 and I have a .vim file. When I tried to deploy a windows 7 using task sequences, I get an error code 0x80070057. Then I spent my times in the Internet and check the smsts.log. I found that this issue relates to partition disk 0 – Bios. Then I tried to use Diskpart.exe by pressing F8 during the client boot and format client disk 0 to NFTS and restart again. but the result is still not successfull. The result showed a RAW partition and assigned C letter and then failed. I would like to get your support to fix this issue.
    Your support is highly appriciated.

  5. Hi,

    I too observed below errors in smsts.log file while deploying windows 10 enterprise task sequence created for Dell 5450 laptop.

    Failed to run the action: Apply Operating System Image. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)

    Process completed with exit code 2147942487

    The execution of the group (Deploy Operating System) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)

    Unable to understand how to implement resolutions provided above. Can you please kindly help in understanding the solution for this issue.

    Regards,
    Mahesh

Comments are closed.