I have recently upgraded to Windows 10 and now opening ArcGIS (10.4) takes over a minute (1:36 last test) to load. I have tried all of the usual tricks (delete normal, uninstall all add-ins, etc) with no luck.
Has anyone else had this problem?
Edit: Windows 10 installation was an upgrade from Windows 7 on a 64bit machine. Windows was 'reset' after installation and all applications were removed. ArcGIS 10.4, ArcEngine 10.4, & Background Geoprocessing were installed after the Windows reset.
Running i5-3470 4/core, 8GB, 120GB SSD
Thanks!
Michael,
Have you tried performing a REPAIR install to ArcGIS?
Also, please describe the Windows 10 installation. 32-bit or 64-bit, and if it was an "upgrade" migrating existing applications or a bare metal install and follow-on installation of applications?
what is your hardware configuration? I would consider these minimum, not recommended
ArcGIS 10.4 for Desktop system requirements—ArcGIS Help | ArcGIS for Desktop
I have tried a repair with no luck. I notice that the splash screen appears to hang on the 'Initializing License' message so I thought to change the license server machine name to its IP address...the ArcGIS Administrator took almost 2 minutes to open. (the IP address change didn't help either)
So this isnt a standalone installation
Windows was a 'reset' upgrade from Windows 7 - 64bit
Michael, I was querying the reference to ''license server'... which suggests that is the root of the issue. I use standalone installations and have never experienced no issues due to operating system upgrades. Perhaps Stuart has suggestions directed towards specifically.
Ahh...right...we use concurrent licensing. For what it's worth I was able to activate a single-use license for this machine with the same results.
Michael,
On Windows 10, I get a fully enabled ArcMap session in about 20 seconds from launch.
It may not be the issue for you, especially as you have checked a stand alone seat, but is there a firewall running on the license server? And, what port is the ArcGIS license pool responding at? I set mine up to still use TCP port 27004 for the odd 9.3.1 box still in service--but I always poke a hole in the license server firewall for 27000-27009. And on the clients I specify the server to be at 27004@FQDN (though by IP saves a DNS lookup).
Without the open range to the FNP service default 27000-27009 range, there can be considerable latency while the FNP clients ping the server for service--but have to wait for time-out to expire when firewall blocks.
If you can arrange with your sysadmin to kill the firewall on the license pool server you can get a feel for if firewall induced latency is the issue.
Stuart