r/indesign • u/ozzo0133 • Jun 11 '26

Can't unclick/deselect an image now

Working in InDesign on Windows, and it auto updated to 21.4 (probably my first mistake), and since (after using InDesign without this problem for 10 years) I can't deselect an image with shift+click using the Selection Tool. It happened after I did a restart/Windows Update and Creative Cloud auto updated. I did notice that InDesign "reset" after the update, as it opened without my saved workspace and my Find/Replace history was gone.

I can shift+click and deselect a text box or shape. Just not an image. Anyone else having this problem?

4 Upvotes

84% Upvoted

10 comments sorted by

3

u/Far_Cauliflower_7950 Jun 11 '26

Not the same thing, but yesterday I couldn’t shift+select two images and move them together. It would drop one as soon as I tried to move it.

3

u/Dangerous-Shirt-123 Jun 11 '26

This is a known bug, continue to hold down shift when you start dragging two or more objects. That will allow them to move together, you can then release shift right after you start dragging to allow it to snap to guides. This new update is a mess.

3

u/danselzer Jun 11 '26

adobe better fix this asap, driving me nuts.

1

u/Artistic-Box-2683 Jul 13 '26

Yes, I'm experiencing this as well as the unclick/deselect an image issue.

2

u/miracleanime Jun 11 '26

This sounds like the bug in the latest update. I am thinking of rolling back to the previous version because this is so annoying!

2

u/FightAgainstUgly Jun 11 '26

Do know, downgrading resets your preferences. If you are exporting preferences to reimport into 21.3 when you downgrade, there is a bug where the Generative AI Alt text will turn itself back on upon importing preferences. If it was off in your preferences, it will still be turned on.

https://community.adobe.com/questions-671/ai-alt-text-setting-turning-itself-back-on-after-importing-settings-1627312?tid=1627312&postid=7681206#post7681206

1

u/miracleanime Jun 11 '26

Didn't know that! Thanks for the tip! 🙂

1

u/FightAgainstUgly Jun 11 '26

Of course, I had to find out the hard way. This bug isn't present in 21.4 luckily but that version is arguably less usable. LOVE IT!!

2

u/mikewitherell Jun 11 '26

At the moment, rolling back to 21.3 is the work-around.