Sysprep fails on removing or updating Provisioned Windows Store apps

Sysprep is widely used every bit Microsoft’s organization grooming tool for Windows operating organization deployment. It prepares an installation of Windows for duplication, auditing, together with client delivery. Sysprep is a command-line tool which tin dismiss survive run manually every bit good every bit through a script. This tool is extremely helpful for the information technology administrators who desire to laid upwards an installation of the Windows for duplication, auditing, together with client delivery.

Sysprep fails on Windows 10

As an information technology professional person or back upwards agent, you lot may meet Sysprep failure acre you lot are creating a Windows 10 reference PC/image or removing around of the side-loaded Appx packages from existing Windows image.

The mistake occurs if you lot withdraw or update provisioned Windows Store apps that include built-in Windows images. Removing or updating the Windows Store Apps which also include built-in Windows images volition final result inwards an mistake where the tool Sysprep may neglect to run.

If you lot have A fatal mistake occurred acre trying to Sysprep the machine  mistake message, at that topographic point could survive iii possible occupation scenarios for it to happen.

A fatal mistake occurred acre trying to Sysprep the machine

Scenario 1: Trying to Remove around of the provisioned Windows Store apps  

• In case, the user is creating a custom Windows 10 or Windows 8 reference figurer which he/she wants to Sysprep together with capture.
• The user wants to withdraw around of the built-in Windows Store apps (Appx packages) from this reference computer.
• The user runs dism -online /Remove-ProvisionedAppxPackage /PackageName:<packagename> to withdraw the Appx packages.
• Post the when the user tries to run the Sysprep functioning inwards this scenario, he/she mightiness become the higher upwards mistake together with the functioning may fail.

Scenario 2: Remove few side-loaded Appx packages from your ikon together with customize it

• In case, the user has an existing Windows image, also many Windows Store apps side-loaded inwards the image.
• The user wants to withdraw few of the side-loaded Appx packages from the ikon together with farther customize it.
• The user boots into the reference figurer together with farther runs i of the next PowerShell commands inwards monastic nation to withdraw the built-ins of the Appx package:
  • Remove-AppxProvisionedPackage –PackageName <PackageName>
  • Remove-ProvisionedAppxPackage –PackageName <PackageName>
• When the user tries to run Sysprep functioning inwards such a scenario, the functioning may neglect amongst the same mistake mentioned above.

Scenario 3: Update the built-in Windows Store apps past times using the Windows Store

• If the user is trying to exercise a Windows reference image
• The user connects to the Windows Store together with tries to update the provisioned Windows Store apps from the Windows Store.
• When the user tried to run Sysprep functioning inwards this scenario, the volition Pb to the functioning getting failed amongst the same mistake every bit mentioned above.

An additional provider has been added inwards Windows 10 inwards Sysprep, this is to build clean the Appx packages together with also to generalize the image. The provider plant solely amongst the next packages:

1. Per-user package: In this parcel the Appx parcel is installed for a detail user line concern human relationship solely together with is non available for other users of the same PC.
2. All-user package: In this parcel the Appx parcel has been provisioned into the images this allows all the users who run this ikon to access the app.

In the scenario where an all-user parcel which was provisioned into the ikon before together with was manually de-provisioned from the ikon but was non removed for a detail user, the provider volition become an mistake acre cleaning out this parcel acre running Sysprep.

The provider is also expected to neglect if illustration an all-user parcel which was provisioned into the ikon was updated past times of the users on the reference computer.

Removing the parcel for the user running Sysprep, together with also withdraw the provisioning tin dismiss assistance inwards resolving this issue. In monastic nation to foreclose the Windows Store from automatically updating the apps, only unplug the Internet connection or disable Automatic Updates inwards the Audit manner before creating the image.

KB2769827 lays downwardly the next steps to cook this issue:

1] Run the following PowerShell cmdlet:

Import-Module Appx

2] Run this next:

Import-Module Dism

3] Finally Run this command:

Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation

Check the below:

• In the output of this final cmdlet, cheque the users for whom the parcel is showing upwards every bit Installed. Delete these user accounts from the reference figurer or log on to the figurer past times using these user accounts. Then, run the cmdlet inwards footstep iv to withdraw the Appx package.
• This ascendency lists all packages that were published past times Microsoft together with installed past times whatever user of that reference computer. Because the figurer is to survive sysprepped, nosotros assume that these user profiles no longer involve the package.
• If you lot bring manually provisioned the apps which belong to other publishers. List them amongst the  command- Get-AppxPackage -AllUser | Format-List –Property PackageFullName,PackageUserInformation

4] Run this:

 Remove-AppxPackage -Package <packagefullname>

5] Remove the provisioning past times running the next cmdlet:

Remove-AppxProvisionedPackage -Online -PackageName <packagefullname>

Kindly banking concern annotation that this number does non occur if illustration you lot are servicing an offline image. In such scenario, the provisioning is cleared automatically for all the users together with also includes the user who genuinely runs the command.

Source: https://www.thewindowsclub.com/