Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get-TaskRemoveAppxProvisionedPackage should allow for querying off of DisplayName as well as PackageName #55

Open
marranaga opened this issue Aug 10, 2021 · 4 comments · May be fixed by #56

Comments

@marranaga
Copy link

The PackageName has additional information following the base name, which also includes version numbers, and can change for each version. When running these scripts via an automated method, it's difficult to remove AppX apps based off of the PackageName.

DisplayName                            PackageName
-----------                            -----------
Microsoft.549981C3F5F10                Microsoft.549981C3F5F10_1.1911.21713.0_neutral_~_8wekyb3d8bbwe
Microsoft.BingWeather                  Microsoft.BingWeather_4.25.20211.0_neutral_~_8wekyb3d8bbwe
Microsoft.DesktopAppInstaller          Microsoft.DesktopAppInstaller_2019.125.2243.0_neutral_~_8wekyb3d8bbwe
Microsoft.GetHelp                      Microsoft.GetHelp_10.1706.13331.0_neutral_~_8wekyb3d8bbwe
Microsoft.Getstarted                   Microsoft.Getstarted_8.2.22942.0_neutral_~_8wekyb3d8bbwe
Microsoft.HEIFImageExtension           Microsoft.HEIFImageExtension_1.0.22742.0_x64__8wekyb3d8bbwe
Microsoft.Microsoft3DViewer            Microsoft.Microsoft3DViewer_6.1908.2042.0_neutral_~_8wekyb3d8bbwe
Microsoft.MicrosoftEdge.Stable         Microsoft.MicrosoftEdge.Stable_84.0.522.52_neutral__8wekyb3d8bbwe
Microsoft.MicrosoftOfficeHub           Microsoft.MicrosoftOfficeHub_18.1903.1152.0_neutral_~_8wekyb3d8bbwe
Microsoft.MicrosoftSolitaireCollection Microsoft.MicrosoftSolitaireCollection_4.4.8204.0_neutral_~_8wekyb3d8bbwe
Microsoft.MicrosoftStickyNotes         Microsoft.MicrosoftStickyNotes_3.6.73.0_neutral_~_8wekyb3d8bbwe
Microsoft.MixedReality.Portal          Microsoft.MixedReality.Portal_2000.19081.1301.0_neutral_~_8wekyb3d8bbwe
Microsoft.MSPaint                      Microsoft.MSPaint_2019.729.2301.0_neutral_~_8wekyb3d8bbwe
Microsoft.Office.OneNote               Microsoft.Office.OneNote_16001.12026.20112.0_neutral_~_8wekyb3d8bbwe
Microsoft.People                       Microsoft.People_2019.305.632.0_neutral_~_8wekyb3d8bbwe
Microsoft.ScreenSketch                 Microsoft.ScreenSketch_2019.904.1644.0_neutral_~_8wekyb3d8bbwe
Microsoft.SkypeApp                     Microsoft.SkypeApp_14.53.77.0_neutral_~_kzf8qxf38zg5c
Microsoft.StorePurchaseApp             Microsoft.StorePurchaseApp_11811.1001.1813.0_neutral_~_8wekyb3d8bbwe
Microsoft.VCLibs.140.00                Microsoft.VCLibs.140.00_14.0.27323.0_x64__8wekyb3d8bbwe
Microsoft.VP9VideoExtensions           Microsoft.VP9VideoExtensions_1.0.22681.0_x64__8wekyb3d8bbwe
Microsoft.Wallet                       Microsoft.Wallet_2.4.18324.0_neutral_~_8wekyb3d8bbwe
Microsoft.WebMediaExtensions           Microsoft.WebMediaExtensions_1.0.20875.0_neutral_~_8wekyb3d8bbwe
Microsoft.WebpImageExtension           Microsoft.WebpImageExtension_1.0.22753.0_x64__8wekyb3d8bbwe
Microsoft.Windows.Photos               Microsoft.Windows.Photos_2019.19071.12548.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsAlarms                Microsoft.WindowsAlarms_2019.807.41.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsCalculator            Microsoft.WindowsCalculator_2020.1906.55.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsCamera                Microsoft.WindowsCamera_2018.826.98.0_neutral_~_8wekyb3d8bbwe
microsoft.windowscommunicationsapps    microsoft.windowscommunicationsapps_16005.11629.20316.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsFeedbackHub           Microsoft.WindowsFeedbackHub_2019.1111.2029.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsMaps                  Microsoft.WindowsMaps_2019.716.2316.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsSoundRecorder         Microsoft.WindowsSoundRecorder_2019.716.2313.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsStore                 Microsoft.WindowsStore_11910.1002.513.0_neutral_~_8wekyb3d8bbwe
Microsoft.Xbox.TCUI                    Microsoft.Xbox.TCUI_1.23.28002.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxApp                      Microsoft.XboxApp_48.49.31001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxGameOverlay              Microsoft.XboxGameOverlay_1.46.11001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxGamingOverlay            Microsoft.XboxGamingOverlay_2.34.28001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxIdentityProvider         Microsoft.XboxIdentityProvider_12.50.6001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxSpeechToTextOverlay      Microsoft.XboxSpeechToTextOverlay_1.17.29001.0_neutral_~_8wekyb3d8bbwe
Microsoft.YourPhone                    Microsoft.YourPhone_2019.430.2026.0_neutral_~_8wekyb3d8bbwe
Microsoft.ZuneMusic                    Microsoft.ZuneMusic_2019.19071.19011.0_neutral_~_8wekyb3d8bbwe
Microsoft.ZuneVideo                    Microsoft.ZuneVideo_2019.19071.19011.0_neutral_~_8wekyb3d8bbwe


@OSDeploy
Copy link
Owner

When you say these names can change for each version, what Version do you mean? Builds like 20H1 20H2, or Version Patch 19042.xxxxx and 19042.yyyyyyy?

@marranaga
Copy link
Author

Apologies, should have been more clear. The individual application versions are built into the PackageName. As that specific app updates overtime, the string will be slightly different. Alternatively, the DisplayName property never changes.

@OSDeploy
Copy link
Owner

I wasn't asking for clarification, just what your use case was, which you didn't answer. What I believe you are trying to do is take a JSON configuration for one OS Build and apply to a different OS Build. Is that accurate?
The reason I ask is that I originally intended the JSON files to be unique for one OS Build, which does not change the Package Name, unless this is now changing because MS is releasing monthly updates on MVLS. I'm not certain on this though.
So asking again for clarification on if you are using the JSON for different OS's or not so I can determine if this is a BUG or a Feature Request

@marranaga
Copy link
Author

Ohh, I'm sorry. Yes, I am using the same JSON for different OS versions that way we can have an automated process to update the OS each month. I've been using this practice for about a year now, and so far, everything has been working great. The only issue we've run into recently is that it's not removing the unique AppX PackageNames that aren't working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants