I while back I wrote a script and published it on Github that allows us to run one step in our Task Sequence to remove the builtin apps and it reads two text files for each version of Windows 10 so we have total control of what we uninstall. It is really simple to update by creating two new files, one for Capabilities that should be removed and of for the Apps we want to remove. On request I have updated the .zip file on Github with sample files for Windows 10 1809 as well.
The original post can be found here: https://ccmexec.com/2018/04/windows-10-remove-builtin-apps-script-with-multiple-version-support/
The updated script can be downloaded here: https://github.com/Ccmexec/MEMCM-OSD-Scripts
8 thoughts on “Updated script to Remove Builtin apps in Windows 10 1809”
Hello Jörgen, once again excellent work.I have a question about the subject.We have the “remove-AppxPackage” that runs in the context of the user and the “remove-AppxProvisionedPackage” that runs in the context of the device, OK.I’m in a situation where I’m upgrading the build of Windows 10 1511 to build 1803 (using the SUP process) and I’ll need to remove the default Windows 10 apps, using your script as a base, a part of it I’ll use to remove the apps in the context of the user (creating a package in SCCM and applying to a collection) and ProvisionedPackage will use the method of the application to withdraw in the context of the device. Would I have another method for this or am I on the right track to remove these apps?
Thanks for the scripts, works great when i deploy the package to a machine via software center, but the same package when applied via TS doesn’t work, any ideas where i may be going wrong?
Thanks Jorgen for this script. I have been looking for this script. I will test this in my lab setup today.
The script works great, 98% of the time. Periodically, a system will get hung up on the RemoveApp.ps1 step and not time-out either, leaving the TS running for a indeterminable amount of time. When I review the log, its stopping at different places.
Yes it is a know issue in Windows 10 1803 & 1809 after the January CU, MS is aware of the issue and working on it.
at my school a lot of computers hangs in the script with i use in sccm deployment. sometimes after 2,3, or 4 times it works, but it is not reliable to deploy the build over the whole school at this point. I hope the next build 1903 works better with this. Or do you know another workaround to let it work well?
It works just fine in 1903, I remove the builtin apps in the .wim instead in 1809 now until we get a fix for it.
Hi Jorgen, do you or anyone else know how to keep track as to when Microsoft provide a fix for this? We are deploying 1809 and causing a real headache! Or can you explain how you remove them from the .wim? Build and capture? Thanks.