Skip to main content
Participating Frequently
November 9, 2021
Answered

InDesign crashes every time, immediately upon launch since, v.17 on Win11

  • November 9, 2021
  • 2 replies
  • 3245 views

Hi All!
InDesign will not open. 
Each time upon launch "Sorry, an error occurred screen" pops up. 

- Started after update to Win 11 and v.17 of ID
- Happens upon launch of app itself as well as trying to open a INDD file
- Reinstalled InDesign, problem still occures
- All other Creative Cloud applications work normally (win 11, all updated to latest release).

Crash report:
https://justpaste.it/6z2ez

System:
Win 11 Pro v21H2
Intel(R) Core(TM) i7-9750H
32 GB RAM
NVIDIA QUADRO RTX 3000

Any suggestions, posible fixes or encountered simillar problems?
Thanks in advance.

This topic has been closed for replies.
Correct answer marekš47917795

Hi, the same happend to me on win 11 (22H2), with Indesign 18.5. I did uninstall only Indesign with CC cleaner and did new clean install of InDesign. Now it works like before, but all custom settings are gone.

2 replies

Anshul_Saini
Community Manager
Community Manager
November 9, 2021

Hi there,

 

Sorry about the crashing! I know that's really frustrating. I would request you to submit the crash report by following the steps suggested here (https://helpx.adobe.com/indesign/kb/submit-crash-reports.html).
While submitting the crash report, please use the same email address with which you are signed in on this community. This will help us find the crash report and help accordingly.

 

Also, do you have any Anti-Virus installed on your machine? If yes, does adding InDesign as an exception in the Anti-Virus app settings help resolve the issue?

 

Additionally, you may try the following steps and let us know if it helps:

  • Try running the app in Safe Mode & Hidden Admin Account?
  • Manually reset preferences by renaming the folders from the following locations:
    - C:\Users\<your username>\AppData\Roaming\Adobe
    - C:\Users\<your username>\AppData\Local\Adobe
    Rename InDesign folders to InDesign.old Launch InDesign from the Creative Cloud Desktop app.
    Disclaimer: Please note that resetting preferences will remove all the custom settings, and InDesign will launch with default settings. This way, all your old settings will be saved in .old folders, and InDesign will recreate new folders with default settings.
  • Rename the CEP folder to CEP.old from the following location:
    C:\Program Files (x86)\Common Files\Adobe
  • If that doesn't help, rename the extensions folder to UXP.old in the following location:
    C:\Program Files\Common Files\Adobe\
    C:\Program Files (x86)\Common Files\
  • If that doesn't help either, uninstall the application using the CC Cleaner tool and reinstall from the Creative Cloud Desktop app.

 

We are here to help. We just need more information.

 

Thanks & Regards,

Anshul Saini

Participant
November 15, 2021

These solutions provided by @Anshul_Saini  did not work. This is very fustrating. What should Windows 11 users do if the updates arent compatiable?

James Gifford—NitroPress
Legend
June 4, 2022

This is an older topic. My problem got "solved" after I re-installed, not only ID but the whole Creative Cloud App with all the applications. To this day, don't know what the cause was. Yes, I had Windows Defender on (default Windows settings) although Win Defender is on now while all is working so I don't think there's a connection there. 


Good to hear! As noted before and in many threads, many of us have updated to Win11 without a hitch, so there is nothing inherent about the version that is incompatible with CC.

 

My guess would be that a common file was outdated or corrupted, perhaps during the Win11 update, and a bare-metal CC reinstall fixed it. Which doesn't reduce any of the irritation at not having things work right, right from the start.

 

Participating Frequently
November 9, 2021

Just to follow up:
I have also installed the last version besides v.17 (v16.4) and the same problems occur. 
InDesign will crash upon launch every time. 

The only thing that has changed on this system is an update to Win11 to which I am connecting the problem right now, 
although do not have 100% certainty of the cause.