Hello, that process usually completes in under 10 seconds on the first start up of a new installation of ArcGIS Pro. At this point you will need to kill the process unfortunately.
In your user profile's Esri Local Caches folder (C:\Users\<user>\AppData\Local\ESRI\Local Caches) you'll likely see a series of g0 and g1 cache files. These are what is generated when the geoprocessing cache is created as you pictured. You might have several of these files if you've used previous versions of ArcGIS Pro. The Pro 2.8 cache files are ~105KB for the g0 file and ~745KB for the g1 file on my machine.
Find the g0/g1 files with a timestamp of today, remove them from the cache directory onto your desktop, make a zip, and upload here please. You can delete all of the g0/g1 files from the cache directory and restart Pro. Try opening the geoprocessing pane to see if cache completion is successful.
We have seen caching fail previously when there is corrupt or out of date Python environment active on your system, perhaps from a previous installed version of Pro.
Let me understand your possible steps based on your screenshot.
Thanks for the reply...
Here is a slightly refined set of steps..
I followed your suggestion
Thanks in advance!
I am checking with our developer on the missing g1 cache file. The hang is not allowing that necessary file to be generated.
The other cache files you showed are unrelated, and have to do with map layer caching. Raster is a complex system with many dependencies, including the whole geoprocessing system, which is why geoprocessing caching is triggered simply from basic use and saving of a project with raster data.
The only troubleshooting I can offer at this time is to please check to make sure the default Python environment is activated. Using a 2.6 Python environment in 2.8 is not supported and will cause issues such as this. And if all else fails, do a complete application uninstall, make sure the installation directory is completely empty, and reinstall.
Oh and you can try to use these complete 2.8 cache files attached in your Local Cache directory. I am completely uncertain if this will help anything or if they will register since they are uniquely guid-ed, but it might be worth a shot to get up and running (or it might make geoprocessing crash later during app usage).
Something in your installation folder or Python environment is causing the cache to generate incompletely, so I would try the troubleshooting I previously described before I would try using my g* cache files.