Lag when selecting Layer drop down

[STFD-Dave]

Does anyone know why ACA lags when clicking on the Layer drop-down on the ribbon?  It doesn't seem to matter when I do it. Any time I click on the Layer drop-down, whether an object is selected first or not, I get a random lag time before the drop-down appears.  Sometimes it is 10 seconds or more, other times it is only 3-4 seconds, but it NEVER just opens immediately and shows the drop-down.  If I try to do anything else, the cursor freezes and I get the "Program is not responding" box. A little bit later, it unfreezes and I can work again.  This is extremely frustrating and a huge time-consuming issue.  Any thoughts or ideas would be appreciated.  I am using ACA 2020.

[pendean]

Is ACA2020 fuly updates? That's a requierment, if you don't know, start ABOUT command and tell us what it says.

Does this happen in ALL files? or just one?
Where do you store your files? ow is our computer connected to there?
PC specs?
WindowsOS version?

[STFD-Dave]

Yes, it happens with all files. Makes no difference.

Yes, ACA is up to date. Product version: 8.2.70.0 AutoCAD Architecture
2020.0.2

Files are stored on server, but like I said, it makes no difference...this
happens all the time.

I'm using Windows 10 Pro
Intel Xeon CPU E5-1650 0 @ 3.2 GHz with 32 GB Ram
64-bit OS, x64-based processor

[pendean]

Do you by chance have the default SAVE format set to something lower than 2018DWG?

Did you use the migration tool to move content from an older version into 2020?

Does changing hardware acceleration in GRAPHICSCONFIG command make a difference?

[STFD-Dave]

Hi, Pendean,

I did actually have the default set to 2013 but even when I changed it to
2018 it didn't affect the lag.

I don't know if the migration tool was used. One of the guys in our office
did the migration. I've asked him about the lag and he doesn't know.

I turned off the hardware acceleration and it did shorten the lag, but it
is still there.

Thanks for the thoughts and ideas!

[pendean]

I suspect you have a removal and reinstall in your future, a fix many users report as the solution.

If it persists (not seeing here in our office) it might be something unique to your setup that I cannot replicate here.