Provisioned Packages (Provisioned Apps) in Windows 10 Pro



Click here to get to the updated article.

Updated on 24th October 2017

By default Microsoft Windows 10 Pro ships with a number of provisioned app packages. Whenever a user signs into a computer for the first time, Windows will register (read: installed) all provisioned apps in the newly created user profile.

For listing the provisioned app packages on your computer, use the PowerShell Cmdlet Get-AppxProvisionedPackage.

Get-AppxProvisionedPackage -Online | Select DisplayName | Sort DisplayName

List of Provisioned App Packages

This list provides a reference of each provisioned app package in Windows 10 Pro along the name of the app and a link to the Windows Store.

DisplayNameApp Name & Store Linkv1607v1703v1709
Microsoft.3DBuilder3D Builder
Microsoft.BingWeatherMSN Weather
Microsoft.DesktopAppInstallerApp Installer
Microsoft.GetHelpGet Help  
Microsoft.GetstartedMicrosoft Tips
Microsoft.MessagingMicrosoft Messaging
Microsoft.Microsoft3DViewerMixed Reality Viewer 
Microsoft.MicrosoftOfficeHubGet Office
Microsoft.MicrosoftSolitaireCollectionMicrosoft Solitaire Collection
Microsoft.MicrosoftStickyNotesMicrosoft Sticky Notes
Microsoft.MSPaintPaint 3D 
Microsoft.OneConnectPaid Wi-Fi & Cellular
Microsoft.PeopleMicrosoft People
Microsoft.Print3DPrint 3D  
Microsoft.StorePurchaseAppStore Purchase App1
Microsoft.Windows.PhotosMicrosoft Photos
Microsoft.WindowsAlarmsWindows Alarms & Clock
Microsoft.WindowsCalculatorWindows Calculator
Microsoft.WindowsCameraWindows Camera
microsoft.windowscommunicationsappsMail and Calendar
Microsoft.WindowsFeedbackHubFeedback Hub
Microsoft.WindowsMapsWindows Maps
Microsoft.WindowsSoundRecorderWindows Voice Recorder
Microsoft.WindowsStoreWindows Store
Microsoft.Xbox.TCUIXbox TCUI  
Microsoft.XboxGameOverlayXbox Game Bar 
Microsoft.XboxIdentityProviderXbox Identity Provider
Microsoft.XboxSpeechToTextOverlayXbox Speech to Text Overlay1 
Microsoft.ZuneMusicGroove Music
Microsoft.ZuneVideoMovies & TV

1 unavailable in App Store

Personal Recommendation for Current Release

In a business environment it is likely that most of the provisioned apps that come with the standard Windows 10 Pro image are not needed or unwanted. If you are uncertain whether it is safe to remove a provisioned app, or whether you should do so, please find my personal recommendation for a small business below. This list always reflects the current version of Windows 10 Pro at the time of the last edit of this article.

  • Microsoft.3DBuilder
    Safe to remove.
  • Microsoft.BingWeather
    Safe to remove. I prefer to keep the app. A good amount of my users appreciate using the app and many have them pinned to Start. Also, the live tile looks nice.
  • Microsoft.DesktopAppInstaller
    Safe to remove, unless you sideload custom or LOB applications.
  • Microsoft.Getstarted
    Safe to remove.
  • Microsoft.Messaging
    Safe to remove, especially if don’t allow your users to link their private Microsoft accounts to their user profile.
  • Microsoft.MicrosoftOfficeHub
    Remove it. This is just an advertisement for Microsoft Office 365 and useless regardless of whether you already use Office or plan to use Office in the future.
  • Microsoft.MicrosoftSolitaireCollection
    Safe to remove. Unless your company has a policy against games, I would prefer to keep it. It’s nice to offer some distraction during a users lunch break. (Although I always prefer to take a walk in the park, before sitting at my computer yet another hour every day ?).
  • Microsoft.MicrosoftStickyNotes
    Safe to remove.
  • Microsoft.Office.OneNote
    Safe to remove. Especially if your company uses Microsoft Office since it brings the full version of OneNote.
  • Microsoft.OneConnect
    Safe to remove.
  • Microsoft.People
    Safe to remove. Especially if you use Microsoft Outlook. Some users may get confused between Outlook Contacts (which can be shared within the company) and People app contacts.
  • Microsoft.SkypeApp
    Safe to remove. Especially if your company uses an Office suite that includes Skype for Business.
  • Microsoft.StorePurchaseApp
    Safe to remove. Only used in apps that support in-app purchases. Since we don’t want this in our company, I prefer to just remove it.
  • Microsoft.Windows.Photos
    Keep it, unless you use a 3rd-party application to view image files.
  • Microsoft.WindowsAlarms
    Safe to remove.
  • Microsoft.WindowsCalculator
    Keep it, unless you feast off your users tears or rage.
  • Microsoft.WindowsCamera
    Safe to remove on Desktops and Workstations. I would keep it on portable Computers.
  • microsoft.windowscommunicationsapps
    Safe to remove. This is the Mail & Calendar app. Definitely remove it if you use Microsoft Outlook or a 3rd-party mail application. People will get confused and if you use Office 365 I guarantee at least one user will configure their email account on it and cause you some amount of headache.
  • Microsoft.WindowsFeedbackHub
    Safe to remove.
  • Microsoft.WindowsMaps
    Safe to remove. At the moment I prefer to keep it since it has at least some amount of utility.
  • Microsoft.WindowsSoundRecorder
    Safe to remove.
  • Microsoft.WindowsStore
    I am still uncertain about this app. In our company we don’t want users to use the store, but I don’t know what consequences this might have. I decided to keep it for now.
  • Microsoft.XboxApp
    Remove it. Definitely not needed on company computers even if you decide to keep Solitaire.
  • Microsoft.XboxIdentityProvider
    Remove it. Definitely not needed on company computers even if you decide to keep Solitaire.
  • Microsoft.ZuneMusic
    Keep it, unless you use a 3rd-party application to play audio files.
  • Microsoft.ZuneVideo
    Keep it, unless you use a 3rd-party application to play video files.


24 responses to “Provisioned Packages (Provisioned Apps) in Windows 10 Pro”

  1. Bill Avatar

    Save to remove? Safe?

    1. Daniel Avatar

      Oops, thanks mate.

  2. Tim Gelhardt Avatar
    Tim Gelhardt

    I have ran a bunch of these commands to remove Windows Modern Apps. I used the Get-AppxPackage -allusers PackageFullName | Remove-AppxPackage with the assumption that is what would happen. After running sysprep (this is my master imaging VM) and powering the VM back on, I had to go through the initial MS setup (out of box experience) and it forced me to create a new user account. OK, fine, well when I logged in with the 2nd user account all of the apps I removed using my main local account prior to sysprep are still on here for any new user that logs in.
    Please advise. I need to use this build to create my Win10 imaging utility and I do not want to have to run all these powershell commands everytime I build a new machine and log in with a new user.

    1. Daniel Avatar

      Tim, Get-AppxPackage gets a list of the app packages that are installed in a particular user profile. You can use -AllUsers to lists app packages for all user accounts on the computer. However, you can only remove installed app packages from the user account you are logged on with. You find more information about removing apps on my other blog post:

    2. Ree Avatar

      Why don’t you just write a script? It would be simple to write in notepad++, save as a Powershell script and then run. Or I would set up a windows10 box exactly how you would like and save that as an Image and then use your image to setup your new system.

  3. GM Avatar

    get-appxpackage MicrosoftSolitaireCollection | Remove-AppxPackage will remove from current user,
    Get-AppXProvisionedPackage -online | WHere-Object {$_.packagename -like “*MicrosoftSolitaireCollection*”} | Remove-AppxProvisionedPackage -online will remove the provisioning so that NEW profiles wont have them available either.

    1. GM Avatar

      put “asterisks” around the MicrosoftSolitaireCollection

  4. GM Avatar

    1703 adds a few more XBOX ones to the fray – Microsoft.XboxSpeechToTextOverlay Microsoft.XboxIdentityProvider Microsoft.XboxGameOverlay

    Versions > 1703 should remember what provisioning you have killed.

    Oh and if you accidentally remove a provisioned app and you want it back then you CAN add it back. You need the “Windows 10 Inbox Apps” ISO (available from VLSC if you are volume customers, if you aren’t volume customers then I have no idea I’m afraid – I cant imagine it is a hard to find). Then mount the ISO and run:

    Add-AppxProvisionedPackage -Online -PackagePath “X:\amd64fre\Microsoft.WindowsStore_8wekyb3d8bbwe.appxbundle” –LicensePath “X:\amd64fre\Microsoft.WindowsStore_8wekyb3d8bbwe.xml”

    (this adds the store back for example)

    1. GM Avatar

      forgot to add, you will need a “clean” machine to get the “packagename” from, the packagename comes from the Get-AppxProvisionedPackage -Online command – again these aren’t secret though so any will do. I suspect you will need to use the same build version though.

  5. Jeff E. Avatar
    Jeff E.

    I had opened a ticket with MS on this and here’s what they had me do (summarized)

    Mount the Win10 ISO
    Copy the install.wim to another folder
    Use DISM to mount the install.wim and then run remove-appx commands to get rid of stuff I didn’t want
    Most importantly, you have to do an offline registry edit and add the key “CloudContent” to HKLM\Policies\Microsoft\Windows and create a DWORD entry “DisableWindowsConsumerFeatures” and set the value to 1. This prevents all the consumer apps you’ve removed from automatically streaming back down when a new user logs in.
    Then after committing your changes and unmounting the WIM, you import the install.wim into MDT and then deploy that to a blank VM. Build your image on that blank VM and then sysprep and capture and you’ll be good.

    Mind you, these are highly summarized steps but there should be a good doc online on how to do this.

    1. Daniel Avatar

      Jeff, did you open a ticket for Windows 10 Enterprise? As far as I know the Pro edition still ignored the “DisableWindowsConsumerFeatures” registry entry.

  6. SIdney Avatar

    Thanks for this, helped me out 🙂 !

  7. ethanthekiwi Avatar

    I removed several apps from a Windows 10 1709 image (downloaded from Volume License center). After install I found out that users can’t open the Windows Store (which I wanted to work), I tried to fix the Windows Store and got an error that Microsoft.NET.Native.Runtime.1.4 was missing. I went back and installed a clean image and removed programs one at a time and found that when I removed Microsoft.OneConnect, Microsoft.NET.Native.Runtime.1.4 was also removed. I also noticed that when I removed Microsoft.XboxIdentityProvider, Microsoft.NET.Native.Runtime.1.3 was also removed. I assume this is some kind of bug on Microsoft’s end.

  8. […] other scripts to get a good idea of what I would consider safe to remove.  I’ll also share this blog post that has a pretty decent description of most of the AppX packages as well as further suggestions on […]

  9. FC-EricW Avatar

    In my 1709 test deployments, Windows Update (using SCCM) is borked if you remove Store. We’re using Group Policy to disable access instead.

  10. First Last Avatar
    First Last

    Thanks so much! Been looking for a M$oft reference on what is safe to remove but they don’t seem to want people removing anything.

  11. David Aslan French Avatar

    Hey just wanted to say thanks for posting this! Was super super helpful!

    1. Daniel Avatar

      Hi David, thank you for your kind words. I just updated it to reflect the current Windows 10 version 1803.

  12. Joey Avatar

    Hi Daniel…..To repeat others – thank you for your informative breakdown of safe and unsafe. I’ve used your info in our own image process.
    Since I’ve started doing v1803 I have checked back a few times to see if you may have updated this. Looking forward to an update soon?
    Appreciate your time and efforts in this.

    1. Daniel Avatar

      Hi Joey, thank you for your interest in my article. I just updated it to reflect the current Windows 10 version 1803.

  13. JP BERGEZ Avatar

    Great job ! Thank you very much.
    Any update expected for 18xx versions (1803 and future 1809) ?

    1. Daniel Avatar

      Hi JP, thank you for your interest in my article. I just updated it to reflect the current Windows 10 version 1803.

Leave a Reply

Your email address will not be published. Required fields are marked *