Hi everyone,
Thank you for your continued patience and for sharing all the details and reports so far. We understand how disruptive this issue has been, especially in enterprise environments, and truly appreciate your cooperation during the investigation.
This issue has now been formally logged as a bug, and our product team is actively working in collaboration with Microsoft to investigate and resolve it. Current findings suggest the issue may be related to VC Runtime corruption occurring during or after certain Windows updates.
This issue has now been formally logged as a bug, and our product team is actively working in collaboration with Microsoft to investigate and resolve it. Current findings suggest the issue may be related to VC Runtime corruption occurring during or after certain Windows updates.
As an interim workaround, some affected users have reported that repairing the Microsoft Visual C++ Runtime resolves the launch issue temporarily and allows InDesign to launch successfully again. You can refer to the following HelpX article for the repair steps:
https://helpx.adobe.com/indesign/kb/crash-on-launch.html#unexpected
Additionally, Microsoft has recommended installing the latest supported VC Runtime version (v14.50.35719):
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-supported-redistributable-version
To help the engineering teams investigate this further, we now need additional diagnostic logs from systems that are currently experiencing the issue before any repair or reinstallation steps are performed.
If you are still encountering this problem, please help us collect the following information from the affected machine:
1. Generate Windows Update Logs
Get-WindowsUpdateLog
2. Export Event Viewer Logs
Open:
-
Event Viewer > Windows Logs > Application
-
Event Viewer > Windows Logs > Setup
-
Event Viewer > Windows Logs > System
For each section:
-
Click Filter Current Log
-
Filter for:
-
MsiInstaller
-
WindowsUpdateClient
-
SideBySide
-
Application Error
Then:
-
Click Save All Events As
-
Export the filtered logs
3. Check System File Corruption
Open Command Prompt as Administrator and run:
sfc /scannow
Please save or note the results after the scan completes.
4. Capture Side-by-Side (SxS) Logs
Open Command Prompt as Administrator and run:
sxstrace trace -logfile:%USERPROFILE%\Desktop\sxstrace.etl
After reproducing the issue, stop tracing and run:
sxstrace parse -logfile:%USERPROFILE%\Desktop\sxstrace.etl -outfile:%USERPROFILE%\Desktop\sxstrace.txt
5. Collect VC Runtime Installer Logs
Open Command Prompt as Administrator and run:
copy "%TEMP%\dd_vcredist*.log" "%USERPROFILE%\Desktop\"
This will copy the VC Redistributable installer logs to your Desktop.
6. Collect Microsoft Setup Diagnostic Logs (Recommended by Microsoft)
Microsoft has requested additional setup diagnostics using their official log collection utility.
Steps:
-
Download the Microsoft log collection utility:
https://aka.ms/getTSS
-
Extract the downloaded package
-
Open PowerShell as Administrator
-
Run:
Set-ExecutionPolicy -scope Process -ExecutionPolicy RemoteSigned -Force
Then run:
.\TSS.ps1 -Collectlog DND_SetupReport
This will generate a C:\MS_DATA folder containing diagnostic logs.
Once all files are collected:
-
Please place them into a single folder
-
Compress the folder into a ZIP file
-
Upload it using any public cloud sharing service such as Google Drive, Dropbox, OneDrive, WeTransfer, etc.
You can share the download link directly in this thread. If the information is confidential, feel free to send it to me via DM instead.
These logs are extremely important and will help both Adobe and Microsoft narrow down the root cause and accelerate the investigation.
Thank you again for your patience and support while we work toward a permanent resolution.
Best,
Abhishek
<Marking as correct for better visibility on the thread>
AdChoices