![]() The Event Viewer with a filter on ID 478 showing installations of modern apps. You go to Microsoft / Windows / AppXDeployment-Server / Microsoft-Windows-AppXDeploymentServer / Operational and filter on Event ID 478 to see successful updates. Whereas as system which had been allowed to update them had 58 apps.Ī Windows 10 v1607 CB machine with no updates allowed, showing 54 apps.Ī Windows 10 v1607 CB machine with updates allowed, showing 58 apps.īut what about apps being actually updated? Well, you can get additional info via the Event Viewer. For a Windows 10 v1607 CB machine, that did not update any built-in updates, I had 54 apps installed. You can just run Get-AppxPackage in a PowerShell prompt, or (Get-AppxPackage).count to see the number of apps. To see which modern applications that you have in your system, for the Administrator user account in this case. Now, the above log is quite obvious, an app named Microsoft.DesktopAppInstaller_.0 was being installed or updated, and Sysprep could not remove it. This is what it looks like during the MDT build and capture process. dwRet = 0x3cf2Įrror SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers hr = 0x80073cf2 This package will not function properly in the sysprep image.Įrror SYSPRP Failed to remove apps for the current user: 0x80073cf2.Įrror SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.Įrror SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:WindowsSystem32AppxSysprep.dll dwRet = 0x3cf2Įrror SYSPRP SysprepSession::Validate: Error in validating actions from C:WindowsSystem32SysprepActionFilesGeneralize.xml dwRet = 0x3cf2Įrror SYSPRP RunPlatformActions:Failed while validating SysprepSession actions dwRet = 0x3cf2Įrror SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. Then, in the C:WindowsSystem32SysprepPanthersetuperr.log you see the following (or similar):Įrror SYSPRP Package Microsoft.DesktopAppInstaller_.0_圆4_8wekyb3d8bbwe was installed for a user, but not provisioned for all users. ![]() ![]() If that happens you will get the following error in the BDD.LOG and LTISysprep.log log files:Įxpected image state is IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE, actual image state is IMAGE_STATE_COMPLETE, sysprep did not succeed.įAILURE ( 6192 ): ERROR – Sysprep did not complete successfully, check C:windowssystem32syspreppanthersetupact.log for details Note that this doesn't happen all the time, it's a timing issue, but it sure happen often enough to be an issue. If modern apps in Windows 10 are being updated during the build and capture of a reference image, Sysprep may fail because it cannot remove the update. ![]() Note #2: Lately I have started to simply limit Internet access to the virtual machines I'm using for reference images, especially for Windows 11 that is quite aggressive in updating for example the OneDrive application. But if you want to pick some background info, and possibly learn something new in the process, continue as you were □ Note #1: This is a quite long post, and if you just want the fix, scroll to the end, to the Fixing the problem section. Sysprep fails after you remove or update Windows Store apps that include built-in Windows images The issue is explained in a KB from Microsoft, but it's workaround are not very good for automation purposes. This post is about preventing that from happening, and is a companion to my guides on building Windows 10 and Windows 11 reference images. When creating reference images for Windows 10 or Windows 11, Sysprep is very likely to fail if the machine has Internet access, and have enough time to start updating it's built-in applications, or install new ones as part of the consumer experience feature.
0 Comments
Leave a Reply. |