Unable to Move Text Boxes and Objects in InDesign 2025

[BerkleyDris]

I can't move text boxes, objects or pages. When I try to move anything the curser changes to a stop sign (red circle with diagonal red line). I have opened a new document, but it still happens. I can however resize boxes/images using the 'handles'. Everything was working fine before. I have not installed any updates.

Thanks for any help.

<Title renamed by MOD>

[Robert at ID-Tasker]

Everything was working fine in 2025 or 2024? 

[BerkleyDris]

Both. I've just reinstalled my CS5.5 version and that does the same thing! I've not had any Windows updates in the meantime. Maybe there was an Adobe update recently?

[Robert at ID-Tasker]

I was talking about updating InDesign from 2024 to 2025. 

Check your AntiVirus software - especially Microsoft Defender. 

[BerkleyDris]

I've looked at anti-virus, but it doesn't seem to have an effect. I used my CS5.5 Master Collection for many years but upgraded to the CC All Apps in June. Everything has been working fine until now. I reinstalled InDesign CS5.5, but it had the same issue. I uninstalled InDesign 2025 and reinstalled, but still same problem.

[Eugene Tyson]

This issue sounds like it could be related to permissions or some system interference. 

This can easily be checked by starting the computer in Safe Mode and run only InDesign to see if the issue persists.

If it is ok then it's likely something interfering with InDesign.

You can then reboot back to normal OS by rebooting the computer and not entering safe mode.

-------------------------
Preferences Issue
Corrupted preferences can cause strange behaviours. Try resetting the InDesign preferences:
Windows: Press Ctrl+Alt+Shift immediately after launching InDesign.
Mac: Press Cmd+Ctrl+Opt+Shift right after starting InDesign.

------------------------

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

------------------------

If Creative Cloud reinstall didn’t help, this could be a system-level issue. Check if InDesign has the necessary permissions on your system.

Windows: Go to Settings > Privacy & Security and check if InDesign has access to the system.

Mac: Under System Preferences > Security & Privacy, ensure that InDesign is allowed to control your computer (look under Accessibility).

-------------------
Graphics Driver/Software Conflicts
Sometimes, antivirus software or even graphics drivers can interfere with InDesign’s functionality, especially if there’s been a recent update.

Try disabling any third-party antivirus 

As already suggested by @Robert at ID-Tasker 

temporarily turning off features in Microsoft Defender (Real-time protection, Controlled folder access, etc.) and test if this resolves the issue.

----------------------------------------
Use Admin Mode or Compatibility Mode
Run InDesign in Administrator mode to see if that changes anything.
For older versions (like CS5.5), try running it in Compatibility Mode for an older version of Windows, if you’re on a newer OS.

----------------------------
System-Wide Troubleshooting
Since CS5.5 shows the same issue, it suggests something broader affecting all Adobe apps.

• Restarting the system
• Updating system drivers
• Creating a new user profile

can sometimes reset permissions that may have changed without notification.

If none of these steps resolve the issue, it might be worth checking if a system rollback or even a clean install of Windows is necessary, though this would be a last resort.

[BerkleyDris]

Gosh, thanks for that. I'll have a go at your suggestions and let you know what happens. I'm still very puzzeled as I saved my InDesign document on Saturday, then when I looked at it on Monday I had this problem!

[Eugene Tyson]

At the end of the day it's a computer, and files can be updated, systems can update, something can change, files can become a bit corrupt and need to be reloaded/reinstalled. 

Maybe a bad shut down - or the program was only closed in the foreground but running in the background in the middle of quitting and the computer shut down, causing something to happen.

Who knows.