Article：
http://stackoverflow.com/questions/13865930/how-to-uninstall-an-app-that-another-user-installed
Cause of the problem:
Windows Update (WU) downloads newer versions of packages you have and “stages” them as Local System, so that when you go to the storeto update the apps, the update process is as quick as possible. WUwill eventually clean up the staged packages that were neverinstalled.
What are some consequences of having "Staged" packages?
1.Staged packages prevent you from installing thatparticular package in development mode
2.Staged packages eat up some disk space, but due tohardlinking, the effect of this is mitigated. If a file is identical betweenmultiple versions of a package, appx deployment hardlinks the filesinstead of maintaining two separate copies of the same file.
How do I find the "Staged" packages?
1.In an administrator powershell prompt, the command:
Get-Appxpackage -All
will display all packages on the machine. For a stagedpackage, the PackageUserInformation will show {S-1-5-18 [Unknownuser]: Staged}
2.Using powershell filtering, to get the list of all stagedpackagefullnames, you could do:
Get-Appxpackage -all |% {if($_.packageuserinformation.installstate -eq"Staged"){$_.packagefullname}} | Remove-AppxPackage
How do I get rid ofthe "Staged" packages?
1.Download psexec from sysinternals tools,written by Mark Russinovich
2.To get rid of all of them, run in a regular admin/elevatedcommand prompt (not powershell):
psexec -i -d -s powershell
Get-Appxpackage -all |% {if($_.packageuserinformation.installstate -eq"Staged"){$_.packagefullname}} | Remove-AppxPackage
