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:


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:


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:


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.


When combined with the Remove-ProvisionedAppxPackage cmdlet, specific app packages can be removed from the current operating system image:


As you can see, the specified apps have been removed from the operating system image:


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.

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.



  1. Martin

    Is this something that can be done with an unattended installation?

  2. wouwie

    I tried this on a dutch enterprise version. All commands work but after the sysprep command, the apps appear anyway. Then I combined your post with
    and the apps do not appear anymore but the start button doesn’t work anymore.

  3. Renaud

    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

    • Mark


      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.

  4. Andrey

    Hi there,

    I’ve tried to run the script with MDT but apps are still there for new logged-in users.

  5. Julio Vivas

    The script must be run by user. It is better to create a GPO with the script at user login.

    I tested and it is working but is taking too much time to apply it.


Leave a Reply

%d bloggers like this: