Share via

APPX Packages disabled in 1809 WIM - returning after 1909 Upgrade

Anonymous
2020-01-30T22:10:44+00:00

Hello,

I have removed all but roughly 10 APPX packages from the WIM we use during SCCM deployment.  The packages are disabled, they are not in the Start menu, and all is working fine in 1809.  Here is the 'before' result of Get-ProvisionedAppxPackage:

Get-ProvisionedAppxPackage -Online | select displayname

DisplayName                   

-----------                   

Microsoft.GetHelp             

Microsoft.HEIFImageExtension  

Microsoft.MicrosoftStickyNotes

Microsoft.MSPaint             

Microsoft.VP9VideoExtensions  

Microsoft.WebMediaExtensions  

Microsoft.WebpImageExtension  

Microsoft.Windows.Photos      

Microsoft.WindowsAlarms       

Microsoft.WindowsCalculator   

After upgrading to 1909, again using SCCM, APPX packages are being restored.   I know before 1709 there was a problem that required the addition of the disabled packages to a registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Deprovisioned], but that after 1803 that was not necessary.  I have been adding it to the registry in the image anyway, just to be sure.  However, that doesn't seem to help in this case, because all of the 1909 upgraded computers have the APPX packages back.  Here is the 'after' result of Get-ProvisoinedAppxPackage on the same computer, after 1909 installed:

Get-ProvisionedAppxPackage -Online | select displayname

DisplayName                           

-----------                           

Microsoft.BingWeather                 

Microsoft.DesktopAppInstaller         

Microsoft.GetHelp                     

Microsoft.Getstarted                  

Microsoft.HEIFImageExtension          

Microsoft.Messaging                   

Microsoft.Microsoft3DViewer           

Microsoft.MicrosoftOfficeHub          

Microsoft.MicrosoftSolitaireCollection

Microsoft.MicrosoftStickyNotes        

Microsoft.MixedReality.Portal         

Microsoft.MSPaint                     

Microsoft.Office.OneNote              

Microsoft.OneConnect                  

Microsoft.People                      

Microsoft.Print3D                     

Microsoft.ScreenSketch                

Microsoft.SkypeApp                    

Microsoft.StorePurchaseApp            

Microsoft.VP9VideoExtensions          

Microsoft.Wallet                      

Microsoft.WebMediaExtensions          

Microsoft.WebpImageExtension          

Microsoft.Windows.Photos              

Microsoft.WindowsAlarms               

Microsoft.WindowsCalculator           

Microsoft.WindowsCamera               

microsoft.windowscommunicationsapps   

Microsoft.WindowsFeedbackHub          

Microsoft.WindowsMaps                 

Microsoft.WindowsSoundRecorder        

Microsoft.WindowsStore                

Microsoft.Xbox.TCUI                   

Microsoft.XboxApp                     

Microsoft.XboxGameOverlay             

Microsoft.XboxGamingOverlay           

Microsoft.XboxIdentityProvider        

Microsoft.XboxSpeechToTextOverlay     

Microsoft.YourPhone                   

Microsoft.ZuneMusic                   

Microsoft.ZuneVideo   

Can you please tell me what the precise method is to keep APPX packages that were removed from the WIM from being restored during the 1909 upgrade?

Thank you

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2020-03-11T15:12:06+00:00

    I'm seeing the exact same thing. The fact that this post is over 40 days old and not a single reply is concerning. It's frustrating because Microsoft saw this was a problem, implemented a fix, and now ignores it. Every feature update feels like 2 steps forward, 2 steps back. I'm sitting here with thousands of enterprise computers running 1709 staring at an end of life date with no clear path forward because of things like this. Windows 10 has been out for almost 5 years now, at what point can we expect things to stop being broken?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-02-20T15:54:46+00:00

    This problem is continuing.   I eagerly await any advice or assistance from Microsoft.

    Was this answer helpful?

    0 comments No comments