none
Capturing an Image from newly built Reference Computer fails with error code 0x00004005 - Windows 10 - 1511

    Question

  • I have now built two brand new clean Windows 10 x64 Enterprise reference computers on a virt.  When I go to capture to the Configuration Manager 2012 R2 updated with the latest cu, I get error code 0x00004005.   I get this on the first run through right after building from the Windows 10 - build 10586 that I downloaded last week before MS pulled it.

    The SMTSLog.txt located here: C:\users\username\AppData\Local\Temp shows this:

    Executing command line: "C:\Windows\system32\sysprep\sysprep.exe" /quiet /generalize /oobe /quit PrepareOS 11/23/2015 12:12:07 PM 4184 (0x1058)
    Process completed with exit code 0 PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    Sysprep state set to IMAGE_STATE_COMPLETE PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    The OS has not been generalized using sysprep.exe, or sysprep did not complete. PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    bSysPreped, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,514) PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    Sysprep did not complete successfully PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    RunSysprep(sCmdLine, bActivate, m_bDebug), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1375) PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    Unable to sysprep the machine, hr=80004005 PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    pCmd->Sysprep(bActivate, bMsd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\main.cpp,270) PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    Sysprep'ing the machine failed, hr=80004005 PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    De-Initialization successful PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    Exiting with error code 16389 PrepareOS 11/23/2015 12:12:08 PM 4184 (0x1058)
    Process completed with exit code 16389 TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    !--------------------------------------------------------------------------------------------! TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    Could not find CCM install folder. Don't use ccmerrors.dll TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    Failed to run the action: Prepare Operating System. 
    Unknown error (Error: 00004005; Source: Unknown) TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    Do not send status message in full media case TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    Set a global environment variable _SMSTSLastActionRetCode=16389 TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    Clear local default environment TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    Let the parent group (Capture the Reference Machine) decides whether to continue execution TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    The execution of the group (Capture the Reference Machine) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)
    Could not find CCM install folder. Don't use ccmerrors.dll TSManager 11/23/2015 12:12:08 PM 4088 (0x0FF8)


    David Grand

    ===== 

    (two hours later) - I just spun up a hardware based Reference Computer.  Same problem.  See below:

    =====

    I need an answer quickly.  I have opened up a Premier case on this:  115112413406937

    • Edited by herkamer Tuesday, November 24, 2015 5:53 AM
    Monday, November 23, 2015 9:18 PM

Answers

  • I was able to capture my reference computer.   The issue around my failed sysprep during the capture process was that with Windows 10 1511, Microsoft is going out to the Windows Store during each initial login and downloading some Universal Apps.

    We need to TURN OFF the Consumer Experience during a reference machine build AND at least for the initial steps have NO internet access for the Reference Computer. Here is the process:

    1. Turn off the network access for the Reference Computer
    2. Install from the 1511 ISO
    3. Install Office from a Click to Run thumb drive
    4. Run the MMC for local Group Policy and turn off the Customer Experience “Computer Configuration –> Administrative Templates –> Windows Components –> Cloud Content” called “Turn off Microsoft consumer experiences”.  See link at bottom of this reply for more info.
    5. Reboot.
    6. Turn ON the network access for the remote computer
    7. Run Windows Update
    8. Install any other Desktop Application you need on the WIM.
    9. Reboot
    10. Capture

    Thanks to Michael Niehaus for his idea about Turning OFF the consumer experience.    http://blogs.technet.com/b/mniehaus/archive/2015/11/23/seeing-extra-apps-turn-them-off.aspx


    David Grand


    • Marked as answer by herkamer Wednesday, November 25, 2015 7:51 PM
    • Edited by herkamer Wednesday, November 25, 2015 7:52 PM
    Wednesday, November 25, 2015 7:51 PM

All replies

  • "Configuration Manager 2012 R2 updated with the latest cu"

    This is not sufficient. You must have ConfigMgr 2012 SP1 (plus preferably CU2) *and* the ADK for Win10 installed on the primary site server (with any previous ADKs uninstalled) *and* you must be using WinPE 10 based boot images.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, November 24, 2015 2:05 PM
  • Dear Sir,

    To support windows 10, Site servers need to upgrade at least to SCCM 2012 R2 SP1 or SCCM 2012 SP2. As Jason said, SCCM 2012 R2 SP1 CU2 is preferred. Also the ADK and WinPE version need to update.

    Best regards

    Frank

    Wednesday, November 25, 2015 1:34 AM
    Moderator
  • Yes, we had a Microsoft PFE come out in mid-October and help us get going on this SCCM build. I have a Console Version of 5.0.8236.1203 and a Site version of 5.00.8239.1000.     We have not yet put on the November CU.

    I have been capturing and deplying Windows 10 x64 Enterprise build 10248 since mid October.   Last week we got the ISO for 1511 from our MVLS site and have been unsuccessful in capturing any customized Reference Computer (now on my 8th!) with various Capture Media since the advent of 1511.

    When the Microsoft PFE was here we put the Windows 10 ADK on the system in the correct order and uninstalled the older ADK.

    Yes, our boot images are WinPE 10.  Problems only surfaced once we tried to capture a 1511 system. 


    David Grand


    • Edited by herkamer Wednesday, November 25, 2015 4:33 AM
    Wednesday, November 25, 2015 4:31 AM
  • With build 1511, also ADK renewed, maybe you should consider to upgrade that as well.

    I really don´t see any need to capture W10 images, since install.wim is fully supported and it will be renewed few times a year. Unless your customer or organization requires super fast deployment times.

    Wednesday, November 25, 2015 6:17 AM
  • With build 1511, also ADK renewed, maybe you should consider to upgrade that as well.


    Don't! http://blogs.technet.com/b/configmgrteam/archive/2015/11/20/issue-with-the-windows-adk-for-windows-10-version-1511.aspx

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, November 25, 2015 6:45 AM
  • Thanks for the heads  up about the new Win 10 ADK.  I will make sure I don't install that.  In the past year, MS has really let the QA go on the patches they release. 

    I was able to capture a WIM from a Reference Computer running Windows 10 - build 1511 but only when I attempted the capture immediately after installing from an ISO.  I ran no Windows Update and did not put any of the desired apps on the Reference computer.   I might as well install from an ISO at this point.

    The failure each time is in the SysPrep.  SysPrep is choking on the Universal Apps.

    See above (in this reply) for a snip from SysPrep's setupact.log.


    David Grand


    • Edited by herkamer Wednesday, November 25, 2015 2:47 PM
    Wednesday, November 25, 2015 2:46 PM
  • The failure each time is in the SysPrep.  SysPrep is choking on the Universal Apps.

    See above (in this reply) for a snip from SysPrep's setupact.log.

    go to Settings - System - Apps & Features - find CandyCrushSodaSaga and Twitter - delete them. repeat capturing.
    Wednesday, November 25, 2015 2:55 PM
  • Here's a better way (since image creation should be automated afterall -- no yucky manual stuff): http://blogs.technet.com/b/mniehaus/archive/2015/11/23/seeing-extra-apps-turn-them-off.aspx

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, November 25, 2015 4:12 PM
  • I was able to capture my reference computer.   The issue around my failed sysprep during the capture process was that with Windows 10 1511, Microsoft is going out to the Windows Store during each initial login and downloading some Universal Apps.

    We need to TURN OFF the Consumer Experience during a reference machine build AND at least for the initial steps have NO internet access for the Reference Computer. Here is the process:

    1. Turn off the network access for the Reference Computer
    2. Install from the 1511 ISO
    3. Install Office from a Click to Run thumb drive
    4. Run the MMC for local Group Policy and turn off the Customer Experience “Computer Configuration –> Administrative Templates –> Windows Components –> Cloud Content” called “Turn off Microsoft consumer experiences”.  See link at bottom of this reply for more info.
    5. Reboot.
    6. Turn ON the network access for the remote computer
    7. Run Windows Update
    8. Install any other Desktop Application you need on the WIM.
    9. Reboot
    10. Capture

    Thanks to Michael Niehaus for his idea about Turning OFF the consumer experience.    http://blogs.technet.com/b/mniehaus/archive/2015/11/23/seeing-extra-apps-turn-them-off.aspx


    David Grand


    • Marked as answer by herkamer Wednesday, November 25, 2015 7:51 PM
    • Edited by herkamer Wednesday, November 25, 2015 7:52 PM
    Wednesday, November 25, 2015 7:51 PM
  • alternative with less steps:

    1. install from the 1511 ISO
    2. install all that you need (applications, updates)
    3. uninstall CandyCrushSodaSaga and Twitter
    4. sysprep
    5. capture

    but your way is better - nobody know which Apps MS will have install with new build...

    Wednesday, November 25, 2015 8:54 PM
  • Yeah but Ewwww yuck -- you're doing manual things. Why would you ever want to manually do anything? We're in IT, you're supposed to automate it. Mike tells you how to do this at the bottom of the post.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, November 26, 2015 2:33 AM
  • who said "ever"? i achieved only this purpose (same as herkamer's)  with less steps (means - faster) and forgot about it.
    • Edited by Anahaym Thursday, November 26, 2015 8:31 AM
    Thursday, November 26, 2015 8:31 AM
  • My point is that you just be building your images using a *completely* automated process. Running the MMC is *not* automated. 

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, November 26, 2015 4:02 PM
  • Running the MMC is *not* automated

    sure 

    4. Run the MMC for local Group Policy and turn off the Customer Experience “Computer Configuration –> Administrative Templates –> Windows Components –> Cloud Content” called “Turn off Microsoft consumer experiences”.
    it is reason, why i didn't use it. i prefer less steps + automation = quickly achieved goal
    Thursday, November 26, 2015 4:36 PM
  • There is a command line for shutdown the services (like turn off "microsoft consumer experience"). I prefer ConfMgr task sequences with run command lines, CMD or powershell for that :)
    Thursday, November 26, 2015 6:25 PM
  • HI.

    Actually a lot of user have reported this issue. And I have had a long fight, trying to capture .wim, myself.

    I solved it by doing the stebs manually.

    I tryed to run Sysprep manually but got an error and an error LOG. By examine the LOG I find out that the original .ISO from MS, acts like an update when installed.

    You have to run the "reset machine to factory defaults" and save nothing. You will get the warning that you cant go back after the "reset".

    When the machine is done resetting. You shoul be able to run SysPrep with an Admin-account and so should SCCM2012 R2 be able to capture the image :-)

    Hope it works!

    Friday, January 29, 2016 10:12 AM
  • Hi!!!

    For any other folk out there that find this 3d

    Just install whatever you need under the "Administrator" account (that has to be enabled and password resetted); get rid of ANY other user account created on the machine

    Run this in Powershell to get rid of all the Appx bloatware introduced by Microsoft

    Get-AppxPackage -AllUsers | Remove-AppxPackage

    Also, if you want to remove OneDrive from the image

    Run this in an Elevated Command Prompt

    taskkill /f /im OneDrive.exe

    if on 32 Bit
    %SystemRoot%\System32\OneDriveSetup.exe /uninstall

    if on 64 Bit
    %SystemRoot%\SysWOW64\OneDriveSetup.exe /uninstall

    rd "%UserProfile%\OneDrive" /Q /S
    rd "%LocalAppData%\Microsoft\OneDrive" /Q /S
    rd "%ProgramData%\Microsoft OneDrive" /Q /S rd "C:\OneDriveTemp" /Q /S
    REG Delete "HKEY_CLASSES_ROOT\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" /f
    REG Delete "HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" /f

    Happy sysprep and enjoy your clean system image

    Please note that default bloatware will be automatically loaded at first User Account creation after deployment

    Personal side note:

    Thank you Microsoft for the frigging Candy Crush Soda Saga / Twitter and all the "Great appx experience"...

    For F sake, at least leave them out of Pro and Enterprise versions of the OS... spare us all!

    Friday, February 12, 2016 9:50 PM
  • First, please try to be professional. Yes, we all have emotions, but there's no reason anyone will take you more seriously because you put an "F" in your post -- quite the opposite in fact.

    As for your concern, see the following:


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, February 13, 2016 12:29 AM
  • Alternatively, there appear to be ways to do all of these things with ICD through provisioning and imaging projects. I have played with the ICD interface and have been able to create provisioning packages that do quite a bit - add local accounts, get rid of universal apps, etc. But, it's scantily documented at this point and it was a challenge to figure out what the family package name variable was for universal app uninstall. In case anyone goes down that path when you run get-appxpackage –allusers in Powershell it returns a list of all universal apps. Each entry includes a PackageFamilyName as follows and can be used in ICD to get rid of universal apps:

    PackageFamilyName     : Microsoft.BingFinance_8wekyb3d8bbwe

    One question I still have, and will probably have to test because the documentation does not specify it,  is whether or not the customizations I make in ICD, universal apps removed for instance, make their way into the .wim that can be created with ICD. That would be pretty cool. I could simply use that .wim in my SCCM task sequences and some of these steps I have added with Powershell Scripts could be eliminated?




    Thursday, March 03, 2016 9:50 PM
  • I know this is pretty old, but I mis-spoke in my original post on this.  At the time I had ConfigMgr 2012 SP1 CU2.  Of course today I am running ConfigMgr 1602

    David Grand

    Wednesday, May 11, 2016 2:47 PM
  • Many organizations have software that can not be deployed using SCCM so a model computer with this software has to be created then an image of that computer has to be captured into SCCM for deployment.

    WD

    Friday, August 26, 2016 5:28 PM
  • That's a rare exception. With a little effort, just about anything can be automated.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, August 27, 2016 8:36 PM
  • in 1607 these apps were deleted, but was added the new one - Windows Maps:

    Get-AppxPackage -name "Microsoft.WindowsMaps" | Remove-AppxPackage
    Monday, September 19, 2016 1:31 PM
  • Thank you!! This fixed my issue.
    Wednesday, October 12, 2016 7:02 PM