We installed Pro 3.0 on Windows 10 20H2 and we're having some issues when trying to execute ArcGIS Pro. Basically, it never opens. If you go to the Task Manager, you can see the process ArcGIS Pro with 0% of CPU usage, and remains static at 0% all the time. If you go to the License Manager, it has not checked out the license. You never see the GUI, interface or any menu of Pro. No license errors, no alerts...
We tried on serveral computers with the same result. We even tried in computers that never have had previous releases of the software installed (I mean, completely clean installation). But no difference at all.
Any has had a similar problem? We appreciate any hint.
Solved! Go to Solution.
Hi there,
I write just to let everybody know that this issue is finally fixed.
Thanks to the Esri team and this post seemed a certificate problem. DigiCert Trusted Root G4 and VeriSign Universal Root must be present in the local machine's certificate store (under Trusted Root Certification Authorities) in order to launch ArcGIS PRO.
Regards,
Have you ensured you have the proper .NET framework installed? Check out the ArcGIS Pro 3.0 system requirements page for more information.
Thanks for your response, Dan. We have installed NET 6.0.4, but you specify NET 6.0.5 ( https://pro.arcgis.com/es/pro-app/latest/get-started/arcgis-pro-system-requirements.htm ) We're going to update NET to 6.0.5 and see if it makes any difference.
We also have installed Microsoft Database Access 2016
Thanks.
I can confirm that we have 6.0.5 installed but it makes no difference.
We have excluded the antivirus to scan the folders recommended in the documentation, and even for testing purpusese we temporarily shutted it down completely.
More people with the same problem: https://community.esri.com/t5/arcgis-pro-questions/arcgispro-does-not-start-after-fresh-install/td-p...
After reading that post we tried reinstalling the .NET framework again and try to repair, but it was not the solution. We tried even to update to NET 6.0.6 but no luck. Today we've been working with the support from Spain but we're really lost. We wonder whether there is a problem with Windows 20H2 but the guys of the link above report a different Windows 10 version with the same problem.
Any help would be appreciated. We need to use 3.0 due to some important enhancements in the deep learning workflows.
Hi @Daniel_Schmidt,
We've been assisting @MrG with this issue the past weeks and we finally managed to execute ArcGIS PRO but using dotnet on the command line:
dotnet "C:\Program Files\ArcGIS\Pro\bin\ArcGISPro.dll"
Still having problems trying to execute the *.exe file or ArcGIS PRO shortcut. Do you think this could be something related to customized Windows security/app policies somehow? Apparently nothing is being blocked looking at the Windows Event Log.
Thanks,
Thank for the quick response. I answer below to your questions:
To be mentioned... we perform a .NET host tracing to get some insights on this issue executing:
set COREHOST_TRACE=1
set COREHOST_TRACEFILE=logfile.log
"C:\Program Files\ArcGIS\Pro\bin\ArcGISPro.exe"
But, strangely, no output file is written.
I was doing manual installs of ArcGIS Pro, and even after updating the software and runtime, we were also receiving a bunch of weird error messages. Not the CPU issues - but it was almost like it had disconnected from the license.
After some testing, I found out that updating the ArcGIS License Manager fixed the problem! At least for us, the update also seemed to require an update for the license manager, but it didn't automatically take care of that when we did ArcGIS Pro. So the program just crashed or didn't register the license. But updating the ArcGIS License Manager app did the trick!
Not sure if this is helpful - but just wanted to share in case it helps with troubleshooting!
Thanks Sara, but in our case we had updated the License Manager to the last version before the installation. Thank you anyway.
We keep struggling with this problem after many months, even after updating to a brand new version of Windows 10... The only workaround that we found is the one pointed out by Kepa in a previous post, which is instancing the ArcGIS Pro DLL through the dotnet framework. I mean, creating a shortcut in the desktop pointing to:
"C:\Program Files\dotnet\dotnet.exe" "C:\Program Files\ArcGIS\Pro\bin\ArcGISPro.dll"
This way, we can start ArcGIS Pro fully, but Esri should give this matter some kind of solution because it's not up to standards, to say the least. We're in constant communication with our support in Spain and they are also working with us in order to provide a comprehesive solution to the problem.