Get-AppxPackage -AllUsers | Where-Object $_.PackageUserInformation.InstallState -eq "Staged" | Remove-AppxPackage -AllUsers Use code with caution. Step 4: Modify Registry Sysprep Status Keys
To prevent subsequent app updates from blocking the process, run a sweeping script to clean up unprovisioned applications across the OS structure. powershell
Windows imaging does not have to be a black art. The constant failures—App Readiness, driver PKG, account corruption, bloatware interference—are all solvable. But solving them manually is a waste of your expertise.
0x8030002 or 0x800F0922 The Fix:
Do not waste time hunting for individual packages in the log files. Open and execute this master script to clean the image: powershell
Right-click the executable and select . You will see a clean interface with four tabs: Main, System Optimization, Appx Cleanup, and Driver Injection .
When Sysprep fails, it is usually due to modern Windows features like AppX packages or BitLocker encryption. 1. Resolve AppX Package Errors easy sysprep v3 final best fix
Easy Sysprep v3 (specifically the v3.1 Final release) serves as a specialized GUI wrapper and enhancement for the native sysprep.exe .
Once the environment is clean, run Sysprep with the ideal switches for cloning. Open the as an Administrator. Change the directory to the Sysprep folder: cd c:\windows\system32\sysprep Use code with caution. Execute the final, optimized command:
Once the prerequisites are ready, follow these steps: Get-AppxPackage -AllUsers | Where-Object $_
Follow these steps in exact order on your reference machine before running the Sysprep utility. Step 1: Remove Conflicting UWP App Packages
For more details, you can review the official Microsoft Sysprep failure and event logs to trace the exact cause.