Just installed 13.6.6 Copy button stays greyed out

Windows 10
Just installed 13.6.6 Copy button stays greyed out
Have rebooted
Can go into any Drive
Highlight a Folder or File and the Copy and Move button on my Drive bar stays greyed out and unclickable
See pic

Have reinstalled 13.6.4 and Copy and Move buttons works as expected

1 Like

Same here - 13.6.6 does often not "see" that files are selected and commands are greyed out. By repeatedly switching between Source and Destination and selecting/deselecting stuff I can get it to work, but only until I switch directories, then I need to start all over again. Copy, Move, Rename, Delete, Archive and Properties are affected.

Edit: As a workaround I've found that if you add the @disablenosel modifier to the script, it does activate the buttons when things are selected. However there is a slight delay, but I'm not sure if that's normal because I haven't used the @disablenosel modifier on any of my main toolbars before this version.


I also just noticed this strange behavior, except it happens with a couple of my menu buttons.

Screen recording below. Specifically the problem appears with these menu buttons I have:
image
image

Annotations:
0:00 - My custom 'Extract' menu button and 'Properties' menu button are disabled when they should be active
0:06 - Entering & exiting customize mode without anything selected makes no difference
0:12 - Entering & exiting customize mode with an item selected turns the buttons active as expected
0:15 - Testing the buttons
0:22 - Leaving & re-entering folder disables Extract button but not the Properties button
0:30 - Opening new tab deactivates both the buttons again

I also noticed that after opening the new tab where the buttons are disabled, the buttons will still be enabled if I go to the other tab where they were enabled, and they disable again when going to the new tab where they were disabled, so their enabled/disabled status seem tied to each tab.

In my case the buttons shouldn't be disabled at all, they don't have any modifier that disables them conditionally:

Confirmed, we'll fix this in 13.6.7 shortly.

1 Like

@leo

Fixed

Thanks for the great support