InDesign 20.1 Update causing strange box selection behavior

[Ignacio23157647nm3k]

Every since my InDesing updated to 20.1, when I select a window or block of text, it will not show as highlighted, but it is. I have to click off and then click back onto the block a few times so that the box appears normally selected. Overall, InDesign seems to be running a bit sluggish as well after this update.

Obviously, something needs to be fixed in this last update because the "removes bugs" didn't work. Now I have NEW bugs that weren't here before.

[Abhishek Rao]

Hello @Ignacio23157647nm3k, 

I tried reproducing the issue, and I don't seem to face it on Windows and on macOS. Would you mind sharing the details of the OS? Would you mind sharing a screen recording demonstrating the issue? Is the issue specific to a particular file or happening with others too (including the newly created ones)? Are the affected files stored on local drive, remote location, external drive or on cloud? 

Moreover, would you mind testing the issue if it happens in Safe mode. This will isolate any third-party app conflicting with InDesign. Reference: 

Windows: https://adobe.ly/4he9PG5

macOS: https://adobe.ly/4heQTaf

Let me know how it goes. 

^

Abhishek 

[Ignacio23157647nm3k]

Dear Abhishek -

Thank you for looking into this issue. I have addressed your questions.

Here is a screen recording showing the issue. What is happening in the recording is that I hover over a box and I am clicking the mouse, but the box does not show itself highlighted. When I roll off of the box, suddenly it highlights. I do this several times. 

The issue persists in Safe Mode.

My OS is: 14.6.1 (23G93)
The issue happens with Server-based files and Local files.

[Eugene Tyson]

When moving to a new version somethings might need to be 'restructured' as new features, new structures and connections - is how I imagine it. 

Therefore, it's logical to think that a file from a previous version might not perform the same in a newer version, maybe. 

What I always do with a project when I have a new version of the software is 

1) I wouldn't continue the project in the new version - I'd finish the project in the version of the software I started in 

2) If that's not an option - you can open your file in the previous version of InDesign - and either continue your edits there (but maybe you can't for some reason)

2a) Open in previous version of InDesign - export to IDML - open that in New Version of InDesign

2b) Open in current new version of InDesign - export to IDML - open that - resave it as a new name

Does the issue persist?

If it persists 

Even with new version of software installs may not go well 

Try resetting your preferences:

Windows: Start InDesign, and then press Shift+Ctrl+Alt. Click Yes when asked if you want to delete preference files.
macOS: While pressing Shift+Option+Command+Control, start InDesign. Click Yes when asked if you want to delete preference files.
A dialog will appear asking to delete the InDesign Preferences, select 'Yes' on this dialog.
Further info and instructions here if needed:
https://helpx.adobe.com/in/indesign/kb/indesign-preferences-support-file-locations.html

If it persists

Reinstalling rarely fixes everything - you can do a complete reinstall using the
Creative Cloud Cleaner Tool https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html

-----------

Still not working - I'm afraid you may need to finish in the previous finish of InDesign. 

[leo.r]

My OS is: 14.6.1 (23G93)

By @Ignacio23157647nm3k

In addition to other suggestions: update Sonoma to its latest version (I think it's 14.7). Also, I know you mentioned the issue still persists in the save mode, but still: are you running Magnet or any other window management utilities, or any corporate security software?

[Todd33636751h6zi]

I am having this exact same issue. It is beyond frustrating and is dramatically slowing down my work flow. Let me know what you need from me to help resolve this.

[Todd33636751h6zi]

Realized I didn't provide any system information. I am using InDesign 20.1 on MacOS Sequoia 15.3 on an Apple M1 Pro processor. None of these issues existed prior to updating to InDesign 20.1.

[Ignacio23157647nm3k]

After suffering with this issue, I have discovered that the way to navigate the issue is to click on boxes (text or photo) and then move off of the box. When you move off of the box it will then highlight.

The other issue is the if you highlight a box and use the arrow keys to move it - nothing happens until after a long delay. I found that by just clicking on the desktop after I do the move seems to kick it into action. 

This has been a very bad update and I wish I would've never done it.

[Todd33636751h6zi · Accepted solution]

I deleted the InDesign preference files using the method below. This has resolved the issue. Thanks.

macOS: While pressing Shift+Option+Command+Control, start InDesign. Click Yes when asked if you want to delete preference files.
A dialog will appear asking to delete the InDesign Preferences, select 'Yes' on this dialog.
Further info and instructions here if needed:
https://helpx.adobe.com/in/indesign/kb/indesign-preferences-support-file-locations.html

[Ignacio23157647nm3k]

Deleting the preferences has failed to solve the issue. If I click on a text box it does not highlight until I move the pointer OUT of the box. This is extremely irritating.

[René25962706bien · Accepted solution]

I got the same error, but only in documents with hidden pages. I solved it by deleting the hidden pages..

[prdh67 · Accepted solution]

Also experiencing this, very annoying. InDesign 20.1 and Sequoia 15.3. Toggling to a different workspace and back seems to fix it, but if I reset my preferences, it comes back.

[Todd33636751h6zi]

Deleting the preferences back on Feb 5, 2025 fixed this. However, it's back again as of March 25, 2025. The update to 20.2 happened March 10, but I didn't notice this behavior until the 25th.

[Todd33636751h6zi]

I just deleted the preference files again by holding down the selected keys while starting. This fixed the issue again. I guess we'll have to wait and see how long it lasts.