Не удалось активировать приложение из магазина windows

UWP program that used to work fine does not want to start. When starting the app from Visual Studio 2017 the error message is:

Unable to activate Windows Store app ‘{guid-name}’. The activation request failed with error ‘Access is denied’.

Windows Event Viewer displays the following error:

Activation for {guid-name} failed. Error code: Access is denied.. Activation phase: COM ActivateExtension

The app deploys successfully, but then trying to start it (with or without debugging) it fails. When trying to start from Start menu, nothing happens when I click the app icon, but when trying to start from Visual Studio it produces an error message box. How to find out what is actually wrong?

I have tried the following:

• Rebooting computer
• Clean solution
• Uninstall the deployed app
• Delete bin folder
• Compile with .NET Native toolchain
• The solution is on C: drive
• Change package name
• Change to release profile and back to debug

When I try to create a new UWP app, it works fine, so this is most likely solution-specific error, not something wrong in the computer itself.

asked May 16, 2018 at 11:14

Usually this happens when there is an App with the same GUID as the one you are trying to Install/Debug. I would try to find the existing App, uninstall it, and try to deploy/debug again.

answered Apr 19, 2019 at 9:15

I had a similar error message to this, but my error was that a Nuget package had a different package version to my App.

• «App» had dependency «B» version .14
• Dependency «A» had dependency «B» version .13

i don’t think this will solve this particular issue but it solved mine and i couldn’t find solution to this anywhere.

answered Jan 16, 2020 at 11:54

Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д.

В сообществах можно задавать вопросы и отвечать на них, отправлять отзывы и консультироваться с экспертами разных профилей.

Найдите решения распространенных проблем или получите помощь от агента поддержки.

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.

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.

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!

answered May 19, 2016 at 18:27

Ensure that ALL APPLICATION PACKAGES has «read» permissions on C:\Windows.

My organization’s group policy likes to strip all permissions from C:\Windows, including the ALL APPLICATION PACKAGES group . By adding it back in and setting Read & execute, List folder contents, and Read, I’m able to run the app from Visual Studio without any problems.

See What to do if your Windows 8 Modern App fails to start for more tips, including this one.

answered Nov 2, 2014 at 23:33

I had the same problem in Visual Studio 2015 Update 3, Windows 10 Build 10586.494.

The error came up when trying to start any UWP app that I compiled without .NET Native Toolchain. With Native Toolchain enabled, the apps would start.

Installing a new (blank) app manually fixed the error for me:

• Start VS 2015
• File > New > Project.
• Blank App (Universal Windows) Visual C#. OK.
• Make sure to be in Debug config
• Right click on Project > Store > Create App Packages
• No. Next.
• Select Debug for all architectures.
• Create
• When packaging is finished, open Explorer to the project path / AppPackages / […]_Debug_Test
• Right-click on Add-AppDevPackage.ps1 > Run with PowerShell
• Follow the instructions
• Start the installed app from Start Menu

answered Sep 1, 2016 at 12:11

answered Nov 10, 2013 at 8:25

answered Jan 27, 2014 at 10:34

answered Dec 18, 2014 at 11:26

answered Dec 30, 2014 at 14:25

answered Aug 21, 2016 at 15:44

answered Feb 18, 2016 at 11:14

answered Jan 2, 2018 at 7:26

I had the same problem on a UWP app when creating a package for Testing, but not when runing directly from Visual Studio 2017.

The solution was to select only the architecture that I am using to Debug the App, Instead of all options (x86, x64, ARM).

Here is the option choosed on Visual Studio

answered Jul 24, 2018 at 21:06

There are can be a couple of things that might be causing this problem.
Here are the trouble shooting steps that helped me out:

Step 1 : Check to see if running visual studio in the elevated mode (Run as an Administrator) helped solve the problem. (Sometimes, your folder permissions might get mangled due to various softwares that you might have install)

Step 2 : Delete all the bin and obj folders in your project and rebuild the projects in your solution manually.

Step 3 : Do a quick check of your System Type (x64 or x86 etc) and see if your project is targeted for the same.

Here is how to do know your system type: Win + R > cmd > systeminfo

If it says x64, then make sure to select the Solution Platforms (In visual studios top action bar) as x64 or so forth depending on your architecture.

Thats all I did to solve my problem.

answered Jan 24, 2019 at 9:43

I had unticked an option while trying to get debugging working prior to this error, the fix for me was to re-check the «Compile with .NET Native tool chain»

answered Oct 30, 2020 at 10:18

A rather niche situation and solution…

I was remote debugging a UWP app for a while successfully. After some reworking, I ran into this issue. In the main app project I had set the windows version compatibility accordingly (I am running the app on a Windows 10 IoT Enterprise 2019 device) but had forgotten to match those windows target and minimum versions for the Library Project that was in my solution.

After cleaning and re-deploying the solution (first uninstalling the app from the remote device), the problem went away.

answered Feb 4, 2021 at 21:14