Select to view content in your preferred language

Problem with drawing order in Contents Pane Arcgis Pro

1592
20
02-05-2025 10:28 PM
AllanDegreef
Emerging Contributor

Hi, I am experiencing troubles with ordering my different feature layers in the Contents Pane. 
It should be straightforward but I always get the red icon. 
I have selected the Drawing Order modality of course. 


Any help would be greatly appreciated, thanks!

20 Replies
Woosh_AP
Occasional Contributor

It appears so, yes.

Woosh_AP_0-1738939260206.png

 

0 Kudos
MichaelGrossman
Esri Contributor

@Woosh_AP

Were you upgrading to 3.4.2 from 3.4.0? Or was it from 3.3 or earlier? We are trying to figure out if this started happening at 3.4.2 or if it was there in 3.4.0 as well. Thank you for any information you can provide.

 

0 Kudos
Woosh_AP
Occasional Contributor

I was upgrading from 3.4.0, so it could potentially be an issue with the patch update.

0 Kudos
ShaneTMF
New Contributor

For me this was upgrading to 3.4.2. I am also experiencing the same issue. Any fixes yet? Thanks!

NellyRubio
New Contributor

I too am having this issue. I was running on a older version 3.1 and it had that issue and just updated to 3.4 a couple days ago and it worked fine for a day and now it’s still not letting me rearrange my layers. I have uninstalled and reinstalled and no improvement. 

YingboDong
Emerging Contributor

Hi .. I think I met the same problem with you. did you solve it?

0 Kudos
kterry1983
Emerging Contributor

I am having the same issue.

0 Kudos
alisterfx
New Contributor

I am having the same issue, also. For reference, I was on 3.4.0 when I noticed this issue. From this esri community message it seems that the issue is actually caused by the Windows 11 update: KB5050094. However, I have not been able to uninstall it from my system to see if this actually does resolve the issue, as others on the linked thread noted as well. But, I was able to find a workaround that AlexKweya noted in the same thread with a link to this BLOG that describes Adobe Premiere customers facing the similar bug in that software suite. The workaround presented in the blog worked for me, although it's definitely a temporary fix:  

"...Since Microsoft hasn’t acknowledged the problem yet, the most straightforward workaround is to uninstall the Windows 11 update by following these steps:

  1. Settings > Windows Update > Update history > Uninstall updates.
  2. Find KB5050094 and Uninstall it.
  3. Reboot your PC.

Once done, Premiere Pro should go back to normal behavior, but make sure you do not accidentally install the update again. You don’t need to pause Windows Update because it’s an optional update and it will not install unless you select it manually.

If you don’t want to remove the update because it fixes some of the most annoying issues of Windows 11 24H2, such as the DAC audio issue, you can keep Premiere Pro on one monitor and disconnect or power off the secondary monitor.

Of course, you may not want to stop using your second monitor, but that’s one of the workarounds that seems to work for many users. You can also make sure that all screens use the same display scaling (e.g., all at 100%).

If the scaling of one monitor is 100% and another is set at 150%, change one of the settings and make sure they have the same scaling."

Hopefully this will help others workaround this issue until a real fix is implemented. 

OAP_SDSCJ
New Contributor

Thank you very much for your suggestions. They helped me resolve (at least temporarily) the problem.

The only solution I found was to set both screens to 100% scaling, since that specific update cannot be uninstalled (it does not appear on the list of updates to uninstall).

I hope this issue gets addressed soon, as I lost one screen: I cannot see anything at this 100% scale.

 

0 Kudos
Woosh_AP
Occasional Contributor

UPDATE: I noticed that if I changed both my laptop screen and my second monitor to 100% scaling. Closed settings, and then reverted the laptop screen to 200%, that the problem with dragging layers now seems to be resolved. Hopefully this isn't temporary and this fix works for others.