Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, November 22, 2017 9:16 AM
Hi all,
I am unable to do sysprep after windows 10 upgraded to latest version (1709)
In the error log file, i found the message below.
2017-11-22 17:02:08, Info SYSPRP ========================================================
2017-11-22 17:02:08, Info SYSPRP === Beginning of a new sysprep run ===
2017-11-22 17:02:08, Info SYSPRP ========================================================
2017-11-22 17:02:08, Info [0x0f004d] SYSPRP The time is now 2017-11-22 17:02:08
2017-11-22 17:02:08, Info [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\System32\Sysprep\Panther
2017-11-22 17:02:08, Info [0x0f0054] SYSPRP ValidatePrivileges:User has required privileges to sysprep machine
2017-11-22 17:02:08, Info [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\System32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
2017-11-22 17:02:08, Warning SYSPRP WinMain: File operations pending
2017-11-22 17:02:08, Info [0x0f003d] SYSPRP WinMain:Displaying dialog box for user to choose sysprep mode...
2017-11-22 17:04:08, Info [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.
2017-11-22 17:04:08, Info SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3
2017-11-22 17:04:08, Info SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null>
2017-11-22 17:04:08, Info SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml
2017-11-22 17:04:08, Info SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
2017-11-22 17:04:08, Info SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
2017-11-22 17:04:08, Info SYSPRP spopk.dll:: Sysprep will run on an upgraded OS.
2017-11-22 17:04:08, Info SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll without error
2017-11-22 17:04:08, Info [0x0f00d7] SYSPRP WinMain:Pre-validing 'generalize' internal providers.
2017-11-22 17:04:08, Info SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 1
2017-11-22 17:04:08, Info SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml, and mode <null>
2017-11-22 17:04:08, Info SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml
2017-11-22 17:04:08, Info SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
2017-11-22 17:04:08, Info SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
2017-11-22 17:04:08, Info SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.
2017-11-22 17:04:08, Error SYSPRP Package CortanaListenUIApp_10.0.15063.0_neutral__cw5n1h4txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2017-11-22 17:04:08, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.
2017-11-22 17:04:08, Error SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
2017-11-22 17:04:08, Error SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2017-11-22 17:04:08, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2017-11-22 17:04:08, Error SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
2017-11-22 17:04:08, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2017-11-22 17:04:08, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2
2017-11-22 17:05:04, Info [0x0f0052] SYSPRP Shutting down SysPrep log
2017-11-22 17:05:04, Info [0x0f004d] SYSPRP The time is now 2017-11-22 17:05:04
I ran the commands below and restart but doesn't work.
Get-AppxPackage -AllUsers | ? {$_.PackageFullName -eq 'CortanaListenUIApp_10.0.15063.0_neutral__cw5n1h4txyewy'}
Remove-AppxPackage -Package 'CortanaListenUIApp_10.0.15063.0_neutral__cw5n1h4txyewy' -AllUsers
Remove-AppxProvisionedPackage -Online -PackageName 'CortanaListenUIApp_10.0.15063.0_neutral__cw5n1h4txyewy'
Get-AppxPackage CortanaListenUIApp_10.0.15063.0_neutral__cw5n1h4txyewy | Remove-AppxPackage
Any ideas? My aim is just to do a sysprep and apply on other machine with most updated OS and software.
Thanks!
Oscar
All replies (12)
Wednesday, November 22, 2017 11:01 AM ✅Answered
If you take a look at this article:
Regards
Maurice Daly
Microsoft MVP | Enterprise Mobility
SCConfigmgr.com
Wednesday, November 22, 2017 9:53 AM
You should have a look at this article ;-)
Sysprep fails after you remove or update Microsoft Store apps that include built-in Windows images
Gérald
Thursday, November 23, 2017 2:37 AM
Hi Oscar,
Let’s note these sentences:
>>2017-11-22 17:04:08, Error SYSPRP Package CortanaListenUIApp_10.0.15063.0_neutral__cw5n1h4txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2017-11-22 17:04:08, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.
CortanaListenUIApp_10.0.15063.0_neutral__cw5n1h4txyewy should be the reason for Sysprep failure. You need to delete it on that specific account and test again.
As the KB Article 2769827
Open the PowerShell Command with Admin Rights. Execute the follow command:
Get-AppxPackage|Remove-AppxPackage
At this point the system remove the Apps that cause the Problem. You receive also many Issuereports, but this isn't a problem. After that you can capture without problem your Image.
You need to run the command by logging into each user that you had set up prior to image capture. After running the command you should able to sysprep and capture.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Monday, January 15, 2018 7:51 PM
The problem you are seeing is this. All of the answers in this thread so far do not address the issue you are seeing. Sysprep'ing an upgraded to 1709 image does not work, full stop. You've done nothing wrong - it is an issue on Microsoft's end.
There are other scenarios that give error messages similar to what you are seeing, and those can be caused by what the previous answers are trying to address. But this is a completely different issue.
Tuesday, January 16, 2018 9:45 AM
I am unable to do sysprep after windows 10 upgraded to latest version (1709)
I missed the Upgrade part in the OP message.
Using Sysprep on an upgraded OS was never supported and could lead to issues like the one you're seeing :-)
https://support.microsoft.com/en-us/help/828287/unsupported-sysprep-scenarios
Gérald
Tuesday, January 16, 2018 12:44 PM
I am unable to do sysprep after windows 10 upgraded to latest version (1709)
I missed the Upgrade part in the OP message.
Using Sysprep on an upgraded OS was never supported and could lead to issues like the one you're seeing :-)https://support.microsoft.com/en-us/help/828287/unsupported-sysprep-scenarios
Microsoft do not have a consistent position on this, and at various times have said "no, that'll never work" and "fully supported, works fine". This is an example of the latter:
/en-gb/windows-hardware/manufacture/desktop/sysprep--system-preparation--overview
Which states:
"Beginning with Windows 10, version 1607, Sysprep can be used to prepare an image that has been upgraded. For example:
-
- You can start with a computer that runs Windows 10, version 1511 or Windows 10, version 1507.
- Upgrade the computer to run Windows 10, version 1607.
Run Sysprep generalize on the upgraded image, re-capture the updated image, and deploy the image to new devices."
This may have stopped working again with later builds, but it's certainly been something that's supposed to work for some builds at least.
Of course, the fact that you can find official MS docs that say contradictory things about this is a problem in itself.
Tuesday, January 16, 2018 6:45 PM
The docs are not inconsistent or contradictory. The link Gérald provided that says sysprep is unsupported after an upgrade does not apply to Windows 10 (click on the "applies to multiple products" to see which products it applies to).
Having sysprep work on an upgraded Windows 10 system is a big deal because Windows 10 now has an upgrade every 6 months, versus the every 2-5 years for previous OS versions.
Wednesday, January 17, 2018 12:35 PM
Yes, the link is not mentioning Windows 10 and indeed, Mike is right, this is supported since 1607.
Since 1607, you can see this in the log:
SYSPRP spopk.dll:: Sysprep will run on an upgraded OS.
Previously, this was:
SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.
I was not aware of this change because I'm following clients that always recreate their corporate image from the latest DVD instead of upgrading :-)
I'll test that on my lab to see if I can reproduce the problem because there's not a lot of info from the OP.
Gérald
Wednesday, January 17, 2018 7:39 PM
Thanks for taking a look Gérald. It should be straightforward to reproduce. I think all you need to do is create a VM with no network access, install 1703, and then upgrade to 1709 by using the 1709 ISO and running its setup.exe (choose to not get updates, as you are not online, when prompted). When the upgrade is done, run
c:\windows\system32\sysprep.exe /generalize /oobe
from an elevated command prompt.
It will quickly error out and tell you it couldn't validate your windows installation. The log will list an error related to one of the packages that is not fully removed.
Wednesday, January 17, 2018 9:27 PM
A curious difference I just noticed in testing.
When working with my MDT images, there are 11 apps left with blank install locations after running the 1709 upgrade. This includes CortanaListenUIApp
When I manually install 1703 and then manually upgrade to 1709, there is only 1 system app left with blank install location, MiracastView.
I'm not sure what the difference is between my automated imaging/upgrading and doing it manually, but it is there. I do use customized ISOs for my MDT images that have all of the provisioned apps removed to avoid other issues. MiracastView is different than all of the other system apps that are removed in that it resides in C:\windows instead of c:\windows\systemapps .
The fact that in certain scenarios CortanaListenUIApp is getting removed successfully by the upgrade is noteworthy.
Wednesday, January 17, 2018 10:29 PM
Just verified that using my slimmed-down no provisioned app ISOs to manually install 1703 and then upgrade to 1709 is what results in having 11 system apps in this bad state, instead of 1. Doing this slimming is what is recommended by one of Microsoft's deployment experts to avoid some of the removing provisioned apps mess.
Wednesday, March 28, 2018 10:17 PM
I just successfully completed an installation of Windows 10 1709 on a Dell Optiplex 3020. I installed all the programs and applications I needed (Office 2016 from office.com, Fox-It pdf reader and several others), ran all available updates.
I thought I'd try to clone the drive to use it for deployment, so I cloned it with Norton Ghost 2003 (yes it's 15 years old, but it still works for me).
I put the cloned drive back in the original PC but it failed to boot, so I booted from an original Windows 10 DVD, accessed the command prompt and ran "bootrec /rebuildBCD" - rebooted and the drive was recognized and ran fine.
Next thought was to sysprep this puppy, so I had an old CopyProfile.xml for windows 10 on a flash drive, I plugged it in and ran "C:\Windows\system32\sysprep\sysprep.exe /generalize /oobe /shutdown /unattend:F:\CopyProfile.xml" - FAILURE!! It directed me to the setupact.log file buried in the panther folder under sysprep.
The first line of errors said that a specific app was not provisioned for all users, so I found that app on the start page, right clicked on the icon and uninstalled the app.
This little ditty went on for about 6 or 7 apps on the start page and finally after one app uninstall, sysprep ran and shut down the PC as directed.
I then cloned my sysprepped drive again with my 15 year old Ghost, put the Ghost clone in the PC, booted it up and after one forced reboot (always happens) OOBE ran and it looks like I have a fresh Image of Windows 10 1709 (OS Build 16299.309) ready to deploy as needed.
The last image I created I used the method of setting Windows 10 so it thought it was on a metered connection and it did no updates, but just uninstalling the apps instead of preventing them from updating was much easier.
Hope someone else can use this to do their deployment.
Jim Smith
Lubbock Christian University