none
Sysprep Error with windows 8.1 RRS feed

  • Question

  • I am Trying to sysprep my WIndows 8.1 enterprise (MSDN) and i get the following errors 

    2013-01-18 11:12:22, Info                  SYSPRP ========================================================
    2013-01-18 11:12:22, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2013-01-18 11:12:22, Info                  SYSPRP ========================================================
    2013-01-18 11:12:22, Info       [0x0f004d] SYSPRP The time is now 2013-01-18 11:12:22
    2013-01-18 11:12:22, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\System32\Sysprep\Panther
    2013-01-18 11:12:22, Info       [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine
    2013-01-18 11:12:22, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\System32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2013-01-18 11:12:22, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'
    2013-01-18 11:12:22, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'
    2013-01-18 11:12:22, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'SHUTDOWN'
    2013-01-18 11:12:22, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND'
    2013-01-18 11:12:23, Info                  SYSPRP WinMain: CBS operations pending
    2013-01-18 11:15:55, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2013-01-18 11:15:55, Info       [0x0f004d] SYSPRP The time is now 2013-01-18 11:15:55
    2013-01-24 17:54:22, Info                  SYSPRP ========================================================
    2013-01-24 17:54:22, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2013-01-24 17:54:22, Info                  SYSPRP ========================================================
    2013-01-24 17:54:22, Info       [0x0f004d] SYSPRP The time is now 2013-01-24 17:54:22
    2013-01-24 17:54:22, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\system32\Sysprep\Panther
    2013-01-24 17:54:22, Info       [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine
    2013-01-24 17:54:22, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\system32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2013-01-24 17:54:22, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'RESPECIALIZE'
    2013-01-24 17:54:22, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIET'
    2013-01-24 17:54:22, Info                  SYSPRP WinMain:Processing 're-specialize' internal provider request.
    2013-01-24 17:54:22, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 6
    2013-01-24 17:54:22, Info       [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\ReSpecialize.xml, and mode <null>
    2013-01-24 17:54:23, Info                  SYSPRP SysprepSession::Execute: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\ReSpecialize.xml
    2013-01-24 17:54:23, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2013-01-24 17:54:23, Info                  SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2013-01-24 17:54:23, Warning               SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2
    2013-01-24 17:54:23, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2013-01-24 17:54:23, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2013-01-24 17:54:23, Info                  SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2013-01-24 17:54:23, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2013-01-24 17:54:23, Info       [0x0f00bd] SYSPRP CreateSysprepActionList: Building action list for component Microsoft-Windows-PnpSysprep
    2013-01-24 17:54:24, Info       [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Respecialize_Pnp' in C:\Windows\System32\sppnp.dll; executing it
    2013-01-24 17:54:24, Info                  SYSPRP SPPNP: Sysprep_Respecialize_Pnp: Enter
    2013-01-24 17:54:24, Info                  SYSPRP SPPNP: Created progress thread.
    2013-01-24 17:54:24, Info                  SYSPRP SPPNP: Creating device install status thread...
    2013-01-24 17:54:24, Info                  SYSPRP SPPNP: Waiting for thread to exit...
    2013-01-24 17:54:24, Info                  SYSPRP SPPNP: Waiting for thread to exit.
    2013-01-24 17:54:43, Info                  SYSPRP SPPNP: Status: Starting...
    2013-01-24 17:54:43, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
    2013-01-24 17:54:43, Info                  SYSPRP SPPNP: Status: Active
    2013-01-24 17:54:43, Info                  SYSPRP SPPNP: Status: Total = 1, Complete = 0, Progress = 0% (0%)
    2013-01-24 17:54:49, Info                  SYSPRP SPPNP: Status: End
    2013-01-24 17:54:49, Info                  SYSPRP SPPNP: Status: Total = -1, Complete = -1, Progress = 100% (100%)
    2013-01-24 17:54:49, Info                  SYSPRP SPPNP: Finished waiting for device install status...
    2013-01-24 17:54:49, Info                  SYSPRP SPPNP: Thread exited.
    2013-01-24 17:54:49, Info                  SYSPRP SPPNP: Sysprep_Respecialize_Pnp: Exit
    2013-01-24 17:54:49, Info       [0x0f0081] SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Respecialize_Pnp' from C:\Windows\System32\sppnp.dll without error
    2013-01-24 17:54:49, Info       [0x0f00b8] SYSPRP SysprepSession::Execute: Sysprep mode was not specified, deleting it from registry
    2013-01-24 17:54:49, Info       [0x0f00c6] SYSPRP ActionPlatform::DeleteValue: Deleting registry value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2013-01-24 17:54:49, Warning               SYSPRP ActionPlatform::DeleteValue: Registry value SysprepMode to be deleted does not exist under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2013-01-24 17:54:49, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2013-01-24 17:54:49, Info       [0x0f004d] SYSPRP The time is now 2013-01-24 17:54:49
    2013-06-13 17:23:46, Info                  SYSPRP ========================================================
    2013-06-13 17:23:46, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2013-06-13 17:23:46, Info                  SYSPRP ========================================================
    2013-06-13 17:23:46, Info       [0x0f004d] SYSPRP The time is now 2013-06-13 17:23:46
    2013-06-13 17:23:46, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\System32\Sysprep\Panther
    2013-06-13 17:23:46, Info       [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine
    2013-06-13 17:23:46, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\System32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2013-06-13 17:23:46, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'
    2013-06-13 17:23:46, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'
    2013-06-13 17:23:46, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'SHUTDOWN'
    2013-06-13 17:23:46, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND'
    2013-06-13 17:23:50, Info                  SYSPRP WinMain: CBS operations pending
    2013-06-13 17:23:59, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2013-06-13 17:23:59, Info       [0x0f004d] SYSPRP The time is now 2013-06-13 17:23:59
    2013-10-08 18:39:40, Info                  SYSPRP ========================================================
    2013-10-08 18:39:40, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2013-10-08 18:39:40, Info                  SYSPRP ========================================================
    2013-10-08 18:39:40, Info       [0x0f004d] SYSPRP The time is now 2013-10-08 18:39:40
    2013-10-08 18:39:40, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\System32\Sysprep\Panther
    2013-10-08 18:39:41, Info       [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine
    2013-10-08 18:39:41, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\System32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2013-10-08 18:39:41, Warning               SYSPRP WinMain: File operations pending
    2013-10-08 18:39:41, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'
    2013-10-08 18:39:41, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'
    2013-10-08 18:39:41, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'SHUTDOWN'
    2013-10-08 18:39:41, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND'
    2013-10-08 18:39:41, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.
    2013-10-08 18:39:41, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3
    2013-10-08 18:39:41, Info       [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null>
    2013-10-08 18:39:41, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml
    2013-10-08 18:39:41, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2013-10-08 18:39:41, Info                  SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2013-10-08 18:39:41, Warning               SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2
    2013-10-08 18:39:41, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2013-10-08 18:39:41, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2013-10-08 18:39:41, Info                  SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2013-10-08 18:39:41, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2013-10-08 18:39:41, Info       [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Clean_Validate_Opk' in C:\Windows\System32\spopk.dll; executing it
    2013-10-08 18:39:41, Error      [0x0f0036] SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.
    2013-10-08 18:39:41, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll; dwRet = 0x139f
    2013-10-08 18:39:41, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml; dwRet = 0x139f
    2013-10-08 18:39:41, Error                 SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x139f
    2013-10-08 18:39:41, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x139f
    2013-10-08 18:39:41, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep cleanup internal providers; hr = 0x8007139f
    2013-10-08 18:39:58, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2013-10-08 18:39:58, Info       [0x0f004d] SYSPRP The time is now 2013-10-08 18:39:58
    2013-10-08 18:48:08, Info                  SYSPRP ========================================================
    2013-10-08 18:48:08, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2013-10-08 18:48:08, Info                  SYSPRP ========================================================
    2013-10-08 18:48:08, Info       [0x0f004d] SYSPRP The time is now 2013-10-08 18:48:08
    2013-10-08 18:48:08, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\System32\Sysprep\Panther
    2013-10-08 18:48:08, Info       [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine
    2013-10-08 18:48:08, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\System32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2013-10-08 18:48:08, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'
    2013-10-08 18:48:08, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'
    2013-10-08 18:48:08, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'SHUTDOWN'
    2013-10-08 18:48:08, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND'
    2013-10-08 18:48:08, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.
    2013-10-08 18:48:08, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3
    2013-10-08 18:48:08, Info       [0x0f00ba] SYSPRP SysprepSession::CreateSession: Successfully created instance with mount path C:, action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null>
    2013-10-08 18:48:08, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml
    2013-10-08 18:48:08, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2013-10-08 18:48:08, Info                  SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
    2013-10-08 18:48:08, Warning               SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2
    2013-10-08 18:48:08, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2013-10-08 18:48:08, Info                  SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2013-10-08 18:48:08, Info                  SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
    2013-10-08 18:48:08, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2013-10-08 18:48:08, Info       [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Clean_Validate_Opk' in C:\Windows\System32\spopk.dll; executing it
    2013-10-08 18:48:08, Error      [0x0f0036] SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.
    2013-10-08 18:48:08, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll; dwRet = 0x139f
    2013-10-08 18:48:08, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml; dwRet = 0x139f
    2013-10-08 18:48:08, Error                 SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x139f
    2013-10-08 18:48:08, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x139f
    2013-10-08 18:48:08, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep cleanup internal providers; hr = 0x8007139f
    2013-10-08 18:53:32, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2013-10-08 18:53:32, Info       [0x0f004d] SYSPRP The time is now 2013-10-08 18:53:32

    Its a Windows error 


    Tuesday, October 8, 2013 1:30 PM

Answers

  • So finally I was able to find the answer, it all lies within a single registry key:

    HKEY_LOCAL_MACHINE\system\setup

    There was a key called “upgrade”, that once deleted lets you run SysPrep like normal.

    Delete that key and you are good.

    Set HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus to 7
    Run sysprep again as Admin, It's finally work for me
    Wednesday, October 23, 2013 9:21 AM
  • Hello,

    Sysprep is not supposed to work on an upgraded system and thus the warning blocking sysprep from running.

    Bypassing this check and allowing sysprep to run could cause future problems if that image is then deployed.  This scenario would be unsupported and thus very risky, if there are any issues, any machines deployed with Image that bypassed the check by modifying a registry key would have to be rebuilt.


    Thanks, Darrell Gorter [MSFT] This posting is provided &quot;AS IS&quot; with no warranties, and confers no rights.

    Monday, October 28, 2013 10:17 PM

All replies

  • the error means incorrect state:

    C:\Users\André>err 0x8007139f
    # as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x139f
    # for hex 0x139f / decimal 5023
      ERROR_INVALID_STATE                                            winerror.h
    # The group or resource is not in the correct state to
    # perform the requested operation.
    # 1 matches found for "0x8007139f"

    this line is confusing:

    2013-10-08 18:48:08, Warning               SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2

    Do you see the value SysprepMode?


    "A programmer is just a tool which converts caffeine into code"

    Tuesday, October 8, 2013 6:51 PM
    Answerer
  • Have you tried to update the built-in Windows store apps before sysprep? See the KB article below, I noted some similar errors to you. I had this occur and chose not to update before sysprep and it worked.

    http://support.microsoft.com/kb/2769827


    • Edited by TechNet-User Wednesday, October 9, 2013 1:43 AM format
    Wednesday, October 9, 2013 1:41 AM
  • Hie 

    I have not applied any updates on any of the winstore metro apps or have installed any app

    I have updated Windows 8 to Windows 8.1 so could that be a reason for that 

    Wednesday, October 9, 2013 3:29 AM
  • What is "value SysprepMode?"
    Wednesday, October 9, 2013 3:30 AM
  • run regedit, go to the key and look if you can find anything with the name SysprepMode.

    "A programmer is just a tool which converts caffeine into code"

    Wednesday, October 9, 2013 5:06 AM
    Answerer
  • Hie,

    Sorry but I am still not getting what is sysprep mode? But if you want the registry value for sysprep status then 

    Cleanupstate = 2

    Generalize state = 7

    Wednesday, October 9, 2013 6:34 AM
  • Hello,  I am experiencing this same issue on a Windows 8 pro in-place upgraded to windows 8.1 pro virtual I'm trying to sysprep as well.    This virtual is not a member of a domain, and I'm logged on as local Administrator.  All windows updates have been installed. 

    Has anyone successfully sysprep'd a windows 8.1 machine yet?

    Tuesday, October 15, 2013 9:36 PM
  • I have searched the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep 

    But i coud'nt find anything for SYSprep mode 

    The value for sysprep was (Value not set)

    Friday, October 18, 2013 5:21 AM
  • I have the same problem with a Widows 8 Pro reference machine that I just upgraded to windows 8.1 Pro. Sysprep worked just fine before the upgrade. After the upgrade, I keep getting the error mentioned here.

    What is the solution?

    Sunday, October 20, 2013 9:22 PM
  • he haven't found a solution. Try the updated ISOs which have the GA Updat Rollup included. Maybe this also fixes this issue.

    "A programmer is just a tool which converts caffeine into code"

    Monday, October 21, 2013 5:23 AM
    Answerer
  • Same problem... I've upgrade to Windows 8.1 and Sysprep don't work ...
    Tuesday, October 22, 2013 7:44 AM
  • This question has not been answered, despite it being marked as answered.

    I have the same issue too going from Windows 8 Enterprise to Windows 8.1 Enterprise as an upgrade.  I have a 65GB image that was only built 2 months ago, and find it ridiculous that it cannot be used to upgrade to 8.1 and take a sysprep.  We are wanting to deploy this image out to our fleet, and were hoping to push it out wit the latest O/S instead. Deleting the registry key under HKLM\Setup\Update didn't help.

    Can someone at Microsoft provide the appropriate solution for this?  I'm not interested in a clean install.
    Wednesday, October 23, 2013 12:43 AM
  • So finally I was able to find the answer, it all lies within a single registry key:

    HKEY_LOCAL_MACHINE\system\setup

    There was a key called “upgrade”, that once deleted lets you run SysPrep like normal.

    Delete that key and you are good.

    Set HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus to 7
    Run sysprep again as Admin, It's finally work for me
    Wednesday, October 23, 2013 9:21 AM
  • Yeah Plain sysprep works but there are some issue with answer file settings that needs to be sorted
    Wednesday, October 23, 2013 11:55 AM
  • Can you advise on your O/S you tested this on Jonathan and Anurag?  I still can't get it working on 8.1 Enterprise after an upgrade.  I've even compared all the settings to a Windows 8 machine that can successfully sysprep, but have no luck.
    Thursday, October 24, 2013 1:55 AM
  • KK so i tested it continuously and it works 2 out of 10 times. So we need a proper Microsoft solution for this not just registry entry  My OS is same as yours Burner1
    Thursday, October 24, 2013 3:23 AM
  • I tested only on Windows 8 Pro by upgrading to 8.1
    Thursday, October 24, 2013 1:17 PM
  • Can you advise on your O/S you tested this on Jonathan and Anurag?  I still can't get it working on 8.1 Enterprise after an upgrade.  I've even compared all the settings to a Windows 8 machine that can successfully sysprep, but have no luck.

    Same here.  I have a base image of 8 Pro that I upgraded using the ISO (which requires a new 8.1 key..unlike trying to upgrade through the windows store which apparently doesn't require a new key (which makes no sense to me).  But anyway, I upgraded using the .ISO manually to 8.1 Pro, and still have the sysprep issue, even after deleting the upgrade key in the registry.   No luck here, haven't even gotten it to work once.
    • Edited by TMLAdmin Thursday, October 24, 2013 2:54 PM
    Thursday, October 24, 2013 2:36 PM
  • Yeah, I hate to pile on this, but I'm in the same boat:

    Windows 8.0 Enterprise updated to Win 8.1 Enterprise (64bit).   No MS applications updated from the Store (ever).

    Same exact problem as the OP.   Deleting the "upgrade" key made no difference and the \SysprepStatus\GeneralizationState value is already set to "7".

    I'm not necessarily surprised this worked for somebody with Pro, but I'm wondering if it's just not supposed to work on an upgraded system at all (as the log indicates) and it's checking for something other than that "upgrade" key...   Or maybe it just does not work on "Enterprise" 8.1...

    Monday, October 28, 2013 6:07 PM
  • Hello,

    Sysprep is not supposed to work on an upgraded system and thus the warning blocking sysprep from running.

    Bypassing this check and allowing sysprep to run could cause future problems if that image is then deployed.  This scenario would be unsupported and thus very risky, if there are any issues, any machines deployed with Image that bypassed the check by modifying a registry key would have to be rebuilt.


    Thanks, Darrell Gorter [MSFT] This posting is provided &quot;AS IS&quot; with no warranties, and confers no rights.

    Monday, October 28, 2013 10:17 PM
  • This OS becomes more and more a nightmare!!!!!!!!

    After installing the OS and all applications it was not possible to open "Change PC Settings". I have done a refresh on the OS as recomended, installed exactly EVERYTHING again and now the Option "Change PC Settings" is working. YEAAHHHH!!!

    But now I want to do a SYSPREP and what happens? Exactly this error Message:

    2013-11-05 14:44:06, Info SYSPRP ActionPlatform::GetValue: Getting value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep 2013-11-05 14:44:06, Warning SYSPRP ActionPlatform::GetValue: Error from RegQueryValueEx on value SysprepMode under key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep; dwRet = 0x2 2013-11-05 14:44:06, Info SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null> 2013-11-05 14:44:06, Info SYSPRP ActionPlatform::GetStringValue: Getting REG_SZ value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment 2013-11-05 14:44:06, Info SYSPRP ActionPlatform::GetValue: Getting value PROCESSOR_ARCHITECTURE under key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment 2013-11-05 14:44:06, Info SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64 2013-11-05 14:44:06, Info [0x0f0080] SYSPRP ActionPlatform::LaunchModule: Found 'Sysprep_Clean_Validate_Opk' in C:\Windows\System32\spopk.dll; executing it 2013-11-05 14:44:06, Error [0x0f0036] SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows. 2013-11-05 14:44:06, Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll; dwRet = 0x139f 2013-11-05 14:44:06, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml; dwRet = 0x139f 2013-11-05 14:44:06, Error SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x139f 2013-11-05 14:44:06, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x139f 2013-11-05 14:44:06, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep cleanup internal providers; hr = 0x8007139f 2013-11-05 14:44:14, Info [0x0f0052] SYSPRP Shutting down SysPrep log 2013-11-05 14:44:14, Info [0x0f004d] SYSPRP The time is now 2013-11-05 14:44:14

    I never have had so much trouble bevore to create an Company Image as with this f****ing OS!!!!

    So, let's start from scratch. AGAIN! :-(

    Tuesday, November 5, 2013 1:56 PM
  • I finally got the sysprep to work 

    You need to take care of the following things

    A> It doesn't work with upgraded PC

    B> For fresh installation and creating sysprep you need to activate the administrator account delete any other user account

    C> Don't update any of the metro apps. Normal windows update is fine .

    D> If you need to add any other settings please use the answer file settings.

    Tested with Windows 8.1 Enterprise 

     

    Thursday, November 7, 2013 6:56 AM
  • Might you be willing to post your unattend.xml file?

    I tried a clean install of Windows 8.1, but sysprep did not work exactly the same with my Windows 8.0 unattend.xml file and rather than start everything *completely* from scratch, I'd like to figure out why...

    Thursday, November 7, 2013 5:34 PM
  • Are you trying to install windows 8 or windows 8.1?

    If its 8.1 then u need to download and install windows ADK 8.1 and then convert the windows 8 unattend.xml to windows 8.1 

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="specialize">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <AutoLogon>
                    <Password>
                        <Value>QQBjAHQAeQAxADIAMwA0AFAAYQBzAHMAdwBvAHIAZAA=</Value>
                        <PlainText>false</PlainText>
                    </Password>
                    <Enabled>true</Enabled>
                    <LogonCount>1</LogonCount>
                    <Username>administrator</Username>
                </AutoLogon>
                <ComputerName>*</ComputerName>
                <CopyProfile>true</CopyProfile>
                <TimeZone>India Standard Time</TimeZone>
            </component>
            <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <fDenyTSConnections>false</fDenyTSConnections>
            </component>
            <component name="Networking-MPSSVC-Svc" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <FirewallGroups>
                    <FirewallGroup wcm:action="add" wcm:keyValue="Remote Desktop">
                        <Active>true</Active>
                        <Group>Remote Desktop</Group>
                    </FirewallGroup>
                </FirewallGroups>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>en-IN</InputLocale>
                <SystemLocale>en-IN</SystemLocale>
                <UILanguage>en-IN</UILanguage>
                <UILanguageFallback>en-IN</UILanguageFallback>
                <UserLocale>en-IN</UserLocale>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <FirstLogonCommands>
                    <SynchronousCommand wcm:action="add">
                        <CommandLine>powershell.exe c:\Windows\Telas\firstlogoncommands.ps1</CommandLine>
                        <Order>1</Order>
                        <RequiresUserInput>false</RequiresUserInput>
                    </SynchronousCommand>
                </FirstLogonCommands>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>3</ProtectYourPC>
                </OOBE>
                <TaskbarLinks>
                    <Link0>C:\Program Files (x86)\Mozilla Thunderbird\thunderbird.exe</Link0>
                    <Link1>C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe</Link1>
                    <Link2>C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe</Link2>
                    <Link3>C:\Program Files (x86)\Google\Chrome\Application\chrome.exe</Link3>
                    <Link4>C:\Program Files (x86)\Mozilla Firefox\firefox.exe</Link4>
                </TaskbarLinks>
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>QQBjAHQAeQAxADIAMwA0AEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>QQBjAHQAeQAxADIAMwA0AFAAYQBzAHMAdwBvAHIAZAA=</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <DisplayName>abc</DisplayName>
                            <Group>Administrators</Group>
                            <Name>acty</Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim:d:/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>


    Friday, November 8, 2013 3:33 AM
  • So, does one *have* to use "Administrator" for this?

    It seems so because if I run sysprep from whatever default localadmin account I set up when clean-installing Windows 8.1, then the start menu is missing applications after an otherwise-successful sysprep

    Tuesday, November 12, 2013 3:27 PM
  • And to clarify, the steps I take with Windows 8.0:

    Clean install with local (non-Microsoft) admin account.   Update Windows.  Run sysprep /oobe /generalize /unattend:<myfile>

    *not audit mode*   *no other software installed beyond the Windows 8.1 updates in Windows update*

    Result in having the exact same startup menu as before I ran sysprep.

    If I do the same exact steps in Windows 8.1, the start menu only shows about 1/2 of the standard Metro applications.

    Something is different in Windows 8.1 compared to Windows 8.0, but I can't figure out what...


    Tuesday, November 12, 2013 4:09 PM
  • Hello Steve,

    Can you post the unattend file?

    You should be able to use a different account than the default local Administrator account, in fact that is recommended.


    Thanks, Darrell Gorter [MSFT] This posting is provided &quot;AS IS&quot; with no warranties, and confers no rights.

    Tuesday, November 12, 2013 5:25 PM
  • Sure -- I created this with the WAIK 8.1 version, too.  Localadmin account is "bec-admin" and unattend file is on the desktop of that account (as you'll see at the end...)   I have also tried this *without* the customizations to reenable System Restore and Windows Update for Microsoft products.

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="generalize">
            <component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SkipRearm>1</SkipRearm>
            </component>
            <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <ComputerName>WIN8164-BEC</ComputerName>
                <ShowWindowsLive>false</ShowWindowsLive>
                <TimeZone>Eastern Standard Time</TimeZone>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>en-us</InputLocale>
                <SystemLocale>en-us</SystemLocale>
                <UILanguage>en-us</UILanguage>
                <UserLocale>en-us</UserLocale>
                <UILanguageFallback>en-us</UILanguageFallback>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <NetworkLocation>Work</NetworkLocation>
                    <ProtectYourPC>1</ProtectYourPC>
                </OOBE>
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>KgAqACoAMQA5ADYANQBPAFQAVAAzADIAYgBpAHQAUABhAHMAcwB3AG8AcgBkAA==</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Description>Local Administrator</Description>
                            <DisplayName>bec-admin</DisplayName>
                            <Group>Administrators</Group>
                            <Name>bec-admin</Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
                <FirstLogonCommands>
                    <SynchronousCommand wcm:action="add">
                        <Description>Enable System Restore</Description>
                        <Order>1</Order>
                        <CommandLine>C:\Windows\System32\wbem\wmic /namespace:\\root\default path SystemRestore call Enable %SystemDrive%\</CommandLine>
                    </SynchronousCommand>
                    <SynchronousCommand wcm:action="add">
                        <Description>Enable Microsoft Update</Description>
                        <Order>2</Order>
                        <CommandLine>cmd /c cscript c:\Users\bec-admin\desktop\microsoftupdate.vbs</CommandLine>
                    </SynchronousCommand>
                </FirstLogonCommands>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim://win8164-bec/users/bec-admin/desktop/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

    Tuesday, November 12, 2013 5:28 PM
  • If there's something terribly obviously wrong in that file -- let me know.
    • Edited by steve maser Tuesday, November 12, 2013 5:38 PM
    Tuesday, November 12, 2013 5:38 PM
  • Hello,

    Are you logging in as Beck-Admin and which tiles are you seeing?

    If you create another user after the unattend do you see all the tiles for that user account


    Thanks, Darrell Gorter [MSFT] This posting is provided &quot;AS IS&quot; with no warranties, and confers no rights.

    Tuesday, November 12, 2013 6:24 PM
  • So, this is what things look like prior to running sysprep from the only account on the computer (bec-admin):

    this is what they look like after I run sysprep /oobe /generalize /unattend:<myfile> from the same bec-admin account:

    Note that some apps in that list show as installing after I look at this.  Initially, there are only about 6-7 apps, but then other apps like "Reader" start installing.

    NOTE:  "PC Settings" retains that "Error" -- so I am unable to create a new user account at this point.   If I go to the classic desktop control panels to add a user, it switches to "PC Settings" which then shows the Metro interface and then immediately quits.

    Again -- same (basically) unattend.xml file on clean-install Windows 8.0 -- and the Start menu is the default when doing the exact same thing.

    I can easily reproduce this with Windows 8.1 64 Enterprise.

    Tuesday, November 12, 2013 6:56 PM
  • But I want to clarify -- even though some of the other apps start installing (like Reader or Travel) if I immediately look at this -- the second photo is where things *stop*.   No Weather, no People, no Mail, no Maps, etc...

    The larger problem really is that "PC Settings" is unusable.   I could live without the other Metro apps if it came down to it.  I can't live without the ability to create new accounts on the computer...

    Tuesday, November 12, 2013 6:58 PM
  • And, not that I expected any difference, the same thing occurs after installing today's Windows Updates...  Same set of apps after sysprep, same "error" on PC Settings, etc...
    Tuesday, November 12, 2013 9:09 PM
  • Steve

    If you sysprep with "administrator" then u can manually add the tiles to the start screen and then sysprep also u can add application tiles too, they stay even after sysprep.(Manual work duhh...)

    And since my early sysprep days from windows 7. I have been using the same old "administrator" account to sysprep haven't caused any issues till now 

    Wednesday, November 13, 2013 3:30 AM
  • So, I'm not opposed to redoing this and enabling "administrator" from the start if that's the *only* way to do this moving forward.

    However, Darrell's post above implies that I shouldn't have to use that specific account (and, as I've mentioned, I don't use that account on my Windows 8.0 64 Enterprise system.)


    • Edited by steve maser Wednesday, November 13, 2013 4:50 AM
    Wednesday, November 13, 2013 4:50 AM
  • Yes, using other user used to work in Windows 8.0 as I recall using it but strangely when i tried using it in 8.1 it was giving up fatal sysprep error
    Wednesday, November 13, 2013 5:00 AM
  • Darrell?

    Are you able to reproduce my problem?  Is it a bug?  Or is it no longer supported?

    Wednesday, November 13, 2013 7:10 PM
  • Hello Steve,

    Not seeing that exact issue.

    One thing, are you logging on with the Bec-Admin account, then running sysprep with that unattended file?

    The unattended file has the same account that you are logged on with?  So wondering if you use a different account it makes any difference/

    A second thought it timing how long between logging on and running sysprep? 


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, November 13, 2013 8:19 PM
  • Correct:   Like on my Windows 8.0 system -- I *only* have a bec-admin admin account on the system.   "Administrator" is not enabled.   I am running sysprep directly from that account.

    How long between logging on and running sysprep?   For Windows 8.0, what I have done in the past is the following:   Logged in on Patch Tuesday, installed all updates and rebooted, ran System Restore to remove any restore points, ran Disk Cleanup to erase files (the goal being to make the contents of the HD as small as possible so I can back it up), then reboot one more time, log in, and run sysprep fairly soon after I have logged back in.

    For Windows 8.1 -- I am essentially doing the same thing in the same time frame, so there usually would never be more than 5-10 minutes between when I have cleaned up the hard disk and when I have run sysprep.  

    I have my Windows 8.1 in a VM while I'm trying to debug this, so I can reboot and can let it sit after reboot for as long as you'd like -- but I don't think that matters.   I initially tried previously installing Office before sysprepping, etc and that would have sat for a while (or been used for a while) without sysprepping.

    What happens when you do my steps above with my unattend file (you could easily change the PW for the account in WAIK..)?

    Wednesday, November 13, 2013 8:34 PM
  • Darrell...

    Another user in this forum (which I started) also has the same exact problem:

    http://social.technet.microsoft.com/Forums/windows/en-US/33a69e96-2ec7-45ed-bd45-da739641f67f/sysprep-and-windows-81-missing-metro-apps-after-reboot?forum=w8itproinstall

    Thursday, November 14, 2013 3:47 PM
  • So, I also tried this:

    Made a second admin account in my restored VM called “becadmin” (no hyphen) using the same password as bec-admin

    Moved my unattend file and associated other files from the “bec-admin” account to C:\sysp — and edited my paths in my unattend file (and associated vbs script and sysprep shortcut file) so they would not be run/read from within any actual user account.

    I also removed the <ShowWindowsLive> line as I missed the prompt in the AIK that it was deprecated (I missed that previously)

    Logged into “becadmin” (note, “bec-admin” still exists).

    Ran sysprep from that account.   Restarted.  Both bec-admin and becadmin accounts are visible.

    I log into “becadmin”

    Same thing.   “becadmin” account acts like when I ran sysprep from “bec-admin” — only some of the Metro app tiles are visible after reboot and “PC Settings” has an “error” on it.

    But, “bec-admin” — is untouched.   I can run “PC Settings” from there.

    HOWEVER — if I create a new account from the bec-admin account (called becadmin2) — it looks like “becadmin” now does — with the missing Metro apps.

    This sounds like a bug.   Am I wrong?

    Thursday, November 14, 2013 4:31 PM
  • I've been asked to post here.

    I do the following.

    Install Win8.1 Pro, created local 'admin' account for administrator, joined domain, logged in as domain\administrator, installed drivers and programs. Deleted admin account, dropped off domain to workgroup, logged in to admin, deleted domain\administrator account, ran sysprep. 

    After sysprep when a new user logs on (and admin), the only icons they get on the start screen are IE, Store, File Explorer, Skydrive and Desktop. I can search for Calculator  / Camera etc and find them but some are missing such as Mail, Weather, People etc.

    I've done exactly the same in Windows 8 Pro in the past and not had this problem at all. I've even setup 2 images from scratch and had the same issue.

    Regards,

    Mark


    • Edited by Tech_Mark1 Friday, November 15, 2013 6:30 AM
    Friday, November 15, 2013 6:30 AM
  • Darrell...

    What are we missing here?   (Since it's not just me with this issue...)

    Monday, November 18, 2013 5:43 PM
  • IMPORTANT!

    SW_DVD5_SA_Win_Ent_8.1_64BIT_English_MLF_X18-96759 is the culprit. I used the following without issues:

    MICROSOFT.WINDOWS.8.1.RTM.X64.ENGLISH.DVD-WZT
    RELEASE DATE: 08/21/2013 BUILD: 6.3.9600.16384.WINBLUE_RTM.130821-1623
    FILE: Windows_8.1_EN-US_x64.ISO SIZE: 3,899,295,744 byte
    SHA-1: BC2F7FF5C91C9F0F8676E39E703085C65072139B
    MD5: F104B78019E86E74B149AE5E510F7BE9
    magnet:?xt=urn:btih:958ED16A00869C0BA4C04815AB500FFA1F2EE92E

    • Edited by cbei1261 Tuesday, November 19, 2013 6:31 PM
    Tuesday, November 19, 2013 2:13 AM
  • So, where did you get that specific .ISO file (which sounds like a pirated version?)   

    I have been using the same one you think is the culprit:

    SW_DVD5_SA_Win_Ent_8.1_64BIT_English_MLF_X18-96759

    Which looks like it installed 6.3.9600.16422.131006-1505  (or at least that's the build I'm running now after having installed the Windows Updates since installing the GM...which would seem like a later build, no?)

    Scratch that -- 16384 is what gets installed with that same DVD.   The kernel just updates to 16422 after you run Windows Update.

    Which makes me wonder if you are not supposed to run Windows Update until after you have sysprepped once?

    Can you resysprep your computer *after* running Windows Update?

    • Edited by steve maser Tuesday, November 19, 2013 8:36 PM
    Tuesday, November 19, 2013 8:16 PM
  • @ steve maser

    What I am saying that I discovered is that no matter what you do, Microsoft made/or didn't make some changes in SW_DVD5_SA_Win_Ent_8.1_64BIT_English_MLF_X18-96759 which causes it to not work using Sysprep, MDT, etc. Forget about updates, which doesn't seem to matter. I tried with and without updates and got the same result, missing apps. You need to contact Microsoft and file a support request so that they can get you an updated ISO file. I'm using the leaked ISO for now since it works and have the licenses. For someone with time, they could compare all the files and determine what has changed, but I would not recommend anyone using  SW_DVD5_SA_Win_Ent_8.1_64BIT_English_MLF_X18-96759.iso from Microsoft until they have resolved this issue.

    Wednesday, November 20, 2013 5:32 PM
  • But to clarify this -- is the version that you are able to make this work with *not* the Enterprise version?

    From what I can google around to see MICROSOFT.WINDOWS.8.1.RTM.X64.ENGLISH.DVD-WZT  is not "Enterprise" (unless I'm wrong here?)

    (Sorry for double-posting this -- I want to make sure anybody else following these threads sees the questions/answers...)

    Wednesday, November 20, 2013 5:38 PM
  • Hey Darrell?   Anything?   I've tried Windows 8.1 Pro and Windows 8.1 Pro VL (downloaded from Technet yesterday) -- and the exact same thing happens.
    Thursday, November 21, 2013 4:48 PM
  • Hello,

    There are people looking into this, the versions of isos was interesting and was something we were considering a possible reason we were not seeing it


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, November 21, 2013 5:50 PM
  • So, if you have a Win 8.1 64-bit Enterprise.iso that *does* work properly -- how do we get it?  

    The one I got from technet does not work and the one we got here at U of M -- does not work.

    Thursday, November 21, 2013 6:20 PM
  • Darrell...

    Not sure if you are reading the other thread about this, but I have tried a torrented .iso from August, the current ISO (dated 10/17) from Technet and the "trial" enterprise .iso -- all 4 Enterprise .iso installations I have tried (off-network installations) have failed -- no matter what account I run sysprep from, when I reboot, that account has lost the vast majority of Metro app icons.

    The only tentative workable solution (which isn't) is to have a dedicated account to only run sysprep from -- which will always be missing apps -- and have my unattend account create a new localadmin account that I can use to *then* provision new accounts from, etc.  -- but if I attempt to sysprep from that new localadmin account, it -- like the original account -- loses whatever Metro app icons were there as usual.  So, I'm stuck with having two visible "administrator" accounts on my system.    Which can't be the intent here.


    Thursday, November 21, 2013 10:18 PM
  • Re-posted from the other thread:

    OK, at least in my case I've worked out the problem. The short story is that the culprit is the "Pre-staged app cleanup" task sitting under "\Microsoft\Windows\AppxDeploymentClient" in Task Scheduler. This is set to run after at any logon, but only after a certain amount of idle time, so whether it actually runs prior to sysprep will vary depending on exactly what happens during the image build and may even be unpredictable on different builds using the same scripts depending on timing. In my case at least, if this task runs prior to sysprep then the resulting image is missing some of the apps. If it doesn't run then they are all there.

    Sysprep doesn't remove the last run time of this task, so you can easily take an image you have (working or not), deploy it and check the last run time of the task to see whether the task ran during image build.

    To make sure the task doesn't run, just run "Schtasks.exe /change /disable /tn "\Microsoft\Windows\AppxDeploymentClient\Pre-staged app cleanup"" as the first thing while building your image. I guess if you ever want to run sysprep then don't enable the task, but you could re-enable it after deployment if you want to. I'm not sure what the purpose of this task is, so I'm not certain if leaving it disabled is a problem.

    I previously said the behaviour had changed between certain dates. As it turns out, I was just confused - I saw the 5 apps on the Administrator's start screen while building the image and assumed it had a problem because of that, but as it turns out that must be normal. After sysprep Administrator gets all the normal icons on the start screen and I don't normally watch the image build closely, so I didn't realise what the normal behaviour was.

    The only reason why it had been working consistently for us was that on the preview version of Windows 8.1 if that task ran then sysprep wouldn't work at all - see http://technet.microsoft.com/en-us/library/dn303404.aspx and I had just left the command in there for building the RTM version. I started seeing the problem after removing that command, but thought it was something else because as mentioned I thought the normal behaviour was different.

    Saturday, November 23, 2013 2:58 AM
  • So, I tried this and was unsuccessful:

    Did another clean install in a Virtual Machine (with no networking so nothing can auto update).

    Set up windows 8.1 with a local account only (not "Administrator").   Did not even log in before saving a snapshot.

    Logged in.  Immediately ran that command above (which disabled that tasks).   I could not have ran this any faster.

    Ran sysprep.

    Same thing -- upon reboot and login, only a few Metro app icons are visible.   And maybe 5 minutes after log in, *some* of the stock Metro apps are reinstalled automatically (maybe 1/3 of them?) but with no icons.

    So, if your method works via "Administrator", it's not making a difference with how I had used sysprep under Windows 8.0

    Monday, November 25, 2013 4:12 PM
  • I also tried the same above and received the same result.

    • Fresh install from SW_DVD5_Win_Pro_8.1_32BIT_English_MLF_X18-96671.ISO to Acer Iconia W510
    • Created account 'admin'
    • Turned bitlocker on then off
    • Ran task above
    • Sysprep
    • Rebooted
    • Log in to 'admin' and only 5 icons are showing
    Tuesday, November 26, 2013 2:08 AM
  • Alright just did another test.

    • Fresh install from SW_DVD5_Win_Pro_8.1_32BIT_English_MLF_X18-96671.ISO to Acer Iconia W510
    • Created account 'admin'
    • Joined domain
    • Installed Windows Updates
    • Installed Office 2013 and Adobe MC CS6 + Updates
    • Turned bitlocker on then off
    • Deleted 'admin' account.
    • Dropped off domain
    • Removed network cable
    • Ran ospprearm
    • Made a change in regedit to skiprearm and persistalldeviceinstall set to 1
    • Ran Sysprep
    • Rebooted
    • Log in to 'admin' / join domain / log into domain\administrator and now everything is showing up properly.

    Perhaps a Windows Update has resolved this issue. Steve can you try again with all Windows Updates from 'Check online' and see if it's working for you now too?

    Monday, December 2, 2013 1:00 AM
  • So, this is what I did (again) this morning.   Note, it differs in many instances that what you did, but these were my exact steps:

    1)  Fresh Install from “en_windows_8_1_enterprise_x64_dvd_2971902.iso” (current on TechNet as of last week) into a Virtual box *offline*.   NOTE:  This is Enterprise where you used “Pro”

    2)  Used “express settings” to set up non-Microsoft/Local account:  bec-admin

    3)  Did *not* join domain.

    4)  Installed Virtual Box 4.3.4 tools (so I could get shared folders/internet to fully work.)  Rebooted (as is required by the tools installer).  NOTE:  this is the only 3rd party software installed.

    5)  Changed the clock (as the default/express install puts me in the Pacific Time Zone (changed this to EST).   Connected laptop to Internet.

    6)  Ran Windows Update -- 12 updates listed.  Installed and rebooted.

    7)  I deleted all restore points and ran “Disk Cleanup” to delete anything listed (including system files) and rebooted and left windows running

    8)  For something different this time, I left the VM up and running for about an hour in case something magically has to run in the background after login to clean up stuff.   

    I do not need to run “osspprearm” because Windows is automatically activated on our network by this time.

    An hour later….

    9)  I run sysprep /oobe /generlize /unnattend:<my unnattend.xml> file — from the bec-admin account (contents of unattend.xml file are listed above...)


    10)  Rebooted.  Logged back in to “bec-admin”.  

    And — as usual with my experiences in this thread — only about 6 Metro app icons are on the start screen and other apps are missing from the list of all apps, but some start to install if I watch, and some “error” — in this attempt “Store” says “error” on it -- as they install

    And any newly created accounts (at this point) only have the 5 Metro app icons in them.

    The only way I’ve been able to make this work -- and by "work" I mean have the ability to create new accounts which contain *all* Metro applications — which is not optimal — is to have an additional local account that I *only* run sysprep from (call it “configure” for example)— and leave the “bec-admin” account manually created (either by sysprep or manually *prior* to sysprep as a second administrator-level account.)   I then would need to log into “bec-admin” to install software (or provision new accounts, etc) and then log back into “configure” to resysprep the system.

    Note — I did try setting skiprearm and persistalldeviceinstall to 1 prior to running sysprep above (after restoring from a snapshot) — but that didn’t matter, either -- the only difference was that "Camera" came up with an "error" this time.

    I fully believe there's a difference between "Pro" and "Enterprise" -- or 64-bit vs. 32-bit -- here.

    Monday, December 2, 2013 6:24 PM
  • Alright just did another test.

    • Fresh install from SW_DVD5_Win_Pro_8.1_32BIT_English_MLF_X18-96671.ISO to Acer Iconia W510
    • Created account 'admin'
    • Joined domain
    • Installed Windows Updates
    • Installed Office 2013 and Adobe MC CS6 + Updates
    • Turned bitlocker on then off
    • Deleted 'admin' account.
    • Dropped off domain
    • Removed network cable
    • Ran ospprearm
    • Made a change in regedit to skiprearm and persistalldeviceinstall set to 1
    • Ran Sysprep
    • Rebooted
    • Log in to 'admin' / join domain / log into domain\administrator and now everything is showing up properly.

    Perhaps a Windows Update has resolved this issue. Steve can you try again with all Windows Updates from 'Check online' and see if it's working for you now too?

    I wanted to come back to this:  if you created a local account "admin" -- logged into that and did your updating, how did you *delete* the account and then run sysprep?   Were you running sysprep from "administrator" at that point?  Or some other account?

    Wednesday, December 4, 2013 2:47 PM
  • I logged in to domain\administrator, deleted account through Advanced system settings > User Profiles > settings > profiles stored on this computer. 

    In control panel > users, the 'admin' account is still there and set to administrator.

    So when dropping off of domain, I can log in to 'admin' and it creates a new account for the local administrator.

    I did notice I missed listing a step above, after ran ospprearm, I did delete the domain\administrator account using the step on the first line.

    Monday, December 9, 2013 7:12 AM
  • My difficulty in trying to reproduce this is that I'm intentionally *not* logging into the domain here -- so I don't know if your workaround would be functional for me or not.

    (I think this still seems to be coming back to the need (requirement) to run sysprep from a "throwaway" account now -- and I don't know why that seems to be the case...)

    Monday, December 9, 2013 1:04 PM
  • Thank you Jonathan D. This worked for my Windows 2012 R2 upgrade.
    Wednesday, January 8, 2014 6:15 PM
  • Thank you Jonathan D!

    Deleting the "upgrade" VALUE worked for me too

    But don't be confuse with the "upgrade" KEY (also under the setup KEY).

    Credit to http://www.youtube.com/watch?v=RQ-hRyacbp0

    Friday, January 10, 2014 4:45 PM
  • Out of curiosity for those where that worked -- is that with *Enterprise* Win 8.0 upgraded to Win 8.1?   Or Consumer?
    Friday, January 10, 2014 4:49 PM
  • For those still following this thread:  we opened a case with Microsoft and the technician I'm working with was able to reproduce the problem of running sysprep from any local admin account and having many Metro applications be missing after restart.

    I'll keep this thread updated if this turns out to not be a bug for some reason.

    Friday, January 17, 2014 5:18 PM
  • Thanks, Steve. I'm continuing to follow this with great interest as well as the related thread http://social.technet.microsoft.com/Forums/windows/en-US/33a69e96-2ec7-45ed-bd45-da739641f67f/sysprep-and-windows-81-missing-metro-apps-after-reboot?forum=w8itproinstall. Would you please clarify the scope of your case with Microsoft. Is it 1) the missing modern apps after completing sysprep generalize->oobe->specialize, or 2) the sysprep generalize error "Sysprep will not run on an upgraded OS” (the original question posed in this thread), or 3) the sysprep generalize fatal error “Package <modern app> was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.”? Issue #3 is where the wheels fall off for us with Windows 8.1 deployment, and I’m prepared to open another tech support case with Microsoft unless you expect this to be addressed in yours. Thanks. Jeff.


    Jeffry A. Spain Network Administrator Cincinnati Country Day School

    Thursday, January 23, 2014 1:05 AM
  • My case is specifically about #1 -- missing modern apps after sysprep /oobe /generalize /unattend

    #2 (upgraded OS) has never worked (IIRC), so I never expected that to be addressed.

    As I've never gotten #1 to work, I've never seen #3

    Thursday, January 23, 2014 1:51 AM
  • Just made an accidental discovery which may or may not be related.

    When using SCCM (new to us) we no longer had this problem (which we expected). However playing around with using SCCM via USB and no network cable connected, the missing app and icon problem reoccured because the computer was not able to join the domain automatically. When a different computer was connected and able to join domain automatically, the problem did NOT occur.

    Tuesday, January 28, 2014 7:27 AM
  • We have the exact same issue with SCCM 2012 R2 using the iso SW_DVD5_SA_Win_Ent_8.1_64BIT_English_MLF_X18-96759.ISO. The machine is a Surface Pro tablet, I log in as as standard user are a succesful USB deployment (as the network dongle is stupidly 10/100) and I have no tiles on the desktop.

    Has anyone at Microsoft found a work around to this?

    Thursday, March 27, 2014 3:02 AM
  • This is because metro apps being tied into the local admin account that you define for the first time when you install Windows. Just use a fresh local admin account or domain admin account if in a domain to sysprep.

    You can also remove the metro packages by using below method.

    http://regularitguy.com/2013/08/05/how-to-fix-sysprep-3-14-error-for-windows-8-1-enterprise/


    Janaka Rangama MCT MIEEE MBCS (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable.)

    Tuesday, September 16, 2014 2:30 PM
  • Excuse me Jonathan, you said " Set HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus to7" but, my question is, What is exactly the key that must be changed on 7 valueI have the keys "(Default)", "CleanupState" and "GeneralizationState" on "SysprepStatus" menu.

    Anyway, I try changing every key on 7 but I doesn't work for me.

    Any suggestion?

    Thanx

    Fernando

    Wednesday, February 18, 2015 5:24 PM
  • Hello, here is my scenario

    I was upgrade a Windows Server 2003 to 2008 and then to 2012 R2 and I get the same issue

    I try all suggestions mentioned in this post, but it doen's work for me.

    So It's confirmed that Sysprep doesn't work on an upgraded OS? There is no way?

    Wednesday, February 18, 2015 6:18 PM
  • Sysprep is never supposed to work on an "upgraded" system -- so you shouldn't even try hacking around with this (honestly -- you can mess up your system otherwise...)

    (I'm assuming this is what you are asking about all these months later?)

    Wednesday, February 18, 2015 6:25 PM
  • hi hi hi...

    uninstall all the apps

    fix that

    amd64_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.17729_none_a9f7ab8f6e48b57e\win32k.ptxml
    amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\telemetry.ASM-WindowsDefault.json
    \amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\utc.app.json

    shit caused by some KB ... do not remember which... using SFCFix.exe

    reset windows update completely,

    HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus to 7

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-21-blblabla-1001]
    "State"=dword:00000000

    disable admin acount net user blabal

    run sysprep works on updated system to the day, software installed (even adobe software keeps its licences), if done correctly default user can keep all the settings even in classic shell... :).

    just be careful with permissions in default user... or the user will fail to logon.

    by!


    • Edited by ibach Tuesday, May 12, 2015 5:08 PM
    Tuesday, May 12, 2015 5:01 PM
  • sysprep is not supposed to work on an upgraded system...

    My as*!, Why sysprep than at all?! Typically Microsoft answer...

    -1 for such answer microsoft...

    And, yes. That's correct answer too, avoidable, but do not expect to be able to do refresh windows from such "abomination" of install.wim, but it is a nice thing to install the machine and all the software in about 30 min. and with all the updates. I just love wiping C drive clean and have it all set in lass than 1 hour with minimal interaction (none at all if possible, and it is). If the user files are all on another disk, it is fastest way of servicing faulty machine completely, and where I work all is set in such a way that when something is really wrong with windows we just wipe c: and up and running again in no time.

    So tell me, why does microsoft have such a stupid policy? Security?! Forget it! It's stupid.

    Tuesday, May 12, 2015 5:36 PM
  • I worked for me.  My Windows 10 Pro was not an upgrade.  The value of Upgrade was 0 but sysprep would not run until I deleted the upgrade key.  I did not change Sysprep status though and it still worked.  NICE FIND!!!
    Wednesday, December 2, 2015 8:44 PM
  • QUESTION on the "sysprep is not supposed to work on an upgraded system" with WIN10 Updates they system really isn't updated, it is patched. But the regentry UPGRADED is just a tag. Please correct me if I am wrong so I can better understand. If I am not, then what is the SUPPORTED fix?

    Thanks!

    Wednesday, March 29, 2017 9:01 PM
  • Hello ,

    Not sure I understand the question.

    Feature Updates are still full upgrades, they are not patches.

    However Windows 10 upgrade to Windows 10 will now be supported for running Sysprep.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, March 30, 2017 11:42 PM