topic Re: Installing Pro 3.5 in ArcGIS Pro Questions

Installing Pro 3.5

DavidGray1 — Sat, 23 Aug 2025 22:52:20 GMT

Hi; I see that there are numerous posts regarding installing Pro 3.X. and none of them describes with any clarity a working solution. I get the same cryptic message about some .NET thing being needed. After following various unexplained prompts and chasing useless rabbit holes of acronyms and cryptic language links and spending hours in frustration, I have no upgrade installed. This is ridiculous and it used to be easy! Offhand, it looks like AI got involved to make our lives faster and seamless. Dave ESRI should provide a simple step by step set of instructions in simple real everyday language on how to do this.....at least 3,2 still works!.....So far.

Re: Installing Pro 3.5

DanPatterson — Sat, 23 Aug 2025 23:09:55 GMT

ArcGIS Pro 3.5 system requirements—ArcGIS Pro | Documentation

this section

Software requirements

install these, if you already have it, it won't be needed to install

Download .NET 8.0 (Linux, macOS, and Windows) | .NET

Microsoft Edge WebView2 | Microsoft Edge Developer

Then, depending on whether it is a single install (eg you have full control over your environment)

Download ArcGIS Pro—ArcGIS Pro | Documentation

Did you try to follow those instructions?

Re: Installing Pro 3.5

RClavero — Sun, 24 Aug 2025 10:00:12 GMT

Hello @DavidGray1, we don't know which error/warning message you are exactly seeing, but if ArcGIS Pro keeps asking for the .NET Desktop Runtime, check this article: https://support.esri.com/en-us/knowledge-base/error-arcgis-pro-requires-microsoft-net-desktop-runtime-000027925

The .NET Desktop Runtime 8.0.19 (the current last version available*) should work well and allow you to install ArcGIS Pro 3.5.

*https://dotnet.microsoft.com/en-us/download/dotnet/8.0

Re: Installing Pro 3.5

BarryNorthey — Sun, 24 Aug 2025 18:40:21 GMT

FAQ article ArcGIS Pro and .NET Life Cycle Overlap and Release Cadence might explain a bit about Microsoft .net versions and esri. Some problems attributed to esri are due to changes by Microsoft. The loss of the personal geodatabase is a case in point.

You implied that you were using Pro 3.2. Excerpt: ArcGIS Pro versions 3.0 through 3.2 require .NET 6 to run, and this requirement will not change. I recall people reporting 3.0-2 installation problems who were installing just .net 8x runtime and assuming it would work, which it did not. They had to install .net 6x. You can have more than one .net version installed but must have the correct one(s) for the version of Pro you are using.

Re: Installing Pro 3.5

DavidGray1 — Sun, 24 Aug 2025 21:22:04 GMT

Thanks Dan; As usual you are a big help. I now have 3.5 installed, but I can't use it. Installing .net 8.0 rather than 9.0 seems to have made a difference.The authorization process doesn't like my authorization number (which I obtained from my profile on myesri)and the (next) button remains grayed out and I can't get anywhere for online authorization. It's always something. I am a single commercial use license. Dave

Re: Installing Pro 3.5

DanPatterson — Sun, 24 Aug 2025 22:04:02 GMT

David

Sadly to say, if you can't get the authorization number recognized, then you will have to contact Tech Support.

Fortunately your software is now good. Pro requires a specific Net version for its release, installing one above or below doesn't cover or compensate for the requirements.

Good luck getting the authorization straightened out.

Re: Installing Pro 3.5

RichardDaniels — Mon, 25 Aug 2025 19:50:33 GMT

key here being, .NET Desktop Runtime version 8.0.19 or higher within the v8 family. Each .Net major version change is a breaking change for ArcGIS Pro.

Re: Installing Pro 3.5

DavidGray1 — Tue, 26 Aug 2025 01:45:29 GMT

Dan and all: Yep; had to get with tech Support to get it straightened out. Turns out single user Basic doesn't need the number - why couldn't they have just said so instead of unresponsive grayed out response boxes? And why did it have to remove all taskbar icons just because? But I am up and running again. call it a solution!

Dave