Adobe Vcruntime140_1.dll Was Not Found | Fix In Minutes

Guide / By

Adobe Vcruntime140_1.dll was not found usually means the Microsoft Visual C++ runtime is missing or damaged, so reinstalling the VC++ Redistributable restores the file.

What This Error Means And Why It Shows Up

When an Adobe app starts, it loads shared Windows components. One of those components is vcruntime140_1.dll, a file that ships with Microsoft’s Visual C++ Redistributable packages. If Windows can’t load that file, the app stops before it opens.

In plain terms, this DLL is part of the “glue” that lets programs built with Microsoft’s C++ tools run on your PC. Many games and creative apps lean on the same runtime files, so a broken runtime can spill into multiple programs.

This message often appears after a Windows update, a new graphics driver, a partial app update, or a cleanup app that removed “unused” runtimes. It can also show up after restoring a system image, copying an Adobe app from another PC, or moving program files to a new drive.

Sometimes the file is not missing at all. It’s there, yet Windows refuses to load it due to corruption, a bad dependency chain, or an outdated copy sitting next to the app that takes priority.

Clues That Point To A Runtime Issue

  • Crashes At Launch — The Adobe splash screen flashes, then the app closes with the DLL message.
  • Multiple Apps Fail — Two or more unrelated programs show “VCRUNTIME” or “MSVCP” errors.
  • Error After Updates — The app worked recently, then stopped after Windows, GPU, or Creative Cloud updates.
  • Fresh Install Still Fails — Reinstalling the Adobe app alone changes nothing.

The good news is that the fix is usually straightforward. In most cases you’re repairing the Windows runtime that Adobe depends on.

Fast Checks That Catch The Common Causes

Start with the quickest wins. These steps don’t change much on your system, yet they clear a lot of one-off glitches.

  1. Restart Windows — Save work, reboot, then try the same Adobe app again.
  2. Run The App As Administrator — Right-click the Adobe shortcut, choose Run as administrator, then test once.
  3. Confirm The Error Text — Note whether it says vcruntime140.dll or vcruntime140_1.dll, since the package you install is the same but the clue helps when you review logs.
  4. Check If Other Apps Fail — Open another program that relies on Visual C++ like a game launcher; if it fails too, the runtime is the likely root cause.
  5. Look For Antivirus Quarantine — Open Windows Security, check Protection history, and restore the file only if the detection is a false positive.

If you see Adobe Vcruntime140_1.dll Was Not Found again after these checks, go straight to the runtime repair steps next.

Adobe Vcruntime140_1.dll Was Not Found Fix That Works On Most PCs

The most reliable fix is to repair or reinstall the Microsoft Visual C++ Redistributable for Visual Studio 2015–2022. Adobe apps commonly rely on that bundle, and it includes vcruntime140_1.dll.

Do this even if you already see “Microsoft Visual C++” entries installed. A damaged install can sit there looking normal while the files behind it are broken.

Install Both x64 And x86 Packages

Even on 64-bit Windows, you may have 32-bit Adobe components or helper apps. Installing both versions avoids a mismatch where one piece loads and another fails.

  1. Open Apps And Features — In Windows Settings, go to Apps, then Installed apps or Apps & features.
  2. Search For Visual C++ — Look for entries named Microsoft Visual C++ 2015–2022 Redistributable (x64) and (x86).
  3. Repair First — Select each entry, choose Modify, then pick Repair when offered.
  4. Reboot After Repair — Restart so Windows can reload the refreshed runtime files.
  5. Reinstall If Repair Fails — If Repair errors out, uninstall the x64 and x86 entries, reboot, then install fresh copies from Microsoft’s official download page.

Pick The Right Installer For Your CPU

Most PCs run x64 Windows on Intel or AMD chips. Some Windows devices run on ARM chips, and they may need a different Visual C++ installer. If you’re unsure, open Settings, go to System, open About, then read System type.

  • x64 System Type — Install both x64 and x86 packages.
  • x86 System Type — Install the x86 package.
  • ARM64 System Type — Install the ARM64 package if Microsoft offers it for that runtime.

Confirm The File Exists In The Right Folder

After installing, the file should appear in system folders that Windows uses for shared runtimes. Don’t download a random DLL from a third-party site. That path is a fast route to malware and mismatched versions.

Where Windows Stores It What You Should See What It Suggests
C:\\Windows\\System32 vcruntime140_1.dll 64-bit runtime present
C:\\Windows\\SysWOW64 vcruntime140_1.dll 32-bit runtime present
Missing In One Folder No matching DLL Install that package version

If the file is present in both folders and the error still pops up, check Windows integrity next. A damaged component store can block proper loading even when the DLL exists.

Fixing Adobe Vcruntime140_1.dll Not Found Error On Windows 10 And 11

This section targets cases where the runtime is installed, yet Windows still refuses to load it. The usual causes are corrupted system files, broken side-by-side registration, or permission issues created by aggressive cleanup apps.

Run System File Checker And DISM

These built-in commands compare core Windows files against trusted copies and repair what’s broken. They don’t touch your personal files.

  1. Open Terminal As Admin — Right-click Start, choose Windows Terminal (Admin) or Command Prompt (Admin).
  2. Run SFC — Type sfc /scannow, press Enter, and wait for it to finish.
  3. Run DISM RestoreHealth — Then run DISM /Online /Cleanup-Image /RestoreHealth and let it complete.
  4. Reboot And Retest — Restart Windows, then open the Adobe app again.

Try A Clean Boot To Rule Out Conflicts

A clean boot starts Windows with a minimal set of startup apps and services. This helps when an overlay, injector, or security app blocks DLL loading.

  1. Open System Configuration — Press Windows+R, type msconfig, then press Enter.
  2. Hide Microsoft Services — On the Services tab, tick Hide all Microsoft services, then click Disable all.
  3. Disable Startup Apps — Open Task Manager from the Startup tab link, then disable optional startup items.
  4. Reboot And Test Adobe — Restart, launch the Adobe app, then re-enable items in batches to find the blocker.

Check For Conflicting DLL Copies Next To The EXE

Some programs ship their own copies of Visual C++ files inside the program folder. If a stale copy sits next to the Adobe executable, Windows may try that one first and fail due to a version mismatch.

  • Search The Adobe Install Folder — Look for vcruntime140_1.dll in the same folder as the app’s .exe.
  • Rename Suspicious Copies — Add .bak to the file name, then try launching again so Windows falls back to the system runtime.
  • Undo If Needed — If the app breaks in a new way, restore the original name and continue with the next steps.

Reset Permissions On The Adobe Folder

If permissions were tightened, the app may not be able to read a dependency in its own folder. This is less common, yet it happens on shared PCs or after manual folder moves.

  1. Locate The Folder — Find the app folder under Program Files or Program Files (x86).
  2. Open Security Settings — Right-click, choose Properties, then the Security tab.
  3. Restore Inheritance — If inheritance is off, turn it on so default Windows rules apply.
  4. Apply And Test — Apply changes, then open the Adobe app again.

Adobe App Fixes When The Runtime Looks Healthy

If Visual C++ repairs and Windows checks look clean, treat the Adobe installation as the moving part. Adobe apps can end up with incomplete updates, broken plugins, or a damaged licensing cache that triggers startup failures that mimic a runtime issue.

Update The Creative Cloud Desktop App

Creative Cloud controls updates and shared components. An out-of-date Creative Cloud install can leave a newer Adobe program pointing at older shared files.

  1. Open Creative Cloud — Launch the Creative Cloud desktop app from the Start menu.
  2. Install Creative Cloud Updates — Apply updates for Creative Cloud itself first.
  3. Update The Failing App — Then update the Adobe app that throws the error.
  4. Reboot After Updates — Restart so any locked files can be replaced.

Reinstall The Specific Adobe App Cleanly

Reinstalling just the failing app is often enough, especially if the issue began right after an interrupted update or a forced shutdown.

  1. Uninstall The App — In Creative Cloud, uninstall the affected app.
  2. Remove Third-Party Plugins — Move plugins out of the app’s plugin folders so the first launch is stock.
  3. Install Fresh — Reinstall the app from Creative Cloud and launch it once.
  4. Add Plugins Back Slowly — Reintroduce plugins one by one so you can spot a bad add-on fast.

Clear Caches That Can Break Startup

Some Adobe apps load caches at launch. When a cache gets corrupted, the app may fail early and still show a dependency message.

  • Sign Out And Back In — Sign out of Creative Cloud, reboot, then sign in again.
  • Reset Preferences On Launch — Use the app’s preference reset shortcut if it offers one.
  • Test A New Windows User — Create a fresh local user, sign in, then launch the Adobe app to rule out profile-level cache problems.

Safer Habits That Keep The Error From Returning

Once the error is gone, a few habits help keep it from returning after the next update cycle or cleanup pass. None of these require extra software, and they don’t slow your PC down.

  • Leave Visual C++ Packages Installed — They look redundant, yet different apps rely on different versions and architectures.
  • Avoid Random DLL Downloads — A single mismatched DLL can introduce crashes, security risk, or silent instability.
  • Finish Updates Before Rebooting — Let Windows and Creative Cloud complete installs so shared runtimes aren’t left half-written.
  • Keep Install Paths Stable — Avoid moving Program Files folders by hand after installation.

One-Page Checklist You Can Reuse

  1. Repair VC++ 2015–2022 — Repair x64 and x86 packages, then reboot.
  2. Reinstall VC++ If Needed — Uninstall both, reboot, then install fresh from Microsoft.
  3. Run SFC And DISM — Repair Windows files, reboot, then test the Adobe app.
  4. Clean Boot Test — Launch Adobe with startup apps disabled, then add items back in batches.
  5. Reinstall The Adobe App — Install the app clean, then add plugins back slowly.

If you see the same message again months later, repeat the Visual C++ repair step first. It stays the fastest path for most cases.

When you’re troubleshooting, keep changes narrow and reversible. If a step doesn’t change the result, revert it and move on.

If Adobe Vcruntime140_1.dll Was Not Found returns after a major update, repair the redistributables first before touching Adobe settings again.