Question

I keep hitting this problem when I try to debug my Windows 8 apps and there is a copy already installed on another user account:

DEP0700 : Registration of the app failed. Another user has already installed a packaged version of this app. An unpackaged version cannot replace this. The conflicting package is {{{PackageName}}} and it was published by CN={{{Certificate Stuff}}}. (0x80073cf9)

Sometimes I can just log in or ask someone else to log in to the machine and uninstall the app. Alternatively I can change the application name/id, but one is not always possible and the other is risky (I don’t want to check in the changed application id to source control).

There must be some way to uninstall it. Maybe a PowerShell script?

Answer 1

My process above still works, but it simply gets around a race condition issue, where Windows Update (yes, oddly enough) is in charge of wiping out “staged packages.”

According to Microsoft, the “other fix” – and I still consider this issue to be a bug – is:

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 store to
update the apps, the update process is as quick as possible. WU will
eventually clean up the staged packages that were never installed.

What are some consequences of having “Staged” packages?

1. Staged packages prevent you from installing that particular package in development mode

2. Staged packages eat up some disk space, but due to hardlinking, the effect of this is mitigated. If a file is identical between multiple
   versions of a package, appx deployment hardlinks the files instead 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 staged package, the
PackageUserInformation will show {S-1-5-18 [Unknown user]: Staged}
2. Using powershell filtering, to get the list of all staged packagefullnames, you could do:

get-appxpackage -all |% {if ($_.packageuserinformation.installstate -eq "Staged"){$_.packagefullname}}

How do I get rid of the “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/elevated command prompt (not powershell):

psexec -s powershell -c "get-appxpackage | remove-appxpackage"