Skip to main content
Inspiring
October 27, 2025

Errors in startup script in Illustrator when Bridge is installed

  • October 27, 2025
  • 1 reply
  • 65 views

This error pops up on every Illustrator startup now:

 

Error in C:\Program Files (x86)\Common Files\Adobe\Startup Scripts
CC\Adobe InDesign\indesign-v20.0.jsx
Line I:
I/0 error

 

Tried reinstalling Creative Cloud and all apps using CC cleaner, no effect. Tried resetting preferences, no effect. Renaming the .jsx file (and then five or six others that it cycles through - or deleting the whole folder) helps but it's not recreated and removing it breaks Bridge automations.

 

Uninstalling Bridge helps, which is why I wondered if Bridge is somehow locking the files such that Illustrator can't read them?

1 reply

matt-tnmAuthor
Inspiring
October 27, 2025

Have managed to fix it - it's a Windows permissions error:


This is the technical fix for an "I/O error." You need to take ownership of the Startup Scripts CC folder and grant your user account full control.

Using File Explorer (GUI)


Navigate to C:\Program Files (x86)\Common Files\Adobe\.


Right-click the Startup Scripts CC folder and select Properties.


Go to the Security tab and click the Advanced button.


At the top, next to "Owner:", click the Change link.


In the "Enter the object name to select" box, type your Windows username. Click Check Names (it should underline your name) and click OK.


Check the box that says "Replace owner on subcontainers and objects."


Click Apply. You might see a few security pop-ups; just click Yes or OK.


After it has applied the new owner, click the Add button (on the same Advanced Security Settings window).


Click the "Select a principal" link at the top.


Type your username again, click Check Names, and click OK.


In the "Basic permissions" section, check the box for Full control.


Click OK, then OK again to close all windows.


Restart your computer and then try launching Illustrator.

(Don't be tempted to skip restarting.)


Illustrator is trying to read the file but your user account (or the application) is being denied permission at the file-system level.


This explains why it moves to the next file when you delete one; it's a folder-level access problem, not a file-specific one.