Pro 2.9.2 crashing when clicking on a symbol or opening the symbology window

[PiperMcKinnon1]

Starting mid-day today all users in our organization are experiencing crashes of Pro 2.9.2 when we attempt any interaction with symbology, whether by clicking in the Contents pane or opening the Symbology pane. We have tried some fixes found in older posts and bug reports, including changing the rendering engine to OpenGL, clearing the display cache and running a repair, all to no avail. We will look into whether there have been OS or network changes next, but are wondering if anyone else is seeing this issue appear.

[WorcesterGTSS]

We are using Symantec. We have not yet tried disabling it as of yet. To my knowledge, the display drivers are up to date. 

[RicciLucas]

Hi Daniel,

I am on Pro 2.9.0 and uninstalled Windows 11 patch KB5017264. This seems to do the trick for us. We are on PCs 64x bit .NET framework version 4.8.04161and use Fortigate as our antivirus.  

We have another PC running 3.0 with all the latest Windows updates and it seems to be running fine.

We have another PC that we left with the Windows updates on Pro 2.9.1 that is still crashing. 

[Daniel_Schmidt]

We should be able to resolve this issue by updating .NET to 4.8.1

[PiperMcKinnon1]

Hi Daniel, FYI, yesterday we tested turning windows updates back on after installing .NET 4.8.1. KB5017266 has recreated the problem in our environment at Pro 2.9.2 and 2.9.3.  (September 20, 2022-KB5017266 Cumulative Update Preview for .NET Framework 3.5 and 4.8.1 for Windows 10, version 20H2, Windows 10 Version 21H1, and Windows 10 Version 21H2).

[EmilyHildebrand]

I have received this same issue this morning.  We are in 2.9.3 operating on a cloud server.

[PiperMcKinnon1 · Accepted solution]

* SEE POST https://community.esri.com/t5/arcgis-pro-documents/recent-microsoft-net-update-resulting-in-arcgis/t...  from ESRI community moderator KoryKramer for clearer guidance as of October 13, 2022. Thanks to Kory for the post.

We have resolved the issue at our organization by uninstalling Windows update KB5017262 (2022-09 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64). Uninstalling an OS patch isn't ideal, but allows us to continue working in Pro 2.9x. Here's hoping ESRI releases a fix in short order!

UPDATE - Further to this issue, we tested on a machine running 2.9.3. We left KB5017262 in place and installed the latest .NET Framework (4.8.1) and the issue resolved. Thanks Daniel_Schmidt for bringing up .NET versions as an avenue to investigate.

UPDATE (September 29, 2022) - Yesterday we tested turning windows updates back on. .NET 4.8.1. KB5017266 has recreated the problem in our environment at Pro 2.9.2 and 2.9.3.  (September 20, 2022-KB5017266 Cumulative Update Preview for .NET Framework 3.5 and 4.8.1 for Windows 10, version 20H2, Windows 10 Version 21H1, and Windows 10 Version 21H2).

UPDATE (October 3, 2022) - Our case supporter has found this report from Windows. KB5017266 and KB5017262 both have known issues. The report indicated these Windows Server Update Services (WSUS) updates are listing errors (should not have been released): https://support.microsoft.com/en-gb/topic/september-20-2022-kb5017266-cumulative-update-preview-for-...
This would affect users working in organizations where Windows updates are managed by WSUS and likely other types of update manager software.

[Daniel_Schmidt]

Hi Piper - which .NET framework do you have on your machine?

[PiperMcKinnon1]

Hi Daniel, I'm running .NET 4.8.04084. Hope that helps!

[Daniel_Schmidt]

Can you try updating to 4.8.1 and seeing if the issue reproduces?

[PiperMcKinnon1]

I can, but not today. Our IT manages the windows installs. I'll have to have them re-install the Windows KB to truly test if a .NET update alone fixes the issue. Will post when I can!