InDesign 21 won't open after a Windows update? Repair VC++

Confirm all four incident markers

Adobe's current known-issues record calls this incident ID-01. It applies to InDesign 21.0 and later on Windows. Adobe says InDesign 20.x is not affected by this specific incident. The matching symptom is that InDesign does not launch or crashes during startup after a Windows update.

Do not use one broad symptom as proof. Confirm each item before touching a shared runtime:

• Application version: Creative Cloud or another reliable record shows InDesign 21.x.
• Operating system: the affected computer runs Windows.
• Launch state: no usable window appears, or InDesign crashes during startup.
• Timing: the failure began after a Windows update.

The error code 0xc0000142 may appear in some launch failures, but Adobe does not require that code for the incident match. Preserve any code you see. Do not add one from a forum post to a failure that did not show it.

Record the evidence before the repair

Open Creative Cloud and record the exact InDesign version. In Windows, record the edition, version, and OS build. Check Windows Update history and note the most recent update installed before the first failed launch. Save the update name or KB number if Windows shows one.

Try one normal launch and record the last visible state. Note whether no window appears, the splash screen stops on a named item, or a visible error opens. Take a screenshot that excludes client documents, license details, email addresses, account names, and private file paths.

If InDesign 21.x opened successfully after the same Windows update, or if the problem started before the update, the current evidence does not fit Adobe's incident cleanly. Skip the runtime repair and investigate the actual launch state instead.

If a different application fails to install a runtime, the Windows installer evidence guide explains how to preserve the stage and error before changing shared components. Do not transfer the EA-specific fix to InDesign.

Repair the installed x64 and x86 runtimes

Save work in every open application and close them. On a business, school, or otherwise managed computer, stop here and send the administrator the evidence plus Adobe's support page from the sources below.

Open Windows' installed-apps or Programs and Features view. Find the installed Microsoft Visual C++ Redistributable entries named by Adobe. Repair both the x64 and x86 packages when Windows offers Change or Modify, then Repair. Approve only the normal Microsoft installer prompt.

Do not remove the packages first. Do not repair unrelated runtimes or select similarly named components at random. If the entries or controls on your computer do not match Adobe's instructions, stop and use Adobe Support or your administrator rather than improvising.

After both repairs finish, restart Windows. A restart is part of Adobe's procedure, not an optional cleanup step. Do not judge the result from the installer completion message alone.

When Repair is unavailable

Adobe says to use Microsoft's current Visual C++ Redistributable page when the installed package does not offer Change. Follow Adobe's link to Microsoft Learn. Microsoft says the package architecture must match the target application and tells application users to follow the vendor's directions.

Use only Microsoft's official download links. Do not use a driver site, DLL archive, download mirror, search ad, or forum attachment. Check the page address before downloading and keep the installer name with your notes.

Adobe's incident instructions call for the x64 and x86 runtimes. If you cannot tell which packages are present or whether your organization permits installation, stop and ask the administrator or Adobe Support. Do not guess based on whether Windows itself is 64-bit.

Restart Windows after the official package work completes. If the installer fails, preserve the exact message and code. That installer failure becomes the next problem to investigate before InDesign is tested again.

Test InDesign once after restart

After Windows restarts, launch InDesign normally without opening a document from File Explorer or a recent-items shortcut. Wait for the Home screen. Record whether the app opens, crashes during startup, remains in the background, or shows an error.

If the Home screen appears, confirm the installed InDesign version and close the application normally. Launch it once more. Then open a protected copy of one representative document from inside InDesign. Keep the original file untouched until the launch and document checks both pass.

If InDesign still does not open, stop repeating the runtime repair. Save the post-restart launch state and any new error. Adobe lists this incident as confirmed and in testing, external, and dependent on Microsoft. Adobe's current 21.6 release notes do not say that version 21.6 resolves it.

A working launch after the repair supports the runtime path, but it does not prove why the runtime became corrupted. It also does not guarantee that every document, font, plug-in, or connected asset will work.

If the match is incomplete

Use the evidence you recorded to choose a narrower branch. An InDesign 20.x failure, a macOS launch failure, a crash that began before a Windows update, or a document-specific crash does not match ID-01 as Adobe defines it.

• Splash screen stops on a named plug-in or font: preserve the exact name and use Adobe's guidance for that component.
• InDesign opens until one document loads: protect the original and treat the document, links, fonts, or plug-ins as a separate branch.
• Several applications fail: record each application and shared error before changing Windows again.
• The runtime installer fails: keep its code and contact Microsoft, Adobe, or your administrator with that evidence.

Do not remove a Windows update to force a match with the timeline. Update removal can affect security and other applications, and it is not Adobe's published fix for this incident.

Where OmniMend fits

On a supported Windows 10 or Windows 11 x64 computer, OmniMend can organize non-secret system, application, update, and timeline evidence around the launch failure. It does not repair Visual C++ Redistributables, change InDesign, install Adobe software, fix a document, remove an update, or confirm Adobe's root cause.

Adobe's instructions and Microsoft's official packages remain the repair path. If you want a separate local record before or after the repair, download OmniMend. Review and redact any report before sharing it.