Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED GP to disable Microsoft Auto-install builtin Apps

  • Thread starter Thread starter Edy
  • Start date Start date
  • Replies Replies 2
  • Views Views 1K
Status
Not open for further replies.

Edy

Well-Known Member
Messages
310
Solutions
3
Reaction score
33
Points
28
Hi guys,

This in relation to Windows Servicing when upgrading to newer Windows OS that Microsoft automatically re-install the built-in apps. I would like to apply this before doing the OS upgrade.

I found an article regarding the above but i couldnt find it anymore.

Please shed some light.

Thanks
 
Hi guys,

This in relation to Windows Servicing when upgrading to newer Windows OS that Microsoft automatically re-install the built-in apps. I would like to apply this before doing the OS upgrade.

I found an article regarding the above but i couldnt find it anymore.

Please shed some light.

Thanks
Hey Edy, this is bit weird. I have used 1709 in our OSD and used Windows 10 servicing to get 1803 and 1809 and the built-in apps haven't been installed again. I am using a PS script for the OSD TS to remove this MS rubbish apps.

Answering your question; I don't think it'll be possible to do this within the feature update since SCCM admins don't have any control over this update apart from scheduling and deploying it.

I'd confirm first if these built-in applications were removed correctlty in the first place before the upgarde.
Here is the PS script I am using you can deploy it to the collections that have received the Feature Update as a workaround.

I haven't written this script so no credit for me :) I am just sharing it.
 

Attachments

Thanks Mahmoud. I have also used a similiar script during imaging to remove those builtin apps.

I found this article TechNet

Looks like the issue is fixed on 1803 and since am updating from 1607 the issue is still persist.
 
Status
Not open for further replies.
Back
Top