Sysprep fails because of package Windows.ContactSupport [Build 14393]

[tale]

I'm doing a quick build and capture with Windows 10 Build 14393 (1607) in which I have a script that removes some of the default installed apps. It's being done with System Center.

 

In regards to the Contact app, it's now able to be uninstalled as a package.

$Packages = (Get-WindowsPackage -Online).PackageName

ForEach ($Package in $Packages) {

If ($Package -like "*ContactSupport*") {

Remove-WindowsPackage -Online -PackageName "$Package" -NoRestart

}

}

It is removed with no issues, won't appear in the start menu for any users, but Sysprep will fail because of it.

[setuperr.log]

Failed to remove staged package Windows.ContactSupport_10.0.14393_.........

Failed to remove apps for the current user: 0x80070002

 

When I log in to the VM after it fails, Windows.ContactSupport only appears if I run "Get-AppxPackage -AllUsers" where it says it's still staged {S-1-5-18 [s-1-5-18]: Staged} by NT AUTHORITY\SYSTEM

If I even try to run powershell.exe as SYSTEM and now try Remove-AppxPackage it just fails like it used to and can't be resolved.

 

 

 

Has anyone run in to this and able to fix it? Or should I just stop trying to remove "Contact Support" and leave it like the last Windows 10 OS builds had to be?

 

[Rackel Gems]

Hello.

I think in the Creators update, there are certain options where you can disallow passing diagnostic information.

Instead of totally removing the particular packages , it's always safe to use the default option present in Windows 10.

That way, you won't  crash anything. Otherwise, we don't know what ripple effect each problem creates. 

[PS14]

Hello,

 

I had the same problem at first then changed TS to launch remove-appx task after Sysprep.

I did this for several appx-packages and it runs.