3 ms·
The issue is you used to be able to remove apps at any time and then set that profile to be a default profile. Once these junkware apps are provisioned once it
by privateSFacct 7y ago
The issue is you used to be able to remove apps at any time and then set that profile to be a default profile.
Once these junkware apps are provisioned once it's a much bigger pain to get them out of default profile land. In other words, you'd better boot straight into audit mode, have everything lined up right to clean this stuff up. And yes, that is Remove-AppxProvisionedPackage . How about adding Remove-AllJunk with some sane defaults?
And why have to do this? I'm the one paying per seat on these installs - and instead of solving problems I am given a bunch of problems.
- basch 7y agoWhy do you need to boot into audit mode? Get-AppXProvisionedPackage -Online | Select PackageName Remove-AppXProvisionedPackage -Online -PackageName <PackageName> Your Remove-AllJunk is basically Get-AppXProvisionedPackage -Online | Remove-AppxProvisionedPackage -Online
- privateSFacct 7y agoTotally false. You realize even just an automatic update blows things up? https://support.microsoft.com/en-us/help/2769827/sysprep-fails-after-you-remove-or-update-windows-store-apps-that-inclu https://support.microsoft.com/en-us/help/2769827/sysprep-fai... "You want to remove some of the side-loaded Appx packages from your image and customize it further. You boot into the reference computer and run one of the following PowerShell commands to remove the provisioning of the Appx package: Remove-AppxProvisionedPackage –PackageName <PackageName> Remove-ProvisionedAppxPackage –PackageName <PackageName> When you run sysprep operation in this scenario, the operation may fail with the following error: System Preparation Tool 3.14 A fatal error occurred while trying to sysprep the machine"