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 1602 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

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.

6
Leave a Reply

avatar
4 Comment threads
2 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
newest oldest most voted
Nat Muniz
Guest
Nat Muniz

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… Read more »

Nick
Guest
Nick

I’m having the same issue. Let me know if you get this resolved. I’m attempting to use USB Media as well.

Harvey
Guest
Harvey

Try to run the “clean” command in diskpart and re-run the TS.

Nguyen Ngoc Son
Guest
Nguyen Ngoc Son

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.… Read more »

Mahesh Sawant
Guest
Mahesh Sawant

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:… Read more »

Rabih
Guest
Rabih

comment image Hello,
I have the following error when I am deploying new machine, in the middle of the installation I got sequence error code : 0x80070002, I check the log and I found the attached image. any help please.
thank you

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. AcceptRead More