Pro 3.7 can't see the GPU on our VMs

Question

I updated .NET and Pro (to 10 and 3.7) over the weekend on our three multi-session Azure VMs. Today, when we open Pro, we get a message that Pro can't detect a GPU so it's using the CPU for rendering. The Tesla T4 GPU looks fine in the device manager and in the NVidia Control Panel.

Anyone else experiencing this? Are there any guidelines for ensuring Pro 3.7 is able to access the GPU?

Ayan Palit · Answer

Thanks for checking with the Pro readiness tool -  this is puzzling for sure. Guessing there is an underlying issue with the virtualization platform and needs review by the IT infrastructure admins.

Reference documentation:  ArcGIS Pro On-premises virtualization

HollyTorpey_LSA · Answer

Hi @AyanPalit, thanks for the response. I ran that tool yesterday and it is not seeing the GPU either. It says we have no dedicated video RAM, and also no Shader Model Version (I'm not sure what that is).

The strange thing is that I was able to use the GPU as recently as last week to classify pixels using deep learning, but after updating, Pro can't see it anymore on any of our VMs.

Note that I've had an issue for a while where the GPU is showing in the device manager and Pro was able to access it (at least until yesterday), but it is not visible in the VM's task manager.

On one of the VMs yesterday, I downloaded and installed the newest versions of the NVidia driver for a Tesla T4 GPU (596.36), CUDA 13.2, and Visual Studio 2026, but to no avail. I also tried CUDA 13.0 and the corresponding driver. No luck.

The results of the Pro readiness tool are the same on the VM where I updated the driver and CUDA and on another VM where I have not made any recent updates to the GPU or related software.

I'm at a loss as to what to do next. Any suggestions are appreciated.

Ayan Palit · Answer

@HollyTorpey_LSA Suggest using  the tool Verify that your computer can run ArcGIS Pro

This produces a report that will check for GPU as well; will be interesting to see the correlation.