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
Thursday, July 19, 2018 4:47 PM | 2 votes
Hey Folks, I am have an absolutely infuriating issue here. I am currently attempting to deploy a Windows 10 v1803 image that was built straight from an 1803 Pro ISO from the Microsoft website. Before sysprepping and deploying our image, I took a snapshot in VMware - this is all fine and good, and it keeps my images from running out of Sysprep validations (as technically as long as we roll back to the last snapshot after deploying an image, we keep our "remaining sysprep" counter untouched indefinitely).
After I deployed the image from Sysprep, we realized that we had left a local account on the VM, which means every time our imaging server deploys the image to a computer in our org, 2 local accounts are present - the built-in Administrator account (we want this active and present) and a second account called "tech admin" that we had put in during the setup process of Windows 10 initially when installing the VM.
So, I re-wound back to the previous point before sysprep and removed the tech admin account and got everything ready for sysprep, took a snapshot again and went to sysprep and when I went to execute sysprep, I was notified that "Sysprep was not able to validate your Windows Installation. Review the log file at [DIRECTORY OF PANTHER] for details. After resolving the issue, use Sysprep to validate your installation again."
According to the log files, Sysprep failed to validate because of a windows app store issue that may have been caused due to removing the other account, which is a serious pain. Our last image was based on Windows 10 v1509 Fall creators edition, and we updated it all the way up to v1803 but ran into this same issue at the time - however the image had numerous issues and was also updated and maintained since mid-way through the lifecycle of Windows 7, so we were fine with re-building the image from the ground up.
Does anybody know how to get past this sysprep issue? I am completely dumbfounded and have tried many times in the past with our previous image to get past this error and had no luck at all, so I am turning to the Windows TechNet forums as my last hope. This problem is infuriating and I refuse to re-install and re-build our Windows 10 custom deployment image all over again because of a stubborn windows app tangling with Sysprep. This never caused issues in previous builds of Windows 10, and I really feel that Microsoft needs to fix this.
Thanks guys - excerpt from the sysprep log file below:
2018-07-19 13:18:20, Error SYSPRP Package 89006A2E.AutodeskSketchBook_1.8.1.0_x64__tf1gferkr813w was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2018-07-19 13:18:20, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.
2018-07-19 13:18:20, Error SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
2018-07-19 13:18:20, Error SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2018-07-19 13:18:20, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2018-07-19 13:18:20, Error SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
2018-07-19 13:18:20, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2018-07-19 13:18:20, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2
All replies (12)
Thursday, July 19, 2018 4:53 PM | 1 vote
check if the appx package is still linked to the removed account; if it is remove the package from the dead account.
then re-sysprep.
Thursday, July 19, 2018 6:54 PM | 1 vote
Is it possible to remove a package from an account if the account no longer exists? It is deleted, not disabled.
Thursday, July 19, 2018 7:03 PM | 1 vote
Read my post I created yesterday.
I'm gonna take a wild guess that you have generalize checked off.
Friday, July 20, 2018 8:19 AM | 1 vote
Hi,
The most common one is that sysprep was executed on an upgraded Windows installation.
You could remove the app to check.
Sysprep fails after you remove or update Microsoft Store apps that include built-in Windows images
Regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Friday, July 20, 2018 12:50 PM | 1 vote
"The most common one is that sysprep was executed on an upgraded Windows installation."
Just to note that I did mention in my question that this was a fresh 1803 image directly from ISO.
Friday, July 20, 2018 12:54 PM | 1 vote
Sysprep was and is always launched here with the following keys - "sysprep.exe /generalize /shutdown /oobe".
Friday, July 20, 2018 1:00 PM
Try running this command in command prompt as admin: sfc-scannow.
This will check and try to fix Windows Integrity issues. This did help me resolve a similar issue to this once before, but this can be hit or miss. But its worth trying.
Monday, July 23, 2018 1:26 PM
/generalize is causing your issue. It will succeed without that flag.
My post I'm looking for the reason why.
Wednesday, August 22, 2018 5:42 PM | 1 vote
Follow Steps 4 and 5 from here
Then Sysprep Generalize should succeed.
For devices running Windows 10, use the Remove-AppxProvisionedPackage cmdlet in Windows PowerShell to uninstall the following applications:
Microsoft.windowscommunicationsapps_8wekyb3d8bbwe
Microsoft.BingWeather_8wekyb3d8bbwe
Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
Microsoft.Getstarted_8wekyb3d8bbwe
Microsoft.Windows.Photos_8wekyb3d8bbwe
Microsoft.WindowsCamera_8wekyb3d8bbwe
Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe
Microsoft.WindowsStore_8wekyb3d8bbwe
Microsoft.XboxApp_8wekyb3d8bbwe
Microsoft.XboxIdentityProvider_8wekyb3d8bbwe
Microsoft.ZuneMusic_8wekyb3d8bbwe
Note
Uninstalling these apps will decrease sign-in time. If your deployment needs any of these apps, you can leave them installed.
At a command prompt, type the following command and press ENTER.
sysprep /oobe /reboot /generalize /unattend:unattend.xml
Tuesday, February 26, 2019 1:48 PM | 1 vote
Hi there, i know this topic is too old but i just had this issue while imaging a laptop with the captured image and i found out that the image which we were trying to capture was encrypted by bitlocker and also the user account being used to sysprep was a local account part of administrators. I decrypted the drive and sysprepped using local administrator account and it worked like a charm!!!!
Thanks,
Ali
Sunday, April 14, 2019 1:48 PM
Yeah I had the same thing :( For me it was a language Package.
Sysprep Was Unable to Validate
Pete
Regards Pete Long http://www.petenetlive.com
Thursday, January 23, 2020 1:02 PM
check if the appx package is still linked to the removed account; if it is remove the package from the dead account.
then re-sysprep.
How to remove/de-link a package from deleted user account ? and how to provision a package or all installed/preinstalled packages for all users ?
I am stuck in sysprep errors (Package 22094SynapticsIncorporate.AudioControls_1.3.89.0_x64__qt57b6kdvhcfw was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image)
Please share.
With Kind Regards
Muhammad Irfan