InDesign causing slow response on folders and drives

[AILAdobe]

Good day all

We are making use of Adobe InDesign CC 2017, Release 2017.1, Version 12.1.0, Build 12.1.0.56 x64

While using InDesign by our users they have noticed that the browsing within folders on local and network drives become slow non-responsive. Are there any other users that experience the same problems? We have looked at log files and event viewer, but unable to find any problems or errors recorded. We have uninstalled the software, re-installed it, update it to the latest build, but the problem still persists. Any suggestions from anyone?

[Alexandre Becquet]

Hello, is that the problem is recent ?

[AILAdobe]

Hi

The problem started when we upgraded to 2017. The users did not experience any issues with the previous version.

[@mj]

How big are the files and linked images combined?

You say both local and network drives. Try the following.

1. Package the file.
2. Move the file to your local drive on your computer.
3. Check responsiveness.

The reason for this suggestion is you may have the ID file saved locally and the links on a shared network drive. If there is a lot of traffic and the files are chunky this will affect speed.

Another q, do you have a lot fonts installed and active?

Oh I almost forgot, you may want to turn off live preflight when you're not actively using it.

Here's a couple of tips from Erica Games you may also want to try. https://indesignsecrets.com/6-tips-speed-up-indesign.php

HTH

[AILAdobe]

Hi

The issue is not with the files. While using InDesign for a while and you open Explorer to browse your folders or files (local and network), it becomes extremely slow and unresponsive.

[dave c courtemanche]

I was having similar issues with our servers, but with previous versions of Indesign. I would open a directory and it would take forever to populate. I think it was a server issue / OS (Mac) issue, not Indesign. Do you have a previous version of Indesign to test with?

[AILAdobe]

Hi Dave

We have the previous version(s). None of them had this issue. It only started when we upgraded to the newest version.