I recently wanted to try to again update my IntelliJ IDEA because I had problems before (I still have problems hence this post). I've tried re-installing, fiddling with VM options, all what the internet says, but nothing provides any answers.
It starts when I click the .exe file of IntelliJ. It will briefly pop up in the task manager, use about 20% CPU for about 8 seconds and then disappear. It doesn't open later also. I've also tried to start it from the CLI, but that gives me this:
cli-output
I currently have IntelliJ 2019 since it's the only version that works, all the other versions I tried have the same problem. Does anyone know how I can resolve this (I'm running on Windows 10)?
I had the same issue on my windows 10. To fix it go to %USERPROFILE%\AppData\Roaming\JetBrains\IntelliJIdea2021.2\ folder and try to remove idea64.exe.jdk file, then run IntelliJ again.
P.s. I'm using JetBrains Toolbox, so all files that need to run IntelliJ will be placed into %USERPROFILE%\AppData\Roaming\JetBrains automatically after installation.
I am trying to create a UWP app (for Desktop) in Visual Studio 2017 on Windows 10. Everything works fine, I added some UI elements and I can start the app without problems.
I want to incorporate OpenCV (3.4.9) into my app, which I built using CMake and Visual Studio 2017 (following the steps from https://medium.com/#rabbi.cse.sust.bd/how-to-build-opencv-for-universal-windows-platform-uwp-1a642ec09955)
I have checked the library path for each config (I built one for each x64/Debug, x64/Release, x86/Debug, x86/Release).
The problem starts when I start using OpenCV, eg by including "opencv2/opencv.hpp".
I can still build without errors, but when I try to run the app (Run without Debugging in VS), I get the error:
Unable to activate Windows Store app. The activation request failed with the error: The app didnt start
When running the .exe directly, nothing happens (I had to add some DLLs to the folder first).
I have tried the suggestions from the similar questions here on SO, but without luck.
Rebuilding or changing configuration doesn´t help.
I can start the app when including "opencv2/core.hpp", and do
cv::Mat img;
But if I write
cv::Mat img(200, 200, CV_8UC3);
The same error occurs. Writing
cv::Point pt(10, 10);
on the other hand works fine.
I am running out of ideas for things to try..
Ok, so I found the problem. Actually similar to what others with the same issue found:
Visual Studio was unable to find the DLL files for OpenCV. I did suspect that, so I added the bin folder to my path, and copied the DLL files into the project root as well as "ProjectRoot/x64/Release/ProjectName".
But apparently, the DLL files need to be in
"ProjectRoot/x64/Release/ProjectName/AppX"
for a x64 Release build.
If someone has any idea on why it can´t find them through the PATH or in the project root, please let me know.
I guess the reason is related to the fact that the binaries are dependent on the configuration?
Anyway, I can load an image through OpenCV in my UWP app now, so I´m happy.
Hope this saves someone a headache.
I've googled pretty much but i can't seem to find any information on this..
I've cloned a project from github, it opens and builds no problem. it's also added to my start menu.
I can run the program from my start menu as if it was a "normal" program.
Now I have made some changes to the sources and built it, and the changes seem to be present in the installed version (which I start from start menu) just by themselves.
my question is: is that really the case? do UWP apps get installed and updated automatically? is there a way to NOT update my installed version with my release-build every time? it seems wrong, did I miss something? (did I maybe "install" the changes somewhere along the way without noticing/by double-clicking the executable etc.) and: can I replace the executable that is started in the start menu? I tried to find where it is stored/linked, but I couldn't find anything, as there is zero information in the start menu.
Or can I rely on the start menu version always being my latest release build?
I'm confused, if someone has any information on this, I'd be really happy. :)
You are correct whenever you build and run the app on the local machine using Visual Studio it gets deployed to the system apps from where you can run it. So each time you build and run with any changes they will be updated in the system installed app as well(Basically they are same)
If you want that these changes do not get reflected in the system's app then I think you can use Device emulators available in the Visual Studio.
While trying to deploy an app from Visual Studio, I'm getting an error. I have already set developer mode and also deleted the app package from the packages folder, but it still won't work.
Here's the error message:
Error : DEP0700 : Registration of the app failed. Deployment Register
operation with target volume C: on Package
App_1.0.0.2_x64__m0fsgersa29a0 from: (AppxManifest.xml) failed with
error 0x80070002. See http://go.microsoft.com/fwlink/?LinkId=235160
for help diagnosing app deployment issues. (0x80073cf9)
Do I need to set anything else?
I got this when attempting to debug a project from a shared folder.
Opening the project from a local folder first resolved the issue.
I know there is already an accepted answer, but I had a totally different problem with the same excact error message. When th app was running I took a look in the SQLite database with a program that I didn't close when I uninstalled the app and re-run it from Visual Studio. I think that Visual Studio couldn't overwrite the database as I was 'using' it.
Closed the program and voila the app run smoothly.
Hope this helpes anybody else as I was stuck for precious hours!
In Windows 10 there are two possible cause of this problem are as follows,
Previously installed app is locked and preventing VS to delete while deploying the application. Goto C:\Users\{you user}\AppData\Local\Packages and delete the folder of your application. Now rebuild and deploy your application.(this was the solution in Windows 8 devices as well)
If it is still not working, double check if you have removed the below entry from appxmanifest file. If you are targeting Desktop Name="Windows.Desktop" entry should be there in the file. If it is Phone, Name="Windows.Mobile" should be there in the TargetDeviceFamily. You can have both in the configuration but sometimes Microsoft will suggest to keep separate configuration when you submit the application for STARTS testing.
< Dependencies>
< TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.0.0" MaxVersionTested="10.0.0.0" />
< /Dependencies>
Hope this help in figuring out the reason and solution for "Error : DEP0700 : Registration of the app failed" error.
Don’t worry, the solution is actually very simple.
Error: DEP0700: Registration of the app failed. An internal error occurred.
So you’ve started your Windows 8 app development journey. All things are going smooth until one day you hit this error when trying to run/debug your app. The error says “Error: DEP0700: Registration of the app failed. An internal error occurred with error 0x80073D05. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. (0x80073cf6)”
This is a very cryptic error and does not give you any info about what the problem actually is. The problem is that Visual Studio is not able to delete the application data in your local packages folder.
Don’t worry, the solution is actually very simple. On your Windows 8 machine, go to C:\Users\\AppData\Local\Packages\ folder. There you will find a folder that has your application’s Package Family Name in it – you just need to delete that folder. The issue is that while your app is in development, it might have a random GUID as its Package Family Name, so the folder will also have that random GUID as its name which makes it hard to know which folder belongs to your app. Again, that is easy to find as well. Right click your project in Visual Studio and click properties. The value you see in the “Package Family Name” field is the name you should look for in the folder. Simply delete it and build your solution again and it will run like a charm.
Read more details at http://paraswadehra.blogspot.com/2012/12/error-dep0700-registration-of-app.html
For me this was caused by being signed in with my Microsoft account in windows instead of the local user account. Logging in as a local user fixed this.
DEP0700: Registration of the app failed
For me the error DEP0700: Registration of the app failed, was raised because my Store App was installed from the actual Microsoft Store. I had to uninstall it and then I could debug my app smoothly.
I got this when I tried to run the project from a ReFS filesystem. Running from NTFS worked. My error code was 0x80073cfd.
I stumbled over the same issue today and after a few hours I found out, that the problem was because I moved the AppIcon files into a subfolder and forgot to adjust the references inside my package.appxmanifest. Unfortunatly the corresponding error message didn't point into this direction and all the above mentioned solutions didn't help for me, so hopefully this helps someone else!
In my case, I was opening one of the App files (Log Files). When deploying, Visual Studio attempts to remove all the files and packages (if uninstall is on in the properties). It was unable to remove the Log file as it was opened. When I closed all files, and tried again, it worked.
I ran into this error when testing some code in domain-bound and non-domain-bound scenarios (which requires me to have a domain account and a non-domain account on the same machine).
I found that I had to uninstall the application from the account I originally deployed it from before I could deploy it again on the other account.
My problem is that there is another Microsoft account in my computer that installed the app from Microsoft Store.
Nothing from the provided solution helped.
The only thing that solved my problem is to delete that account that I installed the app there.
SQLlite database might be opened. Just close the sqllite and try to deploy again.
I installed a retail version of Windows 8 Pro. I downloaded and installed Visual Studio Express 2012. I asked for and received a developers certificate. Then I tried to create a hello world app.
From there I get a "Unable to Activate Windows Store App" message box when I try to debug the app. Most commentary on the web says delete build directories. This didn't work for me
Does anyone have a solution for how to fix this and debug my app?
This happened to me once too, but the deleting build directories advice fixed it. Specifically, you just need to delete the bin\Debug and bld\Debug folders in your projects. Their contents will be regenerated by Visual Studio when you rebuild. I assume that this is only one project since it's a Hello World app; otherwise I would ask if you deleted build directories from all projects in your solution.
You can also try running "Clean Solution" from the BUILD menu in Visual Studio.
I'm sorry...it's horrible if this is happening on a clean install as you describe.
I ran into the same issue, and tried rebuilding, cleaning, deleting temp files, rebooting the computer, etc... and nothing helped.
Then finally I made a release build then went back to debug. And now it works.
I have no idea what happened, nor if that really helped, but it's worth a try.
For me a RESTART of pc solved this error message.
For me the problem was that I created the app on a TrueCrypt mounted virtual drive and when I moved the project files to a normal drive then everything worked just fine. Weird.
I was getting the exact same error. In my case the culprit was a NuGet package. It had added an app.config file to the project and it was confusing VS. I removed the app.config file and it solved my issue.
I got the solution at Iris Classon's site.
This can be solved by Uninstalling the app from the start screen then again building the app from Visual Studio.
I had a similar problem, and the cause was creating the project on a USB thumb drive. Creating a project on a normal hard drive volume works.
this can happen when the application signing key (.pfx file) is missing.
Try the following:
Open the Package.appxmanifest file in Visual Studio
Go to the register "Packaging"
Select [Choose Certificate…]
Select the test certificate using [Configure Certificate…] [From File…], or create a new one using [Configure Certificate…] [Test Certificate…]
When using a test certificate, ensure that it is in the .gitignore file. There should be an entry like !**\*_TemporaryKey.pfx to include the key in Git.
Note: The certificate for release build should only be available to the build server and not included in Git.
Rebuild the project
This has happened to me in the past and I have always found that deleting the build directories resolves it.
However this time this is not working for me.
I have tried
- Rebooting
- Deleting build directories
- Running Build | Clean Solution in VS
- Renewing Developer Account
The only thing that will work for me is changing my Package name under the Package.appxmanifest
However I am not overly happy with this as a solution. I will keep investigating.
The issue might be caused because NuGet will try to add an app.config with binding redirects to Windows Store apps if it thinks it is needed. However, Windows Store apps don’t need app.config, and will actually fail to start with a very confusing error message if it is present.
And the solution in this case would be to Remove the App.config
This error generally comes when you try to deploy in debug mode.
I would suggest, deploy the app first in release mode and then try in debug mode.
This worked for me.
Making a new certificate works for me. For this, go to Package.manifest->Packaging, and follow the Choose certificate.... Click on Configure certificate and select Create test certificate. Give it a name and press OK.
Increasing the revision number of the package worked for me
Tried so many of the above fixes. Nothing worked (deleting bin, obj dirs, editing the manifest, editing the registry, changing package name, etc, etc.) My Avast antivirus software was running and so I uninstalled it completely. That was it. App now runs fine.
This sort of problems are common with Windows 8 Visual Studio. Such errors encounters when your developer license of Visual Studio has expired so you may want to renew or get a new developer license here's how you get that. How to get a developer license in Windows 8
And similar problem may also encounter with E_Fail issues here's how to solve Unable to activate Windows Store app E_Fail Issue
For me, the fix was a combination of two of these answers -
Renew the developer license (How to get a developer license in Windows 8)
And deleting the build directories (though I deleted more then the screenshot depicted) Delete the Build directories
NuGet will try to add an app.config with binding redirects to Windows Store apps if it thinks it is needed. However, Windows Store apps don’t need app.config, and will actually fail to start with a very confusing error message if it is present.
Solution:
Remove the App.config
and build again
For those who get a similar error but who are searching for a solution while debugging an IOT background app on a local machine specifically - you can find it here.
Using the search term "unable to activate windows store app the activation request failed with error" brought me here.
Because of Two things i resolved this issue.
Basically, we just need to delete the bin\Debug and bld\Debug folders in our projects. Those contents will be regenerated by Visual Studio when you rebuild project.
Just Restart the Visual Studio. And Clean Build and Rebuild the solution and RUN it.
Hope this helps.,
Playing with this issue for 3 days, tried every suggestions, nothing works. Until now!!!
The solution was this for me:
renew developer licence
build and deploy solution in Release mode (after this step it still not worked, but VS installed some packages in rpi)
start VS remote debugger with default account (http://:8080/#Debug%20settings)
configure remote device with Universal authentication mode (VS2017 -> Project settings -> debug -> target device: remote machine, authentication mode: Universal (unencrypted protocol))
...and now I can sleep.
Hope it helps somebody.
This gift was courtesy of Microsoft's automatic updates for VS2015 which was one of the 2 culprits:
KB3022398
KB3165756
It also broke SourceTree and other apps that draw the GUI - making an outline of the app but not drawing the contents.
For me changing the Package Name in Package.appxmanifest fixed the problem
In my case, the C# UWP app had a native library which failed in the application startup code, and called exit(1). The symptoms were identical to those in the question, though. Visual Studio would throw a message:
Unable to activate Windows Store app '88888888-6666-5555-4444-111111111111_abcdefgh!App'. The Acme.exe process started, but the activation request failed with error 'Operation not supported. Unknown error: 0x80040905'.
In addition, there was a message in the UWP app Windows log under Microsoft\Windows\Apps\Microsoft-Windows-TWinUI/Operational: event ID 5961, message:
Activation for 88888888-6666-5555-4444-111111111111_abcdefgh!App failed. Error code: Unknown HResult Error code: 0x80040905. Activation phase: COM App activation
Internally, the C# part would try to construct a native class instance from the App constructor, the native class constructor would encounter an unrecoverable error and bail. From the UWP subsystem standpoint, and from the debugger standpoint, though, this looked as something distinct from the mere programmatic exit. I'll leave this answer here, 'cause I've spent some time chasing various UWP failure scenarios instead of running under a native debugger.
I've replaced the exit() call with throw ref new Exception(E_INVALIDARG). At least this way the error manifests in the managed debugger, and the message is descriptive.
I've been having this problem a lot with a UWP Windows 10 app on Visual Studio 2019...for me the reliable workaround is to bump the Build number in the Package.appxmanifest file (Packaging tab). It's a huge pain...really hope Microsoft will sort this out soon
Any existing error in the code can also cause this issue. Make sure your previous version of the code is working fine. Compare the difference and make sure all looks good.
I was getting this error and nothing else worked so I had to dissect my program. Turns out I referenced a StaticResource in my App.xaml that didn't exist.
Seems like a silly error but you'd also think Visual Studio would pick up on something like that and throw a different error so if nothing else works, double check your application resources.
As suggested by #Iman in a comment, in the UWP project settings, enable "Compile with .NET Native tool chain".
(After trying just about every answer in this question)