locked
sysprep fatal error

    Question

  • This type of error code is new for me. Any suggestion? Windows 8.1 en-us with Windows Update and .Net 3.x, syspreped with OOBE and Generalize options:

    2013-07-01 13:50:30, Error                 SYSPRP Could not re-arm region selection, some files and registry keys are no longer recoverable.
    2013-07-01 13:50:30, Error                 SYSPRP Re-arm region selection failed with hr = 0x8000ffff.

    2013-07-01 13:50:30, Error                 SYSPRP Failed to re-arm region selection: 0x8000ffff.

    2013-07-01 13:50:30, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralize' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x8000ffff
    2013-07-01 13:50:30, Error                 SYSPRP ActionPlatform::ExecuteAction: Error in executing action; dwRet = 0x8000ffff
    2013-07-01 13:50:30, Error                 SYSPRP ActionPlatform::ExecuteActionList: Error in execute actions; dwRet = 0x8000ffff
    2013-07-01 13:50:30, Error                 SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x8000ffff
    2013-07-01 13:50:30, Error                 SYSPRP RunPlatformActions:Failed while executing SysprepSession actions; dwRet = 0x8000ffff
    2013-07-01 13:50:30, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x8000ffff
    2013-07-01 13:50:30, Error      [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0x8000ffff

    Monday, July 01, 2013 9:03 PM

Answers

  • SOLVED! This is a know issue:

    http://technet.microsoft.com/en-us/library/dn303413.aspx


    If you attempt to run Sysprep.exe to create a WIM image more than one hour after the first user has logged on to the newly installed operating system, Sysprep.exe will fail. A scheduled maintenance task that recovers disk space by removing unused features is the cause.

    To avoid this, disable the maintenance task immediately after completing Setup. You can disable the task with this command:

    Schtasks.exe /change /disable /tn "\Microsoft\Windows\AppxDeploymentClient\Pre-staged app cleanup"

    Monday, July 01, 2013 10:26 PM

All replies

  • SOLVED! This is a know issue:

    http://technet.microsoft.com/en-us/library/dn303413.aspx


    If you attempt to run Sysprep.exe to create a WIM image more than one hour after the first user has logged on to the newly installed operating system, Sysprep.exe will fail. A scheduled maintenance task that recovers disk space by removing unused features is the cause.

    To avoid this, disable the maintenance task immediately after completing Setup. You can disable the task with this command:

    Schtasks.exe /change /disable /tn "\Microsoft\Windows\AppxDeploymentClient\Pre-staged app cleanup"

    Monday, July 01, 2013 10:26 PM
  • I attempted to run sysprep after a fresh install.  needless to say it failed, after a bit of scouting around I seen this post, attempted to run the command (which was successful) but am still experiencing the same error.

    See the original log below:

    ----------------------------------------------------------------------------------------------------

    2013-08-03 18:39:25, Error                 SYSPRP Package 35135TwoGuysandaApp.FacebookNow_1.0.0.12_neutral__xc3b11gcg8yyg was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

    2013-08-03 18:39:25, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

    2013-08-03 18:39:25, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

    2013-08-03 18:39:25, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralize' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
    2013-08-03 18:39:25, Error                 SYSPRP ActionPlatform::ExecuteAction: Error in executing action; dwRet = 0x3cf2
    2013-08-03 18:39:25, Error                 SYSPRP ActionPlatform::ExecuteActionList: Error in execute actions; dwRet = 0x3cf2
    2013-08-03 18:39:25, Error                 SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
    2013-08-03 18:39:25, Error                 SYSPRP RunPlatformActions:Failed while executing SysprepSession actions; dwRet = 0x3cf2
    2013-08-03 18:39:25, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
    2013-08-03 18:39:25, Error      [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0x80073cf2
    2013-08-03 18:41:22, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
    2013-08-03 18:41:22, Error      [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f
    2013-08-03 18:45:57, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
    2013-08-03 18:45:57, Error                 SYSPRP WinMain:Hit failure while processing sysprep re-specialize internal providers; hr = 0x8007001f
    2013-08-03 19:04:11, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
    2013-08-03 19:04:11, Error      [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f
    2013-08-03 19:05:22, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
    2013-08-03 19:05:22, Error      [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f
    2013-08-03 19:07:23, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
    2013-08-03 19:07:23, Error      [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f

    ----------------------------------------------------------------------------------------------------

    That's after running it a few times, each subsequent attempt to run sysprep (after running the command specified in the previous post) i get the following errors:

    ----------------------------------------------------------------------------------------------------

    2013-08-03 19:20:49, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
    2013-08-03 19:20:49, Error      [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f

    ----------------------------------------------------------------------------------------------------

    Any help is greatly appreciated!  Thanks in advance.

    Levi



    • Edited by lenmeier Sunday, August 04, 2013 12:11 AM
    Saturday, August 03, 2013 11:25 PM
  • @lenmeier, I had this problem as well. Despite this question being already answered, I thought I'd chime in, maybe it'll help you. Here's what I did:

    1. Ran (note: CopyProfile was set to true):

    sysprep /generalize /oobe /shutdown /unattend:<pathToAnswerFile>

    2. Ran into another error
    3. Read the sysprep logs, fired up Powershell, queried for the problematic package in question by running (note: insert the name of the package that's causing problems, in your case it starts with "TwoGuysandaApp.FacebookNow")

    Get-AppxPackage -AllUsers | Where Name -Like ""

    4. Once found, took it a step further and ran:

    Get-AppxPackage -AllUsers | Where Name -Like "" | Remove-AppxPackage

    5. Repeated Steps 1-4 until it successfully went through Generalize.

    Now, in my case, I only ran into 2 errors, which both created the dreaded "0x80073cf2" error in the sysprep logs. The names of those packages as I typed them into Powershell (to the right of "-Like", between the double quotes) were:

    1. Microsoft.WinJS.2.0.Preview
    2. Microsoft.WinJS.Preview

    Both trace back to the v2 and v1, respectively, WinJS preview packages.

    I'm running my Win 8.1 builds in Hyper-V and took snapshots prior to running sysprep, so it really didn't take me very long to get back to a safe point and attempt Generalize once more.

    I highly prefer this method over the (IMO) elephant gun approach of uninstalling all packages that some sites have mentioned (i.e. 'Get-AppxPackage | Remove-AppxPackage')

    This was done with Win 8.1 Enterprise, RTM.

    Wednesday, October 16, 2013 10:12 PM