Tasksequence stops with an error on Client side 0x80004001

Michael Jacinto 136 Reputation points

Hello all,

we created a new ZTI tasksequence, a simple one, to deploy the latest image Win10, 20H2 to our clients. When doing it an error apears, which seems to be one of those generic messages.

When i check the client log, which is attached there are the erros:

[Task sequence execution failed with error code 80004005]
Failed to run the last action: Apply Operating System. Result -2145255404

System is: Server 2012R2 with SCCM 2002.

The image which we are trying to deploy is 20H2


Here is the simple Task sequence, we did for testing:


Client LOG:


For any hint i woould be gratefull. Thank you.

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
899 questions
0 comments No comments
{count} votes

Accepted answer
  1. Colin Ford 1,026 Reputation points

    No worries at all.

    That looks like source media, which needs to be imported into SCCM differently.

    Try the following:

    1. Create a new package under \Software Library\Overview\Operating Systems\Operating System Upgrade Packages and point it to the root of the Windows 10 de_DE folder where setup.exe is located. Then distribute this to a DP.
    2. Modify your task sequence to instead use the "Apply operating system from original installation source" option on the "Apply Operating System" step and point to this new package.
    0 comments No comments

12 additional answers

Sort by: Most helpful
  1. Michael Jacinto 136 Reputation points

    I tried again and now i have the error code 0x80220014 on the client

    0 comments No comments

  2. AllenLiu-MSFT 40,316 Reputation points Microsoft Vendor

    Hi, @Michael Jacinto
    Thank you for posting in Microsoft Q&A forum.
    The error code in your log is very similar to below article, the issue reported when we are capturing OEM image and scheduling for deployment, once we have volume license wim file, above issue should not come.
    (Third-party link, just for your reference)

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. Michael Jacinto 136 Reputation points

    Hello AllenLiu, thank you for the reply. It is not an oem image. I created a new Windows 10 Pro image and add it to SCCM and made a new depoy.

    Following issue is now appearing:


    Error code 0x80070002 in SCCM 2012 can be interpreted as a network error wherein during the OSD the necessary files are not accessible by the computer where the operating system is being deployed. SCCM Account have full rights on the specific folder.

    0 comments No comments

  4. Colin Ford 1,026 Reputation points

    It looks like you may be applying a boot.wim instead of an operating system image WIM.

    Can you please send a screenshot of the Apply Operating System step in the task sequence, and the "Images" property tab of the OS image package MQ100046.

    0 comments No comments