none
Windows 10 1803 Pro + sysprep issues?

    Question

  • I'm trying to capture the latest Windows 10 1803 Professional, and I'm receiving errors when it tries to sysprep. I've tried a number of different troubleshooting techniques that were required for the older versions, but none which have worked so far.

    MDT Error:

    2018-05-08 11:30:04, Info                  SYSPRP ========================================================
    2018-05-08 11:30:04, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2018-05-08 11:30:04, Info                  SYSPRP ========================================================
    2018-05-08 11:30:04, Info       [0x0f004d] SYSPRP The time is now 2018-05-08 11:30:04
    2018-05-08 11:30:04, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\WINDOWS\system32\sysprep\Panther
    2018-05-08 11:30:04, Info       [0x0f0054] SYSPRP ValidatePrivileges:User has required privileges to sysprep machine
    2018-05-08 11:30:04, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\WINDOWS\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2018-05-08 11:30:04, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIET'
    2018-05-08 11:30:04, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'
    2018-05-08 11:30:04, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'
    2018-05-08 11:30:04, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIT'
    2018-05-08 11:30:04, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND'
    2018-05-08 11:30:04, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.
    2018-05-08 11:30:04, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3
    2018-05-08 11:30:04, Info                  SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null>
    2018-05-08 11:30:05, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml
    2018-05-08 11:30:05, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2018-05-08 11:30:05, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2018-05-08 11:30:05, Info                  SYSPRP ActionPlatform::LaunchModule: Executing method 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll
    2018-05-08 11:30:05, Info                  SYSPRP Sysprep_Clean_Validate_Opk:Sysprep will run on an upgraded OS.
    2018-05-08 11:30:05, Info                  SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll without error
    2018-05-08 11:30:05, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'generalize' internal providers.
    2018-05-08 11:30:05, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 1
    2018-05-08 11:30:05, Info                  SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml, and mode <null>
    2018-05-08 11:30:05, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml
    2018-05-08 11:30:05, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2018-05-08 11:30:05, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2018-05-08 11:30:05, Info                  SYSPRP ActionPlatform::LaunchModule: Executing method 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll
    2018-05-08 11:30:05, Info                  SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.

    2018-05-08 11:30:05, Error                 SYSPRP Package Microsoft.Windows.SecondaryTileExperience_10.0.0.0_neutral__cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

    2018-05-08 11:30:05, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

    2018-05-08 11:30:05, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

    2018-05-08 11:30:05, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
    2018-05-08 11:30:05, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
    2018-05-08 11:30:05, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
    2018-05-08 11:30:05, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
    2018-05-08 11:30:05, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2
    2018-05-08 11:30:05, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2018-05-08 11:30:05, Info       [0x0f004d] SYSPRP The time is now 2018-05-08 11:30:05

    ---------

    Anyone able to advise what's going on? I couldn't see the application when looking at appxpackage, or appxprovisionedpackages


    Tuesday, May 08, 2018 1:39 PM

All replies

  • This is not a 1803 specific issue, but rather something you need to be aware of when dealing with W10 ref images. As I am on the road right now I am not going to go various issues surrounding Windows Store auto update functionality and will link Michael‘s blog post instead: https://blogs.technet.microsoft.com/mniehaus/2018/04/17/cleaning-up-apps-to-keep-windows-10-sysprep-happy/ (plus he explained it in great detail anyway and offered potential workarounds.)

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Tuesday, May 08, 2018 4:07 PM
  • I have the exact same error. With other builds in the past I've just removed the offending app using powershell Remove-AppxPackage. However it appears this is an app that Microsoft doesn't let you remove. I rolled my image back to a snapshot I took before upgrading to 1803 and sysprep works fine. 
    Tuesday, May 08, 2018 4:53 PM
  • I know it is supposed to be a supported scenario (i.e. upgrading a reference image), but based on my experiences in the field I would advise against it. There are a few different way to automate image creation (and if you are using MDT in combination with HideShell=YES, store auto update routine never kicks in). If automating (for whatever reason) is not an option, you should consider blocking internet access for the duration of the upgrade using a PowerShell script (there is also a policy that blocks auto updates, but it works only on Ent / Edu editions).

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Wednesday, May 09, 2018 11:20 AM
  • Try this. It worked for me! Follow the steps and change the app name. 

    http://alexappleton.net/post/159702702033/windows-10-pro-remove-wireless-display-media

    Monday, May 14, 2018 11:22 AM
  • It works for me too.
    Wednesday, May 16, 2018 8:52 AM
  • Just a guess... did you remove provisioned apps from either the original image or the upgrade media? I'm seeing the same thing. If I carefully play with 1709 with all provisioned apps installed and upgrade it to 1803, I can then get sysprep to complete without reporting this error.

    However, even if you do get it to succeed, it may be relatively pointless. Sysprep wreaks havoc on appx based applications, particularly after an upgrade. On my 1709->1803 sysprepped image, several apps are not present, even for new users. One example is Microsoft.Windows.ParentalControls - a system app, not even a provisioned app. It's just gone.

    There are lots of posts and blogs and workarounds folks offer, but they all are just putting lipstick on the appx + sysprep pig.

    Wednesday, May 16, 2018 9:53 PM