none
Error capturing image of a Windows 10 1709 with SCCM 2016 0x80004005

    Question

  • Windows 10 Enterprise 1709 reference PC built in VMWare. 

    I am trying to capture it but keep receiving error 0x80004005 after a lot of the Sysprep work has been completed. 

    I cannot post the entire SMSTS.log file, as this system has a character limit, but here is the part that seems to fail:

    <![LOG[Save the current environment block]LOG]!><time="08:32:24.771+300" date="03-28-2018" component="TSManager" context="" type="0" thread="4604" file="executionenv.cxx:827">
    <![LOG[Created volatile registry entry for pending reboot initiated by this task sequence]LOG]!><time="08:32:24.786+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="engine.cxx:38">
    <![LOG[Executing command line: "bcdedit.exe"]LOG]!><time="08:32:24.786+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="CommandLine.cpp:828">
    <![LOG[Process completed with exit code 0]LOG]!><time="08:32:24.880+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="CommandLine.cpp:1124">
    <![LOG[TSUEFIDrive: ]LOG]!><time="08:32:24.880+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="engine.cxx:907">
    <![LOG[TSUEFIDrive: ]LOG]!><time="08:32:24.880+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="bootimage.cpp:774">
    <![LOG[Staging boot image 10100003]LOG]!><time="08:32:24.880+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="bootimage.cpp:781">
    <![LOG[Volume '\\?\Volume{81a7c2ff-0000-0000-0000-100000000000}\' not found]LOG]!><time="08:32:24.896+300" date="03-28-2018" component="TSManager" context="" type="2" thread="4604" file="devicepath.cpp:73">
    <![LOG[Boot image already staged locally]LOG]!><time="08:32:24.911+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="bootimage.cpp:867">
    <![LOG[Installing boot image to hard drive]LOG]!><time="08:32:24.911+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="bootimage.cpp:617">
    <![LOG[Backing up existing boot system before trying to set up new boot system]LOG]!><time="08:32:24.911+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="bootimage.cpp:642">
    <![LOG[Volume '\\?\Volume{81a7c2ff-0000-0000-0000-100000000000}\' not found]LOG]!><time="08:32:24.927+300" date="03-28-2018" component="TSManager" context="" type="2" thread="4604" file="devicepath.cpp:73">
    <![LOG[BootLoader::backup: Z:\, C:\_SMSTaskSequence\backup]LOG]!><time="08:32:25.005+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="bootloader.cpp:85">
    <![LOG[Failed to save offline store to C:\_SMSTaskSequence\backup]LOG]!><time="08:32:25.583+300" date="03-28-2018" component="TSManager" context="" type="3" thread="4604" file="bootsystem.cpp:506">
    <![LOG[Failed to install boot image. 
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="08:32:25.599+300" date="03-28-2018" component="TSManager" context="" type="3" thread="4604" file="bootimage.cpp:736">
    <![LOG[Failed to install boot image 10100003. 
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="08:32:25.599+300" date="03-28-2018" component="TSManager" context="" type="3" thread="4604" file="engine.cxx:984">
    <![LOG[Failed to reboot the system. Error 0x80004005)]LOG]!><time="08:32:25.599+300" date="03-28-2018" component="TSManager" context="" type="3" thread="4604" file="engine.cxx:1107">
    <![LOG[Failed to initialize a system reboot. 
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="08:32:25.599+300" date="03-28-2018" component="TSManager" context="" type="3" thread="4604" file="engine.cxx:622">
    <![LOG[Fatal error is returned in check for reboot request of the action (Prepare Operating System). 
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="08:32:25.599+300" date="03-28-2018" component="TSManager" context="" type="3" thread="4604" file="engine.cxx:310">
    <![LOG[An error (0x80004005) is encountered in execution of the task sequence]LOG]!><time="08:32:25.599+300" date="03-28-2018" component="TSManager" context="" type="3" thread="4604" file="engine.cxx:390">
    <![LOG[Do not send status message in full media case]LOG]!><time="08:32:25.599+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="utils.cpp:6499">
    <![LOG[Task Sequence Engine failed! Code: 80004005]LOG]!><time="08:32:53.646+300" date="03-28-2018" component="TSManager" context="" type="3" thread="4604" file="tsmanager.cpp:1263">
    <![LOG[****************************************************************************]LOG]!><time="08:32:53.646+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="tsmanager.cpp:1295">
    <![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="08:32:53.646+300" date="03-28-2018" component="TSManager" context="" type="3" thread="4604" file="tsmanager.cpp:1296">
    <![LOG[Cleaning Up.]LOG]!><time="08:32:53.646+300" date="03-28-2018" component="TSManager" context="" type="1" thread="4604" file="tsmanager.cpp:794">

    Wednesday, March 28, 2018 2:45 PM

All replies

  • There's no such thing as SCCM 2016.

    What version exactly of ConfigMgr are you running? What ADK version?

    Is this happening on all systems or just one?

    Is the system configured for UEFI? If so, is the system properly partitioned for UEFI boot?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, March 28, 2018 3:51 PM
  • Hello James,

    I assume that you ran into the same error as I did. The problem is, that same apps are installed/configured or whatever to the current user profile. This somehow prevents the capturing of the image.

    Stick to this site and try again.

    Solution

    Before deleting the current profile, don't forget to enable the local admin and check if it is part of the local admin group. Otherwise,you won't have an admin to capture your image.

    Wednesday, August 29, 2018 6:22 AM