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 upgraded my Windows 7 machine to Windows 8.1 to be capable of developing Windows Store apps using Visual Studio 2013. When I open a blank project (Windows Store -> Blank App) and run it I get this error:

Unable to activate Windows Store app 'Package Name'. The App1.exe process started, but the activation request failed with error 'The app didn't start'.

See help for advice on troubleshooting the issue.

I already tried:

• Reinstalling Windows (Clean install)
• Reinstalling Visual Studio 2013
• Installing Visual Studio 2012 (same error)
• Deleting "bin" and "obj" folder
• Cleaning the solution
• Uninstalling the app from start menu
• Creating a new project
• Acquiring the license multiple times (the license is valid)
• Making sure that app.config doesn't exist
• Investigating the Windows Event Log which says

Activation of the app 'Package Name' for the Windows.Launch contract failed with error: The app didn't start..

but found nothing useful

• Adding a new Windows user
• Run everything as administrator
• and at last, changing the desktop background :)

None of this did bring a solution. Does anyone have an idea what else could be the reason for this error?

Thank you.

Solution 1

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.

Solution 2

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

Solution 3

I had the same Error and tried after loading the SQLite Package for WP 8.1 some things above:

not working:

• Clean and Rebuild
• Restart Computer/Phone

what did the deal (for me)

• I put Platform Target under Properties -> Build to ARM instead of x86

Hopefully this might help somebody else facing this ridiculously informative Errormessage.

Solution 4

I had the same problem with Visual Studio Community 2015 while trying to debug an Blank App (Universal Windows) using Visual C#.

Visual Studio was installed on Disk C:(SSD), and Project files were placed on D:(HDD). I´ve created a Folder on C: Drive and placed my test project there. After that Error messages gone.

Solution 5

If you are receiving this error and are developing for Microsoft Hololens:

You are trying to build to a device that is asleep. To wake your device, tap on the button on the back (on/off button).

Good luck!

View more solutions

Comments

[Admin]

I have already tried that (even a fresh install), but it didn't help. I also knew about the app.config, but there is no app.confing in my project or folder on disk.

[Niels Verhoeven]

What version of Visual Studio do you use, and is your developer license connected to your Microsoft account?

[Lessneek]

The same. What on earth it that? Why TrueCrypt influences in such way?

[Joe Brunscheon]

TrueCrypt was the source of the problem that I was experiencing as well.

[krtek]

This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post.

[Maurizio Manca]

It provides another way to solve the "unable to activate the app" by changing the Package Name in the appxmanifest.

[outbred]

This was my issue as well.

[Dave Friedel]

I found just changing the build type to another value resolved it for me (in my case x64) Thank you though!

[Roel van Westerop]

I had the same problem. Even though I don't have different physical disks, copying my project from D to C solved the problem.

[Roel van Westerop]

So, I finally found something for this on MSDN: link

[Serve Laurijssen]

No matter what the package name becomes it keeps giving the error

[Eric]

This appears to do something indeed. Changing to Debug x64 will work. Changing to Release x86 will work. Changing back to the default Debug x86 the problem remains, however.

[user3079834]

@Eric do you maybe use third party binaries (plugins, ...) that are only provided as release?

[Eric]

I don't think so. I'm using some packages (UWP Community Toolkit, Newtonsoft.Json), project references (Universal Windows and .NET Standard 1.4) and the default references+extensions from Add Reference. I should say this problem is new. The same solution didn't have this before.

[Daniel Armstrong]

I also had this issue and this was the fix! I had been trying for ages, thanks.

[DaveDev]

This is what eventually worked for me too. It's so infuriating.