New
#1
Sysprep error - active scenario
The PC came with Win7Pro OEM from the factory. I performed a clean install of Win10Pro 1903 and it activated itself. I let Windows update itself and I installed a couple of freeware applications. I did not install/uninstall any apps.
I'm trying to sysprep the PC so that I can transfer ownership. I just want to remove the current account and files associated with it and have the new owner be presented with OOBE when they boot the PC. I want to keep the applications I installed so I do not want sysprep to totally wipe the HDD.
I ran the following command but sysprep failed:
Code:sysprep.exe /audit /reboot
Error log:
Code:2019-10-03 22:54:10, Info SYSPRP ======================================================== 2019-10-03 22:54:10, Info SYSPRP === Beginning of a new sysprep run === 2019-10-03 22:54:10, Info SYSPRP ======================================================== 2019-10-03 22:54:10, Info [0x0f004d] SYSPRP The time is now 2019-10-03 22:54:10 2019-10-03 22:54:10, Info [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\system32\sysprep\Panther 2019-10-03 22:54:10, Info [0x0f0054] SYSPRP ValidatePrivileges:User has required privileges to sysprep machine 2019-10-03 22:54:10, Info [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything 2019-10-03 22:54:10, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'AUDIT' 2019-10-03 22:54:10, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'REBOOT' 2019-10-03 22:54:10, Info [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers. 2019-10-03 22:54:10, Info SYSPRP RunDlls:Running platform actions specified in action file for phase 3 2019-10-03 22:54:10, Info SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null> 2019-10-03 22:54:10, Info SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml 2019-10-03 22:54:10, Info SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null> 2019-10-03 22:54:10, Info SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64 2019-10-03 22:54:10, Info SYSPRP ActionPlatform::LaunchModule: Executing method 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll 2019-10-03 22:54:10, Info CSI 00000001 Shim considered [l:125]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.387_none_5f0e233a5902e7db\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 2019-10-03 22:54:10, Info CSI 00000002 Shim considered [l:122]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.387_none_5f0e233a5902e7db\wcp.dll' : got STATUS_SUCCESS 2019-10-03 22:54:10, Error SYSPRP Sysprep_Clean_Validate_Opk: Audit mode can't be turned on if there is an active scenario.; hr = 0x800F0975 2019-10-03 22:54:10, Error SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll; dwRet = 0x975 2019-10-03 22:54:10, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml; dwRet = 0x975 2019-10-03 22:54:10, Error SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x975 2019-10-03 22:54:10, Error [0x0f0070] SYSPRP RunDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x975 2019-10-03 22:54:10, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep cleanup internal providers; hr = 0x80070975 2019-10-03 22:54:12, Info [0x0f0052] SYSPRP Shutting down SysPrep log 2019-10-03 22:54:12, Info [0x0f004d] SYSPRP The time is now 2019-10-03 22:54:12
Some have recommended deleting the "HKEY_LOCAL_MACHINE\SYSTEM\Setup\Update" key but it does not exist on this PC. Others have suggested using Powershell to remove/re-install default apps but that did not help either.
I did manage to make it work by taking ownership of C:\Windows\System32\spopk.dll and replacing it with one from Win10 1809 but this seems so "hackish".
Is there another/proper way to remedy this situation?
Last edited by jeffshead; 04 Oct 2019 at 08:11.