Launch issues after Windows update

Last updated on Jun 2, 2026

Learn how to resolve Adobe InDesign launch failure caused by VCRuntime issues after Windows updates.

Based on our investigation, the issue appears to be related to a Windows update corrupting the VC runtimes required to launch InDesign. There have been no recent changes in InDesign that would cause this behavior.

Microsoft has acknowledged the issue, and we’re working closely with them to resolve it as quickly as possible. In the meantime, here are a few workarounds suggested by Microsoft that may help reduce the impact.

Corrupt VCRuntime

Workaround 1: Repair VCRuntime

Repairing the VCRuntime installed resolves this issue. Before you begin, close all applications on your system.

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

Please send the logs as requested below to sharewithID@adobe.com for Adobe to share it with Microsoft for further investigation.

Additional information requested by Microsoft to assist with the issue investigation

To try to understand where/how Windows updates may be failing to properly update the components in question.

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.

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: