Forum Discussion

Copper Contributor

May 24, 2017

Solved

Retaining Removed Pre-Provisioned AppX Packages Across Feature Updates

We are testing out using Servicing Plans within ConfigMgr, and upon rolling our first 1703 Feauture Update, we have discovered that all the AppX packages we removed from our 1607 builds seemed to hav...

Nathan Mercer
May 31, 2017
After upgrading to Windows 10, v1703 in-box apps that were uninstalled by the user won't automatically reinstall as part of the Feature Update installation process. (Apps de-provisioned by IT administrators will still be reinstalled, this is expected to be addressed in the next Feature Update)

SigurdWerner

Iron Contributor

Jun 21, 2017

you can also remove the unwanted apps in the install.wim directly, so just mount the wim and run the PowerShell against the mounted wim. The newly created wim can be used in new installations and upgrade sequences, so you have a consisten configuration.

Eddie Leonard
Copper Contributor
Jun 21, 2017
Sigurd,

Thanks, I am aware and do that today. My post is around the Feature Update (patch) that is pushed, not new installs. It sounds like the fix is coming in 1709.

Eddie
- SigurdWerner
  Iron Contributor
  Jun 21, 2017
  Hey Eddie, we apply the feature update via ConfigManager update task sequence and are using the same customized wim for the update as for new installation (we still face to many issues after just applying the feature update: missing .net 3.5; language packs, Office needs to be repaired,...)
  - Eddie Leonard
    Copper Contributor
    Jun 21, 2017
    Are you referring to an "upgrade task sequence"? If so this is different than what I am referring to. I am talking about when you are on a version of Win10, say 1607, and you are going to 1703 using servicing plans.