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.
915 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

    Hello,thank you for your reply. Sorry also for all thoose question. I am quite new to this topic.

    I did the capture of the image via SCCM Adding Operation System image. I converted beforehand the image.esd to image.wim and add this image to OS images. Seen in the pictures below.



    One side note. I also verified the permissions on the image itself, see picture below. Also this seems to be correct.


    0 comments No comments

  2. Michael Jacinto 136 Reputation points

    Hello ColinFord, thank you for your time and reply, the mention way seems to work out. At least it stared now the OS instalation and did not stop with an error. Can you let me know why this should be done this way, for my understanding.
    As far as i read, normaly i should import the image the way i did, but it did not work. :-(

    0 comments No comments

  3. Colin Ford 1,026 Reputation points

    To import an Operating System Image, the package source folder should contain only one file in the of the root folder - the install.wim or your captured WIM file.

    If you want to make a custom captured WIM file, for example you want to pre-install some some software that is used on all devices to save time doing that every build, like Office for example, you can follow this https://learn.microsoft.com/en-us/windows/deployment/deploy-windows-cm/add-a-windows-10-operating-system-image-using-configuration-manager

    0 comments No comments

  4. AllenLiu-MSFT 41,136 Reputation points Microsoft Vendor

    Glad to hear that ColinFord-6663's suggestion is useful, and thanks ColinFord-6663 for the explanation.
    Is there any other assistance we can provide?

    0 comments No comments