locked
MDT 8443 Capture Task Bombs on Sysprep Step (screen shot, logs included) RRS feed

  • Question

  • I recently upgraded our MDT server to version 8443 and ADK 1703 in order to start capturing and deploying Windows 10 to our computers. Up until then I only deployed Windows 7 images. After upgrading I can capture and deploy my Windows 7 images with no problems. 

    Now I am trying to capture a Windows 10 Pro 64bit image from a VMWare VM, same way I capture my Win 7 Pro 32 & 64bit images. I have not created a new Capture Task Sequence, I am using one of the old ones in the MDT Capture An Image Tasks list. When I tried the first time it bombed on my network connection because it looked like I forgot to add Win PE 10 NIC drivers to my WinPE OOB, so I added these. Now I am trying to capture it for the second time and MDT splashed the big ugly salmon screen below. Reading it I cannot determine what the problem is. I included the 2 log files it references.

    Note: the VM I am attempting to capture is customized. We removed/uninstalled several of the built-in Windows 10 apps.  We had to join it to our domain to install and test certain desktop applications we use which also meant we logged into this VM with our AD accounts.  I dis-joined it from the domain and deleted the local AD account profiles when we were ready to capture.  

    Any help you can offer is much appreciated. At this point I am stuck as far as imaging Windows 10 is concerned.

    BDD.LOG

    Re-armed Office 2010 successfully. LTISysprep 7/14/2017 9:53:38 AM 0 (0x0000)
    Copying C:\MININT\Unattend.xml to C:\Windows\system32\sysprep\unattend.xml LTISysprep 7/14/2017 9:53:38 AM 0 (0x0000)
    About to run command: C:\Windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /quit /unattend:C:\Windows\system32\sysprep\unattend.xml LTISysprep 7/14/2017 9:53:39 AM 0 (0x0000)
    Command has been started (process ID 4504) LTISysprep 7/14/2017 9:53:39 AM 0 (0x0000)
    Return code from command = 0 LTISysprep 7/14/2017 9:53:40 AM 0 (0x0000)
    Image state after sysprep: IMAGE_STATE_COMPLETE LTISysprep 7/14/2017 9:53:40 AM 0 (0x0000)
    Expected image state is IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE, actual image state is IMAGE_STATE_COMPLETE, sysprep did not succeed. LTISysprep 7/14/2017 9:53:40 AM 0 (0x0000)
    FAILURE ( 6192 ): ERROR - Sysprep did not complete successfully, check C:\Windows\system32\sysprep\panther\setupact.log for details LTISysprep 7/14/2017 9:53:40 AM 0 (0x0000)
    Removing AutoAdminLogon registry entries LTICleanup 7/14/2017 9:53:41 AM 0 (0x0000)
    Re-enabling UAC for built-in Administrator account LTICleanup 7/14/2017 9:53:41 AM 0 (0x0000)
    VSSMaxSize not specified using 5% of volume. LTICleanup 7/14/2017 9:53:41 AM 0 (0x0000)
    Logs contained 11 errors and 2 warnings. LTICleanup 7/14/2017 9:53:41 AM 0 (0x0000)
    Checking mapped network drive. LTICleanup 7/14/2017 9:53:41 AM 0 (0x0000)
    testing drive  mapped to \\s2h\lti$ LTICleanup 7/14/2017 9:53:41 AM 0 (0x0000)
    Disconnecting drive  mapped to \\s2h\lti$ LTICleanup 7/14/2017 9:53:42 AM 0 (0x0000)
    FAILURE: 1: Run command: NET USE  /d /y LTICleanup 7/14/2017 9:53:42 AM 0 (0x0000)
    testing drive Z: mapped to \\s2h\lti$ LTICleanup 7/14/2017 9:53:42 AM 0 (0x0000)
    Disconnecting drive Z: mapped to \\s2h\lti$ LTICleanup 7/14/2017 9:53:42 AM 0 (0x0000)
    testing drive Y: mapped to \\s2h\lti$ LTICleanup 7/14/2017 9:53:42 AM 0 (0x0000)
    Disconnecting drive Y: mapped to \\s2h\lti$ LTICleanup 7/14/2017 9:53:42 AM 0 (0x0000)
    Cleaning up C:\MININT directory. LTICleanup 7/14/2017 9:53:42 AM 0 (0x0000)
    Cleaning up TOOLS, SCRIPTS, and PACKAGES directories. LTICleanup 7/14/2017 9:53:42 AM 0 (0x0000)
    Removing C:\MININT folder (final log entry) LTICleanup 7/14/2017 9:53:42 AM 0 (0x0000)


    ------------------------------------------------------------------------------------------------------------
    SETUPACT.LOG

    The ERROR lines right at the bottom are highlighted in red in CMTRACE and seem to indicate the problem. I also included SETUPERR.LOG which contains some of the same lines.
    SETUPACT.LOG
    2017-07-13 09:28:17, Info                  SYSPRP ========================================================
    2017-07-13 09:28:17, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2017-07-13 09:28:17, Info                  SYSPRP ========================================================
    2017-07-13 09:28:17, Info       [0x0f004d] SYSPRP The time is now 2017-07-13 09:28:17
    2017-07-13 09:28:17, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\system32\Sysprep\Panther
    2017-07-13 09:28:17, Info       [0x0f0054] SYSPRP ValidatePrivileges:User has required privileges to sysprep machine
    2017-07-13 09:28:18, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\system32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2017-07-13 09:28:18, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'RESPECIALIZE'
    2017-07-13 09:28:18, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIET'
    2017-07-13 09:28:19, Info                  SYSPRP WinMain:Processing 're-specialize' internal provider request.
    2017-07-13 09:28:19, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 6
    2017-07-13 09:28:19, Info       [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\ReSpecialize.xml, and mode <null>
    2017-07-13 09:28:22, Info                  SYSPRP SysprepSession::Execute: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\ReSpecialize.xml
    2017-07-13 09:28:22, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-13 09:28:22, Info                  SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-13 09:28:22, Warning               SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2
    2017-07-13 09:28:22, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2017-07-13 09:28:22, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2017-07-13 09:28:22, Info                  SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2017-07-13 09:28:22, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2017-07-13 09:28:22, Info                  SYSPRP SysprepSession::ExecuteInternal: After sorting, providers will be excuted in this order:
    2017-07-13 09:28:22, Info                  SYSPRP SysprepSession::ExecuteInternal: name:Microsoft-Windows-PnpSysprep, order: 100d
    2017-07-13 09:28:22, Info       [0x0f00bd] SYSPRP CreateSysprepActionList: Building action list for component Microsoft-Windows-PnpSysprep
    2017-07-13 09:28:23, Info       [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Respecialize_Pnp' in C:\Windows\System32\sppnp.dll; executing it
    2017-07-13 09:28:23, Info                  SYSPRP SPPNP: Sysprep_Respecialize_Pnp: Enter
    2017-07-13 09:28:23, Info                  SYSPRP SPPNP: Created progress thread.
    2017-07-13 09:28:23, Info                  SYSPRP SPPNP: Creating device install status thread.
    2017-07-13 09:28:23, Info                  SYSPRP SPPNP: Waiting for device install status thread to exit.
    2017-07-13 09:28:23, Info                  SYSPRP SPPNP: Status: Starting...
    2017-07-13 09:28:23, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
    2017-07-13 09:28:23, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
    2017-07-13 09:28:24, Info                  SYSPRP SPPNP: Status: Starting...
    2017-07-13 09:28:24, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
    2017-07-13 09:28:24, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
    2017-07-13 09:28:25, Info                  SYSPRP SPPNP: Waiting for progress thread to exit.
    2017-07-13 09:28:25, Info                  SYSPRP SPPNP: Status: Starting...
    2017-07-13 09:28:26, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
    2017-07-13 09:28:26, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
    2017-07-13 09:28:27, Info                  SYSPRP SPPNP: Status: Starting...
    2017-07-13 09:28:27, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
    2017-07-13 09:28:27, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
    2017-07-13 09:28:28, Info                  SYSPRP SPPNP: Status: Starting...
    2017-07-13 09:28:28, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
    2017-07-13 09:28:28, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
    2017-07-13 09:28:29, Info                  SYSPRP SPPNP: Status: Starting...
    2017-07-13 09:28:29, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
    2017-07-13 09:28:29, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
    2017-07-13 09:28:30, Info                  SYSPRP SPPNP: Status: Starting...
    2017-07-13 09:28:30, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
    2017-07-13 09:28:30, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
    2017-07-13 09:28:31, Info                  SYSPRP SPPNP: Status: Idle
    2017-07-13 09:28:31, Info                  SYSPRP SPPNP: Finished waiting for device install status.
    2017-07-13 09:28:31, Info                  SYSPRP SPPNP: Progress thread exited.
    2017-07-13 09:28:31, Info                  SYSPRP SPPNP: Sysprep_Respecialize_Pnp: Exit
    2017-07-13 09:28:31, Info       [0x0f0081] SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Respecialize_Pnp' from C:\Windows\System32\sppnp.dll without error
    2017-07-13 09:28:31, Info       [0x0f00b8] SYSPRP SysprepSession::Execute: Sysprep mode was not specified, deleting it from registry
    2017-07-13 09:28:31, Info       [0x0f00c6] SYSPRP ActionPlatform::DeleteValue: Deleting registry value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-13 09:28:31, Warning               SYSPRP ActionPlatform::DeleteValue: Registry value SysprepMode to be deleted does not exist under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-13 09:28:31, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2017-07-13 09:28:31, Info       [0x0f004d] SYSPRP The time is now 2017-07-13 09:28:31
    2017-07-13 16:18:33, Info                  SYSPRP ========================================================
    2017-07-13 16:18:33, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2017-07-13 16:18:33, Info                  SYSPRP ========================================================
    2017-07-13 16:18:33, Info       [0x0f004d] SYSPRP The time is now 2017-07-13 16:18:33
    2017-07-13 16:18:33, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\system32\Sysprep\Panther
    2017-07-13 16:18:33, Info       [0x0f0054] SYSPRP ValidatePrivileges:User has required privileges to sysprep machine
    2017-07-13 16:18:33, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\system32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2017-07-13 16:18:33, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'RESPECIALIZE'
    2017-07-13 16:18:33, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIET'
    2017-07-13 16:18:33, Info                  SYSPRP WinMain:Processing 're-specialize' internal provider request.
    2017-07-13 16:18:33, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 6
    2017-07-13 16:18:33, Info       [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\ReSpecialize.xml, and mode <null>
    2017-07-13 16:18:34, Info                  SYSPRP SysprepSession::Execute: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\ReSpecialize.xml
    2017-07-13 16:18:34, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-13 16:18:34, Info                  SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-13 16:18:34, Warning               SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2
    2017-07-13 16:18:34, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2017-07-13 16:18:34, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2017-07-13 16:18:34, Info                  SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2017-07-13 16:18:34, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2017-07-13 16:18:34, Info                  SYSPRP SysprepSession::ExecuteInternal: After sorting, providers will be excuted in this order:
    2017-07-13 16:18:34, Info                  SYSPRP SysprepSession::ExecuteInternal: name:Microsoft-Windows-PnpSysprep, order: 100d
    2017-07-13 16:18:34, Info       [0x0f00bd] SYSPRP CreateSysprepActionList: Building action list for component Microsoft-Windows-PnpSysprep
    2017-07-13 16:18:35, Info       [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Respecialize_Pnp' in C:\Windows\System32\sppnp.dll; executing it
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Sysprep_Respecialize_Pnp: Enter
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Created progress thread.
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Creating device install status thread.
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Waiting for device install status thread to exit.
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Status worker: Waiting for service to start.
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Waiting for progress thread to exit.
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Status: Idle
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Finished waiting for device install status.
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Progress thread exited.
    2017-07-13 16:18:35, Info                  SYSPRP SPPNP: Sysprep_Respecialize_Pnp: Exit
    2017-07-13 16:18:35, Info       [0x0f0081] SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Respecialize_Pnp' from C:\Windows\System32\sppnp.dll without error
    2017-07-13 16:18:35, Info       [0x0f00b8] SYSPRP SysprepSession::Execute: Sysprep mode was not specified, deleting it from registry
    2017-07-13 16:18:35, Info       [0x0f00c6] SYSPRP ActionPlatform::DeleteValue: Deleting registry value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-13 16:18:35, Warning               SYSPRP ActionPlatform::DeleteValue: Registry value SysprepMode to be deleted does not exist under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-13 16:18:35, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2017-07-13 16:18:35, Info       [0x0f004d] SYSPRP The time is now 2017-07-13 16:18:35
    2017-07-14 09:53:39, Info                  SYSPRP ========================================================
    2017-07-14 09:53:39, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2017-07-14 09:53:39, Info                  SYSPRP ========================================================
    2017-07-14 09:53:39, Info       [0x0f004d] SYSPRP The time is now 2017-07-14 09:53:39
    2017-07-14 09:53:39, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\system32\sysprep\Panther
    2017-07-14 09:53:39, Info       [0x0f0054] SYSPRP ValidatePrivileges:User has required privileges to sysprep machine
    2017-07-14 09:53:39, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2017-07-14 09:53:39, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIET'
    2017-07-14 09:53:39, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'
    2017-07-14 09:53:39, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'
    2017-07-14 09:53:39, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIT'
    2017-07-14 09:53:39, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND'
    2017-07-14 09:53:39, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.
    2017-07-14 09:53:39, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3
    2017-07-14 09:53:39, Info       [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null>
    2017-07-14 09:53:39, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml
    2017-07-14 09:53:39, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-14 09:53:39, Info                  SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2017-07-14 09:53:39, Warning               SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2
    2017-07-14 09:53:39, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2017-07-14 09:53:39, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2017-07-14 09:53:39, Info                  SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2017-07-14 09:53:39, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2017-07-14 09:53:39, Info       [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Clean_Validate_Opk' in C:\Windows\System32\spopk.dll; executing it
    2017-07-14 09:53:39, Info       [0x0f0081] SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll without error
    2017-07-14 09:53:39, Inf

    __________________________________________________________________________________________________

    SETUPERR.LOG


    2017-07-14 09:53:39, Error                 SYSPRP Package Microsoft.Messaging_3.26.24002.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
    2017-07-14 09:53:39, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.
    2017-07-14 09:53:39, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
    2017-07-14 09:53:39, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
    2017-07-14 09:53:39, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
    2017-07-14 09:53:39, Error                 SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x3cf2
    2017-07-14 09:53:39, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
    2017-07-14 09:53:39, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2






    Friday, July 14, 2017 3:37 PM

All replies

  • I was getting the same error messages and my issue was caused by me removing the Windows Apps.  I had to go about removing them a different way.  Not sure if that is your issue but worth a shot.

    I ended up having to use the steps in the comments from the blog here: https://blogs.technet.microsoft.com/mniehaus/2016/08/23/windows-10-1607-keeping-apps-from-coming-back-when-deploying-the-feature-update/

    Friday, July 14, 2017 4:50 PM
  • Thank you for your response WhovianTim12.  This seems pretty complicated. Which steps in Mike Niehaus' post did you end up using and can you explain with a little more detail how you resolved this issue?   Was this occurring when you attempted to Capture your image?  

    Lynchburg Mike


    Friday, July 14, 2017 5:19 PM
  • It looks like this article describes the exact message generated in the setuperr.log file:


    Sysprep fails after you remove or update Windows Store apps that include built-in Windows images

    Summary

    This article discusses an issue that occurs when you remove or update a provisioned Windows Store app by using the Windows Store and then running sysprep on the computer.

    Sysprep is a tool for IT administrators who want to prepare an installation of Windows for duplication, auditing, and customer delivery. The guidance in this article is intended for use by support agents and IT professionals. If you are a home user who is encountering issues while using Windows Store apps, see the following Windows websites:

    Friday, July 14, 2017 7:23 PM
  • Did you attempt to remove built-in/in-box Windows 10 apps during built and capture by running some form of PowerShell script?  As Tim has already pointed out this will most likely cause the sysprep process to fail.  Based on my experience I would suggest running the PowerShell script (one that strips out the built-in apps) during build and deploy rather than the build and capture.  Additionally, there's also a PowerShell script that allows you to mount the WIM you just captured and remove it using dism:

    https://gallery.technet.microsoft.com/Removing-Built-in-apps-65dc387b

    Jeff

    Sunday, July 16, 2017 5:21 PM
  • This error can also be caused if Windows is installing or updating apps during Sysprep. If that is the case, this guide could be helpful - https://deploymentresearch.com/Research/Post/615/Fixing-why-Sysprep-fails-in-Windows-10-due-to-Windows-Store-updates
    • Edited by Balterz Monday, July 17, 2017 11:38 AM
    Monday, July 17, 2017 11:25 AM
  •    Thank you Jeff,  yes, we used similar Powershell commands mentioned in that article to remove the apps BEFORE capturing it. We built a VM using VMWare then removed the apps from it, then upon Capture received the big ugly error message.

      My colleagues and I were discussing the idea you mention last Friday after reading WhovianTims' response and the Niehaus post he referenced.  We were thinking the same thing, remove the apps AFTER deploying the image or if we can figure out how to remove them in the Add Applications step in the task sequence we might do it that way.

       We also use a tool called PDQ Deploy to install/push applications and settings remotely to domain computers. We may be able to use this tool to remove them too, we've just never done that before nor had a need to.



    Monday, July 17, 2017 1:23 PM