Sysprp Failed To Remove Apps For The Current User 0x80073cf2 !new! 〈DELUXE ★〉

Remove-AppxProvisionedPackage -Online -PackageName <FullPackageName> If removal fails, force removal from the image (offline servicing recommended for production):

Document ID: WIN-SYSPREP-009 Severity: High (Image preparation blocker) Applies to: Windows 10/11 (1809 and later), Windows Server 2019/2022 1. Executive Summary The error sysprep failed to remove apps for the current user 0x80073cf2 occurs during the generalization phase of Windows System Preparation (Sysprep). This prevents successful image capture for deployment. The error indicates a critical failure where Sysprep cannot remove provisioned modern (UWP/Store) applications for the built-in administrator or current user context. This paper outlines the root cause, diagnostic steps, and three validated remediation methods. 2. Error Description & Context When executing sysprep /generalize /oobe /shutdown , the process validates that all provisioned apps can be removed for the current user. Error 0x80073cf2 translates to: ERROR_APPPACKAGE_INTERACTION_NOT_ALLOWED – The interaction with the app package is not allowed because it is blocked by policy or system constraints. Full typical error log excerpt (from %WINDIR%\System32\Sysprep\Panther\setuperr.log ): sysprp failed to remove apps for the current user 0x80073cf2

2025-03-15 10:23:45, Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure while executing 'SysprepGeneralizeValidateUsers' from 'C:\Windows\System32\spopk.dll'; dwRet = 0x80073cf2 2025-03-15 10:23:45, Error [0x0f0070] SYSPRP sysprep.dll: Sysprep failed while validating Windows Store app package interactions. Error: 0x80073cf2 Sysprep fails because one or more provisioned apps (user-installable but pre-staged for all new users) are in a state that violates Sysprep’s requirement for a clean, unpersonalized default user profile. The error indicates a critical failure where Sysprep

Primary causes:

dism /online /remove-provisionedappxpackage /packagename:<PackageName> If above fails, execute a complete app package reset: If above fails