Remove App Packages from Windows 10 Enterprise Edition

So you’ve installed Windows 10 enterprise edition only to find applications that you would consider to be consumer type apps such as Bing Finance, News, and Sports which is not what you would normally expect to find in an enterprise edition operating system version:

You can obtain a list of these app packages for the current user with the Get-AppxPackage PowerShell cmdlet. I’ve sorted the list of app packages by name in the following results:

PowerShell

1

Get-AppxPackage|Sort-Object-PropertyName|Select-Object-PropertyName

I’ve determined which app packages that I want to remove and I’ll remove them for the current user with the following PowerShell script:

The app packages that were previously removed no longer exist for the current user:

PowerShell

1

Get-AppxPackage|Sort-Object-PropertyName|Select-Object-PropertyName

One thing to keep in mind is this occurs for the current user so if you’re logging into your machine as a non-admin (which I highly recommend) and you run PowerShell elevated, whatever user you specify when you’re prompted for elevation is the user account the applications will be removed for. This will make it appear as if the command didn’t work.

The secret to removing these applications for the current user is that PowerShell doesn’t need to run elevated (run an admin) as shown in the previous examples where the PowerShell console doesn’t say “Administrator” in the title bar of the console window.

When complete, you should notice that those applications have been removed from your start menu, screen, or whatever they’re calling it now days:

Get-AppxPackage does have an AllUsers parameter but that only retrieves applications for all users and doesn’t remove them for all users when piping to Remove-AppxPackage.

You could also walk through the applications one by one and remove the desired ones by simply piping Get-AppxPackage to Remove-AppxPackage using the Confirm parameter:

PowerShell

1

Get-AppxPackage|Remove-AppxPackage-Confirm

What if you want to prevent these applications from being installed for any new user that’s created on your machine? Well, you’re in luck because these’s a cmdlet for that.

The Get-AppxProvisionedPackage cmdlet retrieves a list of app packages that are set to be installed for each new user that’s created. Note that this command does require elevation.

The Remove-AppxProvisionedPackage cmdlet doesn’t remove the app packages that are already installed for any preexisting users, but it does prevent any new users from receiving the app packages that are removed from the operating system image.

Update I received notification from fellow PowerShell MVP Emin Atac that there’s a known problem where sysprep fails after removing or updating Windows built-in Windows Store apps as referenced in KB2769827 so take that into consideration when removing apps.

Thank you for your very detailled article. I use this technic in my sccm task sequence TS and all apps like Xbox for example are gone at the end of the OSD. But, i did an inplace upgrade from 10.0.240 to Windows 10 1511 with sccm current branch on my already deployed workstations and all this apps are back with the new version of Windows 10. Do you know how can i prevent those apps to reinstall after inplace upgrade ? Thanks

You would need to deploy the removal again after the upgrade to 1511. I was at a MS W10 deployment meeting a couple of weeks ago and this very thing was brought up. The MS technician clearly stated that branch updates are complete new kernel sources and thus are basically a complete OS reinstall. To add to that he also stated that as such these AppX packages will indeed be reinstalled with any branch update that they publish.

Thank you, you are 1 of 25 blogs who does explain it CORRECT and right.

There is a 1) SYSTEM part and 2) a per user APPX part. If you want to automate this on a deployment you will need a SYSTEM package and one THAT RUNS per user account THAT was already ON the W10 client. If you USE Roaming profiles and the user has LOGGED on to another W10 you will also have to REMOVE those APPX per user on the machine (Or per roaming profile).

There has been a error with the 15XX to 1607 Migration where the APPX Came then Back after migration. MS called it a bug but it was by purpose. (ENTERPRISE Edition CBB)

My Speaking Engagements

User Groups

Disclaimer

All data and information provided on this site is for informational purposes only. Mike F Robbins (mikefrobbins.com) makes no representations as to accuracy, completeness, currentness, suitability, or validity of any information on this site and will not be liable for any errors, omissions, or delays in this information or any losses, injuries, or damages arising from its display or use. All information is provided on an as-is basis.