Go to Control Panel > Programs > Programs and Features.
Last updated on
Jun 8, 2026
Learn how to resolve Adobe InDesign launch failure caused by VCRuntime issues after Windows updates.
Our investigation confirms that a Windows update corrupted the VC runtimes required to launch InDesign. No recent InDesign changes caused this issue.
Microsoft has acknowledged the issue. We are working directly with them to resolve it. In the meantime, use one of the following Microsoft-recommended workarounds.
Corrupt VCRuntime
Workaround 1: Repair VCRuntime
Repairing the VC installed resolves this issue. Before you begin, close all applications on your system.
Right-click each of the installed Microsoft Visual C++ Redistributable packages (x64 and x86).
Select Change > Repair (if the Change option is available). Follow the instructions to repair the Microsoft Visual C++ Redistributable.
If the Change option is not available, follow the steps in Workaround 2.
Restart the system and launch InDesign.
Workaround 2: Install the latest VCRuntime
Install the latest supported VCRuntime from Microsoft.
Help track the issue
Adobe is actively collaborating with Microsoft, and the investigation is being tracked under Microsoft Support Request Number 2602270030003886. Follow either of these options to help Microsoft and Adobe investigate this further:
Raise a Microsoft Service Request
Customers are advised to create a support ticket directly with Microsoft, share the additional logs listed below, and reference Adobe-created Microsoft Support Request Number: 2602270030003886 to help ensure coordinated tracking and investigation across both teams. Once you create the Microsoft support ticket and include the requested logs below, please email the InDesign team at sharewithID@adobe.com with your Microsoft Support Request Number.
Share logs with Adobe ID
If you're still experiencing this issue, please send your logs to sharewithID@adobe.com so we can share them with Microsoft to help resolve it more quickly.
Additional information requested by Microsoft to assist with the issue investigation
Please provide the following information.
Information 1: Additional logs by running collect.exe
Download collect.exe from Download Microsoft Visual Studio and .NET Log Collection Tool. This utility captures setup logs for Visual Studio, .NET, and even the VC Redistributable packages.
If you have access to a machine where the applications continue to fail to launch after applying the updates, please run the collect.exe utility and share the generated setup logs with Microsoft or Adobe for further analysis.
After running collect.exe, all the relevant installation logs will be zipped to %TEMP%\vslogs.zip.
Information 2: Additional logs by running TroubleShootingScript toolset (TSS)
Capture additional logging via the TroubleshootingScript toolset (TSS) to generate a DND_SetupReport.
Download and unzip toolset from: https://aka.ms/getTSS.
Select the Windows Start menu and type Powershell.
Right-click Windows PowerShell or PowerShell and select Run as administrator to launch an elevated PowerShell prompt.
Run the following to ensure the script can be executed: Set-ExecutionPolicy - scope Process -ExecutionPolicy RemoteSigned - Force
Capture the installation data by running the tss script as follows: .\TSS.ps1 -Collectlog DND_SetupReport
Zip the resulting C:\MS_DATA folder containing the files.
Information 3: Printer driver details
Please share details of any printer drivers installed on the affected machine, particularly older or legacy drivers such as Fiery or Canon printers. Such drivers may overwrite newer VC runtime components with outdated DLL versions during Windows updates.
Refer to the following links to track more information from Adobe around this issue:
Create print and digital materials with InDesign
Design impactful ads, magazine and book layouts, and more.
