I get this error on a device I am using despite having uninstalled the app and only having used the device with one user.
My current workaround is to hack the identity to be something different, but this is not a good solution - its risky and error prone to keep going that way I feel...
I'm not sure I understand the purpose for the error? Can VS not ask for elevated privileges and uninstall the app for you? It seems naively to me that this is the only desired behaviour in this circumstance - if I press play I want my app to run in the debugger...
there are a number of questions already about this issue, but they all seem to have been resolved in ways which are not going to help me.
- Moved by Rob CaplanMicrosoft Employee, Moderator Monday, February 25, 2013 9:41 PM
All Replies
-
Sunday, December 16, 2012 3:42 AM
Raman Sharma
Raman Sharma
Microsoft
MSFT
Recent AchievementsForums Answerer II Forums Replies II New Gallery ContributorMicrosoft(MSFT)1,610 Points
0I believe this error should go away after a certain period of time.
Raman Sharma | Program Manager, Visual C++ | @rasharm_msft
(if my post has answered your question, please consider using the 'mark as answer' feature in the forums to help others) -
Monday, February 25, 2013 7:21 PM
0
I've encountered this case several times. For me, it typically occurs when I had installed my app from the Windows Store and then try to run a local build through Visual Studio. What I have noticed is that even when you uninstall the app from the Windows Store, a "staged" entry still exists in the app database that prevents Visual Studio from installing the app. Here's what I did to remove it.
1. Launch PowerShell as administrator and type: get-appxpackage -all
2. Look for the "staged" entry for your app. It should contain a line like this: PackageUserInformation : {S-1-5-18 [Unknown user]: Staged}
3. Note the PackageFullName and copy it. It should be something like ABCDEF01.YourAppName_1.0.0.0_neutral__xyz0123456789
4. Download the PSExec tool from the site: technet.microsoft.com/en-us/sysinternals/bb897553
5. Launch a Command Prompt as administrator and type: psexec -i -s -d powershell
6. In the PowerShell window that was launched, type: remove-appxpackage PackageFullName (where PackageFullName is the name you copied in step 3)
For example: remove-appxpackage ABCDEF01.YourAppName_1.0.0.0_neutral__xyz0123456789
Now you should be able to launch your app again from Visual Studio.
- Edited by CarlSobeski Monday, February 25, 2013 7:35 PM
-
Monday, February 25, 2013 9:41 PM
Rob Caplan
Rob Caplan
MSFT
Recent AchievementsForums Curator I New Gallery Rater New Blogger(MSFT)51,775 Points
0Prashant blogged about this in Registration of the app failed. Another user has already installed a packaged version of this app. An unpackaged version cannot replace this… .
He provides a bit more explanation, but essentially the same steps that Carl listed.
--Rob
-
Sunday, March 03, 2013 7:53 PM
0
I have encountered this problem before and every time it was the app installed in the machine in a user account other than the one you're logged in as.
The simple fix is simply to login as the other user, uninstall the app and log back in and debug.
-
Monday, April 22, 2013 1:26 PM
phil_ke
phil_ke
Recent AchievementsNew Blog Commentator Forums Answerer II Forums Curator I730 Points
0Oh dear, this is some serious bug in Win8! When a user has staged packages and the user is deleted, the staged packages for that user are NOT removed. Rendering the device (in my case a Surface) unusable for new installs of the package for ANY OTHER USER! Of course there is no ARM psexec to run powershell with the local system account to remove the staged packages. What can I do now, except reinstalling the system?- Edited by phil_ke Monday, April 22, 2013 1:26 PM
