none
[UWP] Unable to activate Windows Stoe app, the app didn't start - Windows 10 Universal Apps

    Question

  • When I try to launch a project, it gives this error:

    What can be the problem here? This only happens on universal apps. Classic Desktop projects opens without problems.

    Things I already did, some of which are based on solutions I came across while trying to solve this:

    • Install Visual Studio 2015 Update 1
    • Check for App.config (supposedly, I should delete this; there no such file so I can't really delete it)
    • Build > Clean Solution, Build > Rebuild Solution
    • Uninstall the output app on the start menu
    • Delete `bin` and `obj` folders
    • Change the `Package name` in the Package.appxmanifest file
    • Change the output from `x86` to `x64` and vice versa
    • Change the `Debugger type` in Properties to `Native Only`
    • Tried running as `Release` failed, then reverted it back to `Debug`, still failed
    • Tried renewing my developer license. It doesn't work for Windows 10 Universal Apps and is only for Windows 8 Apps.
    • Tried uninstalling Visual Studio 2015 completely and re-installing. Still nothing.
    • NEW: Tried doing a full fresh reformat of Windows 10 still didn't work.

    So yeah, I've pretty much exhausted every solution I can find on the internet to try and fix this. If anyone can offer more solutions, I'd be glad to test it out.






    Monday, December 14, 2015 10:08 AM

Answers

  • Hello ShedoSurashu,

    I am not able to reproduce the issue on my side and I would recommend opening a support ticket for this.

    1.) Go to http://aka.ms/storesupport (sign in using your MSDN Subscription if applicable)

    2.) Under "App development" click the “Windows 10 Universal app development” OR "Windows 8.x app development” link based on where they are experiencing the problem.

    3.) On the next page, choose Problem type = Support for Writing apps, Category = <<appropriate category>>

    4.) Then choose the "Start request" link to start a support request.

    Support incident charges will be refunded if they are caused by a Microsoft bug.

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Sorry for not getting back to this thread sooner. I even went as far as to do a fresh install of Windows 10 but when the problem still persists, I was about to give up. But I found out another solution that I haven't tried: move the project folder to the C: drive.

    Apparently, when I have the project folder on my D: drive, it wouldn't work and will show me the said error. Moving it to drive C: fixed the issue. That is such a stupid limitation and I don't know why Microsoft thought that was a good idea to implement. Just to be clear, the issue only happens with Universal Windows Apps projects. If I start a regular classic C# project and place the source into a different drive, the problems don't occur when compiling/running them.

    • Marked as answer by ShedoSurashu Friday, January 22, 2016 2:08 PM
    Friday, January 22, 2016 2:08 PM

All replies

  • Hi ShedoSurashu,

    You can try to start app as a release build, and then go back to debug build. Maybe that can be helpful...

    Best regards!
    Monday, December 14, 2015 1:51 PM
  • Hi ShedoSurashu,

    You can try to start app as a release build, and then go back to debug build. Maybe that can be helpful...

    Best regards!
    I just tried that, same thing.
    Monday, December 14, 2015 5:36 PM
  • Does it deploy to a phone or the emulator?
    Monday, December 14, 2015 7:23 PM
  • Does it deploy to a phone or the emulator?

    I don't have either, but I am making a desktop application, not a mobile one.
    Monday, December 14, 2015 10:59 PM
  • Hello ShedoSurashu,

    Please see this similar issue: http://stackoverflow.com/questions/13404315/unable-to-activate-windows-store-app

    1. Try deleting the build directories and then clean solution and then rebuilt the project. (Seems you already tried! but do this again and then follow below)

    2. It seems it mentioned to renew the developer license. Did you try that?  

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Wednesday, December 16, 2015 6:42 AM
  • Hello ShedoSurashu,

    Please see this similar issue: http://stackoverflow.com/questions/13404315/unable-to-activate-windows-store-app

    1. Try deleting the build directories and then clean solution and then rebuilt the project. (Seems you already tried! but do this again and then follow below)

    2. It seems it mentioned to renew the developer license. Did you try that?  

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Renewing the developer license doesn't seem to be a thing for Windows 10 Universal Apps.

    I'll add that to my list above.

    Saturday, December 19, 2015 8:06 AM
  • Hello ShedoSurashu,

    Could you provide me a minimum sample demo in which this issue is reproducible? I will take a look on my side.

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Wednesday, December 23, 2015 3:04 AM
  • Hello ShedoSurashu,

    Could you provide me a minimum sample demo in which this issue is reproducible? I will take a look on my side.

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Hi, this is about as bare bones as it can get. Launching this gives me the above error.

    https://app.box.com/s/uraes6sgo40bcdhroxhiohcbofhb2unv

    Sunday, December 27, 2015 5:21 AM
  • Hello ShedoSurashu,

    I tested this on my side and it works fine. I suspect that it is environment issue. Try Repair / Reinstall Visual Studio.

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    • Proposed as answer by Krunal Parekh Wednesday, January 06, 2016 8:06 AM
    • Unproposed as answer by ShedoSurashu Thursday, January 07, 2016 8:12 AM
    Thursday, December 31, 2015 2:47 AM
  • Hello ShedoSurashu,

    I tested this on my side and it works fine. I suspect that it is environment issue. Try Repair / Reinstall Visual Studio.

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Hi, I just finished uninstalling Visual Studio 2015 and reinstalling. The problem is still here.

    Thursday, January 07, 2016 8:11 AM
  • Hello ShedoSurashu,

    I am not able to reproduce the issue on my side and I would recommend opening a support ticket for this.

    1.) Go to http://aka.ms/storesupport (sign in using your MSDN Subscription if applicable)

    2.) Under "App development" click the “Windows 10 Universal app development” OR "Windows 8.x app development” link based on where they are experiencing the problem.

    3.) On the next page, choose Problem type = Support for Writing apps, Category = <<appropriate category>>

    4.) Then choose the "Start request" link to start a support request.

    Support incident charges will be refunded if they are caused by a Microsoft bug.

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Monday, January 11, 2016 1:40 AM
  • Hello ShedoSurashu,

    I am not able to reproduce the issue on my side and I would recommend opening a support ticket for this.

    1.) Go to http://aka.ms/storesupport (sign in using your MSDN Subscription if applicable)

    2.) Under "App development" click the “Windows 10 Universal app development” OR "Windows 8.x app development” link based on where they are experiencing the problem.

    3.) On the next page, choose Problem type = Support for Writing apps, Category = <<appropriate category>>

    4.) Then choose the "Start request" link to start a support request.

    Support incident charges will be refunded if they are caused by a Microsoft bug.

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Sorry for not getting back to this thread sooner. I even went as far as to do a fresh install of Windows 10 but when the problem still persists, I was about to give up. But I found out another solution that I haven't tried: move the project folder to the C: drive.

    Apparently, when I have the project folder on my D: drive, it wouldn't work and will show me the said error. Moving it to drive C: fixed the issue. That is such a stupid limitation and I don't know why Microsoft thought that was a good idea to implement. Just to be clear, the issue only happens with Universal Windows Apps projects. If I start a regular classic C# project and place the source into a different drive, the problems don't occur when compiling/running them.

    • Marked as answer by ShedoSurashu Friday, January 22, 2016 2:08 PM
    Friday, January 22, 2016 2:08 PM
  • Hello ShedoSurashu,

    I am not able to reproduce the issue on my side and I would recommend opening a support ticket for this.

    1.) Go to http://aka.ms/storesupport (sign in using your MSDN Subscription if applicable)

    2.) Under "App development" click the “Windows 10 Universal app development” OR "Windows 8.x app development” link based on where they are experiencing the problem.

    3.) On the next page, choose Problem type = Support for Writing apps, Category = <<appropriate category>>

    4.) Then choose the "Start request" link to start a support request.

    Support incident charges will be refunded if they are caused by a Microsoft bug.

    With Regards,

    Krunal Parekh


    Thanks MSDN Community Support Please remember to Mark as Answer the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

    Sorry for not getting back to this thread sooner. I even went as far as to do a fresh install of Windows 10 but when the problem still persists, I was about to give up. But I found out another solution that I haven't tried: move the project folder to the C: drive.

    Apparently, when I have the project folder on my D: drive, it wouldn't work and will show me the said error. Moving it to drive C: fixed the issue. That is such a stupid limitation and I don't know why Microsoft thought that was a good idea to implement. Just to be clear, the issue only happens with Universal Windows Apps projects. If I start a regular classic C# project and place the source into a different drive, the problems don't occur when compiling/running them.

    Bingo! This is the problem.

    I've been going round in circles for ages and seen a lot of posts with a similar problem, all suggesting everything you've tried with nothing working.

    I've tried the same, move the project to C drive... works perfectly.

    This is a big issue as many people are now moving to SSD drives as their OS and application drive but do their work on another drive, often a regular hard drive. Many corporates set up like this now. The SSD is often small and data drive large, plus you don't really want to be doing builds on the SSD where it will do frequent writes.

    Is this a restriction with Universal Apps to only work on C drive? (and yet you can change apps to another drive on Windows 10, and I have done just that. Could that be an issue too?).

    Having to locate the project folder on C is limiting. If at least a project could local deploy to C but the development folder is kept wherever you like, that would be fine.

    Saturday, March 05, 2016 3:11 PM
  • This is also happening to me. I have tried ProcMon and other troubleshooting tools to see if the problem was with some path that gets broken when the project lives in another drive, but I couldn't find anything.

    At least Microsoft should document this in any of the UWA creation tutorials.


    Álvar García del Río - SharePoint Solutions Architect

    Thursday, March 31, 2016 4:42 PM
  • Hello,

    Thanks for sharing your experience. I know I'm nearly a year late to the party but I still cannot figure out what kind of testing has been done in Redmond (or Hyderabad) for this issue to persist. I too have spent fruitless time harboring hope that some basic "checks and balances" may exist to warn the poor developer.

    To cut to the chase, Hello World UWP works fine on the D: drive for me. But when I start merging the UWP with OpenCV or other open source libraries (using the D: drive), I run into the identical issue first reported here:

    "Unable to activate Windows Store app"

    "The app didn't start"

    No error events in the log folders at Application and Services Log\Microsoft\Windows\Apps

    I have installed and reinstalled VS Studio Enterprise 2015 many times on this box with all latest updates and hot-fixes for VS and Windows but successful test of a Hello OpenCV exercise eludes me.

    I suspect that changing the default profile for the basic user (not Administrator) from C: to D: triggered the cascade of issues (e.g. File History does not work for this basic user but works for the Administrator since File History is still looking at C: drive for some info and I have no way to change the environment variable that drives this lookup by File History).

    Lesson learnt. Do not use D: drive for Visual Studio projects even if these worked previously. (In fact I can no longer change the installation drive for VS 2015 unlike previous versions).

    Sorry for long rant but your observations echo my predicament. I can confirm that there is an issue with UWP apps on other drives if the support end-user libraries are spread across. No Build error messages yet the run-time failures persist.

    Regards.

    Friday, February 03, 2017 2:08 PM