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 /quitPrepareOS11/23/2015 12:12:07 PM4184 (0x1058)
Process completed with exit code 0PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Sysprep state set to IMAGE_STATE_COMPLETEPrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
The OS has not been generalized using sysprep.exe, or sysprep did not complete.PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
bSysPreped, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,514)PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Sysprep did not complete successfullyPrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
RunSysprep(sCmdLine, bActivate, m_bDebug), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1375)PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Unable to sysprep the machine, hr=80004005PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
pCmd->Sysprep(bActivate, bMsd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\main.cpp,270)PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Sysprep'ing the machine failed, hr=80004005
PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
De-Initialization successfulPrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Exiting with error code 16389PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Process completed with exit code 16389TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
!--------------------------------------------------------------------------------------------!TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Could not find CCM install folder. Don't use ccmerrors.dllTSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Failed to run the action: Prepare Operating System.
Unknown error (Error: 00004005; Source: Unknown)
TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Do not send status message in full media case
TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Set a global environment variable _SMSTSLastActionRetCode=16389TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Set a global environment variable _SMSTSLastActionSucceeded=falseTSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Clear local default environmentTSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Let the parent group (Capture the Reference Machine) decides whether to continue executionTSManager11/23/2015 12:12:08 PM4088 (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)TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Could not find CCM install folder. Don't use ccmerrors.dllTSManager11/23/2015 12:12:08 PM4088 (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