Most ArcGIS Pro updates are quiet. You click update, and maps still open the next day. Pro 3.7 is different. It changes the runtime it needs, the licenses it accepts, and the databases it talks to.
If your IT team patches GIS machines, this post is your checklist. It lists each change, who it hits, and what to do. You can read it in ten minutes and hand it to the person who runs the update.
Why does this update matter now?
There is a date behind it. Microsoft ends support for .NET 8 on November 10, 2026. .NET is the Microsoft software layer that ArcGIS Pro runs on. After that date, .NET 8 gets no more security fixes.
ArcGIS Pro 3.3 through 3.6 run on .NET 8. Pro 3.7 moves to .NET 10, which Microsoft supports until November 14, 2028. So machines that stay on Pro 3.6 keep a runtime that has stopped getting fixes. That is a real reason to plan the move now, not next year.
What does ArcGIS Pro 3.7 need to install?
Here are the main system requirements from Esri, in plain words:
- Windows: Windows 11, or Windows Server 2019, 2022 or 2025. All are 64-bit. Windows 10 is not on the list.
- .NET 10 Desktop Runtime: version 10.0.0 or a later 10.x patch, using the x64 installer. .NET 11 does not count.
- WebView2 Runtime: version 132 or later. WebView2 is the small browser engine that Pro uses inside its windows.
- Memory: 8 GB at minimum. Esri recommends 32 GB.
- Disk: at least 32 GB free. An SSD, or solid-state drive, is recommended.
Esri also offers a free app that scans a machine and reports if it can run Pro. Run it on your oldest GIS machine first.
One piece of good news: you can install .NET 10 on a machine that already has .NET 8. You do not need to remove the old one first. Esri also says you do not have to wait for the upgrade day. IT can push .NET 10 to the machines ahead of time.
Will my licenses still work?
This is the change most likely to stop work. Starting with Pro 3.7, Concurrent Use licenses are no longer supported. A Concurrent Use license is a shared pool of seats. A license server hands seats out to whoever opens Pro.
Esri's notice is blunt. If you update Pro without changing your license type, the new version will not open. Your existing Concurrent Use licenses still work for versions released before March 1, 2026. That means Pro 3.6 and earlier.
Pro 3.7 accepts two license types:
- Named User: each person signs in with an ArcGIS Online or ArcGIS Enterprise account.
- Single Use: a license tied to one machine. Esri says new Single Use licenses must be obtained for 3.7.
Also, ArcGIS License Manager was deprecated on July 1, 2025. Esri plans updates for it into 2028, for Pro 3.6 and earlier. So check your license type before you touch a single machine.
Which changes affect which team?
The table below sums up the changes from Esri's 3.7 release notes. Use it to send each item to the right person.
| Change in Pro 3.7 | Who it affects | What to do |
|---|---|---|
| .NET 10 Desktop Runtime required | Every Pro machine | Push .NET 10 (x64) before you install Pro 3.7 |
| Concurrent Use licenses not supported | Offices that use a license server | Move to Named User or new Single Use licenses first |
| Last release to support PostgreSQL 14 | Teams with an enterprise geodatabase on PostgreSQL 14 | Plan a move to a newer PostgreSQL version |
| Oracle user-schema geodatabases not supported | Teams on older Oracle setups | Move the data out before you upgrade |
| Utility Network Version 3 not supported | Utilities on an older utility network | Run the Upgrade Dataset tool |
| Reviewer workspace tools deprecated | Data quality staff | Move to attribute rules |
| Built-in help viewer replaced | Staff who use offline help | Install the ArcGIS Documentation Center |
| VBScript on its way out of Windows | Teams that still use VBScript | Plan to replace VBScript code now |
Not every row will apply to you. Most small offices only need the first two. But the database rows can hurt the most if you miss them.
What about our database and add-ins?
Start with the database. Pro 3.7 is the last ArcGIS release that supports PostgreSQL 14. PostgreSQL is a free database many GIS teams use to store shared data. Pro 3.7 still connects to it. The next release may not. Put a database upgrade on the plan now, while there is time.
Next, ask about add-ins. An add-in is a custom button or tool built for Pro. Esri says add-ins built for Pro 3.0 through 3.6 run on 3.7 without being rebuilt. That is good news for most teams.
There is one catch for developers. Add-ins that use copy-paste or drag-and-drop may need code changes under .NET 10. If your team owns custom tools, have the developer test them on a 3.7 machine first.
Finally, check your server. Esri pairs Pro 3.7 with ArcGIS Enterprise 12.1. Older pairs still work for most tasks. Esri suggests staying within two companion versions.
How should IT roll out ArcGIS Pro 3.7?
Do not update every machine on the same morning. Use a short, staged plan:
- Check licenses. Confirm each user is on Named User or Single Use. Fix this first.
- Scan the machines. Run Esri's checker. Note any machine on Windows 10 or with too little memory.
- Push the runtimes. Install .NET 10 and WebView2 ahead of time, through your normal patch tool.
- Pilot on one machine. Install Pro 3.7 for one power user. Have them open real projects, edit data and run their usual tools.
- Test the add-ins and scripts. Try every custom tool on the pilot machine.
- Roll out in groups. Move the rest of the team in small batches, and keep notes on any issue.
The pilot step matters most. It turns a surprise on a deadline day into a small fix on a calm day.
How do we handle upgrades at GeoLink?
We do this work as part of our GIS Managed Service. Its price is From $2,000/month. It includes up to 20 hours of GIS work every month. It also covers managed cloud operations on AWS: monitoring, backups, patching.
For an upgrade like Pro 3.7, we follow the plan above. We check licenses, test on one machine, and only then roll out. Esri and AWS licenses stay on your own accounts. You keep full control of them.
You can see what the service covers on our services page.
What should you do this week?
Write down three things. Which license type does each GIS user have? Which Windows version runs on each GIS machine? Which version of PostgreSQL holds your shared data?
With those answers, the rest of the plan is simple. If you want a second pair of eyes, a free 30-minute audit can review your list. We will tell you plainly what to fix first, or that you are ready to go.