Forum Discussion
Update-AppxPackage....where is it????
Hi Tguadagno​,
You're not going crazy - there's never been such a commandlet as Update-AppxPackage shipped in the operating system-native Appx module.
The article you've linked also doesn't make a lot of sense since the the attribute PackageFullName is version-specific, where an update to the application typically results in a change of version, which is more akin to executing Add-AppxPackage using the application Name attribute (which is version-agnostic).
If the PackageFamilyName of the detected store (or sideloaded) package matches the PackageFamilyName you already have installed, the MSIX engine will perform an update, while if it's not - which by default means it's more recent, it'll be added
I'm not sure where the author of that article got their information about such a commandlet.
Cheers,
Lain
- TguadagnoJul 14, 2025Copper Contributor
Lain, thanks for the validation, i am now thinking that this is an AI generated page meant to sell ads. I think it is hallucinating. the scary part is that i found this same command on at least 2 other sites....ug
brave new world
btw, do you know of any way to command a computer to upgrade Store Apps even for users not logged in?
thanks
- LainRobertsonJul 15, 2025Silver Contributor
It's not a scenario I've thought to look at before, and the Appx module is quite basic in nature. I also wouldn't say I'm an expert with MSIX behaviour since I've rarely worked with it.
If I were going to look at it, I expect I'd use group policy to deploy a scheduled task that runs perhaps once a day that runs a PowerShell script under the SYSTEM account which:
- Enumerates all staged packages (i.e Uses Get-AppxPackage -AllUsers);
- For each unique Name, run Add-AppxPackage -Register to installer the newer version.
From memory, MSIX is implemented so that it's "stored" in two locations:
- A staging area (there two areas: one for apps shipped with Windows and another for those added later from the store or sideloading);
- In the user profile (i.e. Within %APPDATA%\Packages).
So long as any user "updates" (as described in my previous reply) a package, the MSIX engine updates the staging location as well as the user profile location of the user making the Appx call.
Other existing users will have to perform their own Appx call to update their own user profile store, while new users will receive the new version from the staging area as part of their user profile creation.
What you cannot do - as far as I recall - is update an MSIX app for all users since there's no capacity to call Add-AppxPackage to target a different user. The store experience is based around a per user experience, not per system - as with traditional MSI-based management.
Cheers,
Lain