Unable to activate windows store app the app didn't start

Question

First of all I would like to say that I already tried all the solutions I could find on the internet, including Unable to Activate Windows Store App

I recently upgra

Answer 1

I've tried all the solutions found on the net and none applied to my case, not even this one.

The only way I could make it work was changing the Package Name in the appxmanifest. This made me think there must be some leftovers somewhere around with the old package name, that are either corrupted or inaccessible because of some permissions issues.

It might be just a coincidence but the problem appeared twice after I tried using the app verifier (appverif.exe)

Now I reassociated my app to a store app package and things seem to continue working...

Answer 2

I found a solution. The problem was that the drive I was working on was encrypted (TrueCrypt). Moving the output folder to an unencrypted drive solved the problem.

Answer 3

If switching from x86 to x64, make sure your Project Properties Platform Target and Configuration Platform are BOTH set to X64.Hint you need to change to x64 debugging in the Build menu/Configuration Manager dialog to get the Configuration Platform in Project Properties to update.

This caused the activation error problem to be resolved for me

HTH

Robert

Answer 4

I had the same issue with a Windows Store App after moving some files around. I ended up opening an older file (as Admin) to see if it would run and found that it did. I then returned to the file that would not and it ran also. I believe opening the older file (as Admin) reset the paths for development and the permissions. Hope this helps.

Answer 5

In my solution, I have a non-UWP project (Multiplatform development) that builds with a different Solution Platform.

I was attempting to run the UWP project in Debug, but as the wrong Solution Platform.

Edit: I also get this when I build my project for Any-CPU, instead of x64.

Answer 6

I had a similar issue, solved by choosing a new publisher certificate. And of course restarting Windows