Forum Discussion
Removing UWP apps from the 1709 Build
When needed we typically use a PowerShell script during the build and capture task sequence that removes all apps and on-demand features except the ones we explicitly specify. I like this script from Nickolaj: http://www.scconfigmgr.com/2016/03/01/remove-built-in-apps-when-creating-a-windows-10-reference-image/
Just be aware about removing is one thing, putting stuff back at a later time may be impossible without re-imaging the machine.
- Markus KlockerMay 25, 2018Copper Contributor
So with SCCM you possibly have a WSUS in place.
I figured that the cmdlet "Get-WindowsCapability -online" symply fails and therefore "Quickassist" and "ContactSupport" can't be removedin 1709.
- DiogoSousaJan 12, 2018Iron Contributor
Hello and greetings from Portugal!
For me, the best way to completely get rid of the apps and make sure they don't appear again is by running a powershell script during custom image creation and removing both app and provisioned package.
Here some examples for Windows 10 Enterprise:
#Microsoft Bing Weather Remove-AppxPackage -Package Microsoft.BingWeather_4.21.2492.0_neutral_~_8wekyb3d8bbwe | Out-Null Remove-AppxProvisionedPackage -PackageName Microsoft.BingWeather_4.21.2492.0_neutral_~_8wekyb3d8bbwe -Online | Out-Null #Microsoft Tips (Get Started) Remove-AppxPackage -Package Microsoft.Getstarted_5.11.1641.0_neutral_~_8wekyb3d8bbwe | Out-Null Remove-AppxProvisionedPackage -PackageName Microsoft.Getstarted_5.11.1641.0_neutral_~_8wekyb3d8bbwe -Online | Out-Null #Microsoft Mail and Calendar Remove-AppxPackage -Package microsoft.windowscommunicationsapps_2015.8241.41275.0_neutral_~_8wekyb3d8bbwe | Out-Null Remove-AppxProvisionedPackage -PackageName microsoft.windowscommunicationsapps_2015.8241.41275.0_neutral_~_8wekyb3d8bbwe -Online | Out-Null #Microsoft Messaging Remove-AppxPackage -Package Microsoft.Messaging_2017.815.2052.0_neutral_~_8wekyb3d8bbwe | Out-Null Remove-AppxProvisionedPackage -PackageName Microsoft.Messaging_2017.815.2052.0_neutral_~_8wekyb3d8bbwe -Online | Out-Null #Microsoft Office Hub (Get Office) Remove-AppxPackage -Package Microsoft.MicrosoftOfficeHub_2017.715.118.0_neutral_~_8wekyb3d8bbwe | Out-Null Remove-AppxProvisionedPackage -PackageName Microsoft.MicrosoftOfficeHub_2017.715.118.0_neutral_~_8wekyb3d8bbwe -Online | Out-Null #Microsoft Office OneNote Remove-AppxPackage -Package Microsoft.Office.OneNote_2015.8366.57611.0_neutral_~_8wekyb3d8bbwe | Out-Null Remove-AppxProvisionedPackage -PackageName Microsoft.Office.OneNote_2015.8366.57611.0_neutral_~_8wekyb3d8bbwe -Online | Out-Null
- Clifton HughesFeb 28, 2018Former Employee
Hi, were you able to use this script you referenced in your comment on Windows 10 1709?
- DiogoSousaFeb 28, 2018Iron Contributor
Hi there,
Yep, had no problems but it's true that from 1511 to 1709 I needed to make some adjustments, basically because some apps were not on 1709.
But are you having issues?Best Regards,
Diogo Sousa
- Neil GoldsteinJan 30, 2018Iron ContributorIts to bad that Windows MDM setting under https://docs.microsoft.com/en-us/intune/device-restrictions-windows-10#app-store "Store originated app launch - Used to disable all apps that were pre-installed on the device, or downloaded from the Microsoft Store" blocks more than pre-installed. I am right now trying to see if enforcing Private Store only will de-provision pre-installed using "Use private store only" -Neil