vcomp140_app.dll Errors: The Real Fixes for Windows 11 and 10

If Windows says vcomp140_app.dll was not found, could not be loaded, or is not designed to run on Windows, the application that requested it cannot start. The vcomp140_app.dll error usually means that the program’s Microsoft Visual C++ OpenMP runtime, packaged-app framework, or app-local files are missing or damaged.

The 60-second answer

First identify which game or application produced the message. Then repair or reinstall that application from its official source.

As an Amazon Associate I earn from qualifying purchases.

For the exact filename vcomp140_app.dll, repairing the owning Store, MSIX, UWP, or packaged desktop application is usually more useful than copying a DLL into a Windows folder. The file is associated with Microsoft’s Visual C++ OpenMP runtime and is commonly deployed through the Microsoft.VCLibs.140.00 framework, although some traditional games and programs bundle their own copy.

If the message instead names VCOMP140.DLL without _app, install or repair the matching official Microsoft Visual C++ Redistributable package. A 32-bit application needs the x86 package, while a 64-bit application needs x64. Many 64-bit Windows systems need both because they run applications of both architectures.

Do not download an individual DLL from a random file site. A replacement can have the wrong architecture, an incompatible build, or malicious code, while leaving the damaged application installation untouched.

What is vcomp140_app.dll?

vcomp140_app.dll is part of Microsoft’s Visual C++ v14 OpenMP runtime family. OpenMP is a programming interface used by applications that distribute work across multiple processor cores. Microsoft documents the corresponding VCOMP140.DLL as the dynamic Visual C++ OpenMP runtime for applications compiled with OpenMP. See Microsoft’s OpenMP Library Reference.

The _app suffix matters. It generally indicates a runtime built or packaged for an application deployment model rather than the ordinary desktop DLL name. Packaged Windows applications commonly receive C++ runtime components through Microsoft’s Microsoft.VCLibs.140.00 framework dependency. Packaged desktop applications can also use Microsoft.VCLibs.140.00.UWPDesktop.

A Microsoft diagnostic listing shows VCOMP140_app.DLL inside a package path resembling:

C:\Program Files\WindowsApps\
Microsoft.VCLibs.140.00_<version>_<architecture>__8wekyb3d8bbwe\

That location is documented in a Microsoft Q&A diagnostic listing. The exact package version, architecture, and installation path can differ.

This is not normally a core Windows file that you should manually place in:

C:\Windows\System32
C:\Windows\SysWOW64

It may be installed as part of a Store or MSIX framework, or placed beside a game’s executable by the game installer. The runtime technology comes from Microsoft, but the copy that failed may belong to the application that installed it.

Microsoft’s MSIX troubleshooting documentation explains that packaged applications can depend on framework packages such as VCLibs. Those dependencies are normally installed with the application or downloaded automatically by the Microsoft Store.

Why does the error mention _app?

The Windows loader displays the name requested by the executable. If the program was built to load vcomp140_app.dll, Windows reports that exact filename rather than changing it to vcomp140.dll.

The standard loader wording may look like this:

The code execution cannot proceed because vcomp140_app.dll was not found. Reinstalling the program may fix this problem.

Other versions of Windows may show:

The program can’t start because vcomp140_app.dll is missing from your computer. Try reinstalling the program to fix this problem.

×

Free tools Windows power users keep installed

One-click scans. No signup required.

Stop driver crashes →Clean & speed up →

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A damaged file can also produce wording such as:

vcomp140_app.dll is either not designed to run on Windows or it contains an error.

The exact _app wording varies by Windows version, architecture, localization, executable, and the way the dependency failed. The important detail is the filename requested by the application, not the precise wording of the dialog.

The similar-looking names are easy to confuse:

Filename in the error	Most relevant repair path
vcomp140_app.dll	Repair the Store, MSIX, packaged desktop application, or the game that bundled it. Check VCLibs.
VCOMP140.DLL	Repair or install the matching desktop Visual C++ Redistributable.
A different vcomp filename	Identify the application and use the runtime package required by that application.

The desktop redistributable and packaged-app VCLibs framework are related, but they are deployed differently. Installing vc_redist.x64.exe should not be treated as a guaranteed replacement for a missing vcomp140_app.dll inside an MSIX application.

First identify the failing application

The filename alone cannot tell you which program owns the failed copy. Before changing Windows components, find the executable that produced the dialog.

Check the error window

Look at the title bar and the application icon. A title such as a game name, launcher name, camera utility, or editing application usually identifies the owner.

If the error appeared after clicking a shortcut, right-click that shortcut and choose Properties. The Target field shows the executable or launcher path. Do not edit the target. You only need the program name and installation location.

Check Reliability Monitor

Reliability Monitor often gives a clearer record than the error dialog.

1. Press Win+R.
2. Enter perfmon /rel.
3. Press Enter.
4. Select the day and approximate time of the failure.
5. Expand the red critical event.
6. Note the Faulting application name, application path, and any faulting module.
7. Select View technical details if it is available.

If the application path points to a game library, the game’s own files are the first repair target. If it points into C:\Program Files\WindowsApps, it is likely a packaged application or framework dependency.

Check Event Viewer

1. Press Win+R.
2. Enter eventvwr.msc.
3. Press Enter.
4. Open Windows Logs.
5. Select Application.
6. Use Find in the Actions pane and search for the application name or vcomp.
7. Open the event recorded at the failure time.
8. Record the faulting application name, path, module name, and exception information.

Do not assume that the Faulting module name is the original cause. A missing dependency may cause the application to fail before its own code loads, and a damaged runtime can be reported as the module involved in the crash.

Check whether the program is packaged

A Store application usually appears in:

Settings > Apps > Installed apps

An MSIX or packaged desktop application may also appear there even if you normally launch it from a desktop shortcut.

A traditional desktop game or program is more likely to be installed under:

C:\Program Files
C:\Program Files (x86)
A Steam library
An Epic Games library
A publisher-specific folder

The folder alone is not definitive, but it helps determine which repair route to use.

Fix 1: Repair or reinstall the application

This is the safest first fix when the error names vcomp140_app.dll. The application installer can restore the correct runtime, package registration, permissions, and supporting files together.

Repair a Microsoft Store or packaged application

On Windows 11:

1. Open Settings.
2. Select Apps.
3. Select Installed apps.
4. Find the application.
5. Select the three-dot menu beside it.
6. Choose Advanced options.
7. Select Repair.
8. Start the application again.

Repair preserves the application’s data where Windows supports it. If the error remains:

1. Return to the same Advanced options page.
2. Select Reset.
3. Confirm the reset.
4. Launch the application again.

Reset can remove application data and settings, so use it after Repair rather than before.

On Windows 10:

1. Open Settings.
2. Select Apps.
3. Select Apps & features.
4. Select the affected application.
5. Choose Advanced options.
6. Select Repair.
7. If necessary, use Reset.

Microsoft documents these options in its guide to repairing apps and programs in Windows.

If the application does not offer Repair or Advanced options, uninstall it from the same Apps page and reinstall it from the Microsoft Store or the publisher’s official installer.

Update the Store application

A partially completed application update can leave the package and its framework dependency out of sync.

1. Open the Microsoft Store.
2. Select Library.
3. Select Get updates.
4. Allow the Store to update the affected application and its dependencies.
5. Restart Windows.
6. Try the application again.

If the Store reports an installation failure, restart the computer before trying the update again. If only one application is affected, uninstalling and reinstalling that application is usually more targeted than repairing Windows globally.

Repair a traditional desktop program

Some desktop installers include a repair mode.

1. Press Win+R.
2. Enter appwiz.cpl.
3. Press Enter.
4. Select the affected program.
5. Choose Change, Repair, or Modify if the installer provides it.
6. Complete the repair.
7. Restart the program.

If there is no repair option, download the installer from the application publisher or reinstall using the launcher that originally installed it. Do not remove unrelated Visual C++ packages while doing this. Several runtime generations can coexist, and older applications may need older packages.

Repair a game through its launcher

For Steam:

1. Open Steam.
2. Open Library.
3. Right-click the game.
4. Select Properties.
5. Select Installed Files.
6. Choose Verify integrity of game files.
7. Wait for the process to finish.
8. Start the game again.

For Epic Games Launcher:

1. Open the launcher.
2. Open Library.
3. Select the three dots beside the game.
4. Choose Manage.
5. Select Verify.
6. Wait for the scan and repair to finish.
7. Launch the game again.

Other launchers use similar Verify, Repair, or Scan options. If verification finds nothing but the error continues, reinstall the game from the same official launcher. This is especially important when vcomp140_app.dll is an app-local file beside the game executable rather than a shared Windows framework file.

How to tell whether this fix worked

The repair succeeded if the application reaches its normal startup screen without the DLL dialog. A successful repair may not display a confirmation about the DLL itself.

If the same error returns immediately, check whether:

• the antivirus quarantined the restored file;
• the launcher repaired the wrong installation;
• the application is running from a second library or external drive;
• the package dependency failed to register;
• the application is requesting VCOMP140.DLL rather than vcomp140_app.dll.

Fix 2: Check the VCLibs framework package

For a Store or MSIX application, the runtime may be present but damaged, missing, or not registered for the current user.

Open PowerShell and run:

Get-AppxPackage *Microsoft.VCLibs.140.00* |
  Select-Object Name, Version, Architecture, InstallLocation, Status

To open PowerShell:

1. Open Start.
2. Search for PowerShell.
3. Open Windows PowerShell.
4. Paste the command.
5. Press Enter.

Review the output:

• Name identifies the framework package.
• Version shows the installed package version.
• Architecture shows whether it is x86, x64, ARM, or another supported architecture.
• InstallLocation shows where Windows installed it.
• Status can help reveal an abnormal package state.

If the command returns no VCLibs package, the affected application may not have installed its framework dependency correctly. Reinstall the application first. Store applications normally obtain framework dependencies automatically.

If the package exists but the application still fails, perform the application Repair and Reset steps described above. Avoid manually changing permissions on C:\Program Files\WindowsApps. Taking ownership of that directory can interfere with Windows servicing and package security.

Sideloaded or enterprise-deployed applications

Sideloaded MSIX applications may require the publisher to provide a matching VCLibs dependency package. Microsoft’s documented installation pattern installs the dependency before the application:

Add-AppxPackage -Path .\Microsoft.VCLibs.x64.14.00.Desktop.appx
Add-AppxPackage -Path .\MyApp.msix

Use the exact dependency supplied by the application publisher or deployment administrator. Do not search for an arbitrary AppX package by filename and install it.

The architecture must match the application. A 32-bit package, 64-bit package, and ARM-family package are not interchangeable in every deployment. Microsoft describes these framework dependencies in its MSIX troubleshooting guide and desktop-to-UWP packaging guide.

If Add-AppxPackage returns an error, record the full error text and code. It may indicate a missing dependency, a package version conflict, an architecture mismatch, or a deployment permission issue. Repeatedly installing random AppX files can make the package state harder to diagnose.

Fix 3: Install or repair the correct Visual C++ Redistributable

This step is most directly relevant when the message names VCOMP140.DLL without _app, or when the traditional desktop application bundles or expects the ordinary Visual C++ runtime.

Use Microsoft’s latest supported Visual C++ Redistributable downloads.

The official packages are:

• Microsoft vc_redist.x86.exe for 32-bit applications
• Microsoft vc_redist.x64.exe for 64-bit applications
• Microsoft vc_redist.arm64.exe for ARM64 applications

A 64-bit Windows installation can run 32-bit software. Therefore, the operating system’s architecture does not by itself determine which package the application needs.

Install the package matching the application, not merely the computer. If you regularly run both 32-bit and 64-bit games or utilities, installing both x86 and x64 can be appropriate. Do not uninstall an older runtime just because a newer one is present.

Repair the redistributable

After downloading the correct installer:

1. Close the affected application and its launcher.
2. Right-click the downloaded installer.
3. Choose Run as administrator.
4. Select Repair if the installer offers it.
5. Allow the repair to complete.
6. Restart Windows.
7. Launch the application again.

The installer also supports a repair command. From an elevated Command Prompt in the folder containing the installer, use the architecture that matches the package:

vc_redist.x64.exe /repair /passive /norestart

For a 32-bit package:

vc_redist.x86.exe /repair /passive /norestart

Microsoft documents these installer switches and deployment behavior in its guide to redistributing Visual C++ files.

If the installer reports that the operation failed, uninstalling and reinstalling the same redistributable can help, but record the current installed programs first. Do not remove every Visual C++ entry as a general cleanup step.

How to tell whether the package was the problem

The repair was relevant if:

• the error changed from missing VCOMP140.DLL to a different dependency;
• the program starts normally;
• the installer reported a successful repair and the same desktop application now launches.

If the exact error remains vcomp140_app.dll, return to the application and VCLibs fixes. The desktop redistributable may not be the package that owns the _app file.

Fix 4: Check Microsoft Defender Protection History

Antivirus software can quarantine a runtime file after an interrupted installation, a false positive, or detection of a tampered application directory.

1. Open Start.
2. Search for Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review entries created around the time the application stopped launching.
7. Open any entry associated with the affected application or DLL.

Do not restore a quarantined DLL solely because its filename looks like a Microsoft runtime. A malicious program can use the same filename.

Restore or allow the item only when all of the following are true:

• the application came from a trusted official source;
• the file is located in the expected application or framework directory;
• the application publisher confirms the detection is a false positive;
• a fresh reinstall or launcher verification does not provide a clean replacement.

Microsoft explains the risks of restoring quarantined files in its documentation for Protection History.

The safer default is to remove the damaged installation and reinstall it from the official Store, publisher, or game launcher. If Defender repeatedly removes the same file after a clean reinstall, scan the system and contact the application publisher rather than repeatedly allowing the file.

Fix 5: Install pending Windows updates

A Store framework or package deployment problem can follow an incomplete Windows update or an application update.

On Windows 11:

1. Open Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart when prompted.
6. Return to Windows Update.
7. Check again until no additional standard updates are offered.

On Windows 10, open:

Settings > Update & Security > Windows Update > Check for updates

Then restart and test the application.

If the failure began immediately after a specific Windows update, first try repairing or reinstalling the affected application and installing any newer updates. Removing an update should be a later step because it changes system servicing state.

To review recent updates:

1. Open Settings.
2. Select Windows Update.
3. Select Update history.
4. Review the installation dates.
5. Choose Uninstall updates.
6. Select the update that clearly matches the beginning of the problem.
7. Choose Uninstall and follow the prompts.

Microsoft documents this process in its instructions for uninstalling a Windows update.

Do not remove an update merely because it is recent. The timing should be clear, and application repair should have failed first.

Fix 6: Repair Windows components with DISM and SFC

Use Windows repair tools when several Store applications fail, Windows components are malfunctioning, or the problem is part of broader system corruption. They are secondary fixes for a missing game-local DLL.

Run DISM first, then System File Checker.

1. Open Start.
2. Search for Command Prompt.
3. Right-click it.
4. Choose Run as administrator.
5. Select Yes at the User Account Control prompt.
6. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish.
2. Then run:

sfc /scannow

1. Wait until the verification reaches 100 percent.
2. Restart Windows.
3. Test the affected application.

Microsoft documents DISM in its guide to repairing a Windows image and SFC in its System File Checker documentation.

Possible SFC results include:

• Windows found no integrity violations: protected system files were not the problem.
• Windows found corrupt files and successfully repaired them: restart and test again.
• Windows found corrupt files but was unable to fix some: review the CBS log, run DISM again if necessary, and consider an in-place Windows repair.
• Windows Resource Protection could not perform the requested operation: restart and run the scan again, or use Safe Mode for further troubleshooting.

SFC and DISM will not necessarily recreate a deleted game-local DLL or reinstall a missing Store framework package. If the application alone is affected, return to its installer or launcher.

Repeatedly running SFC and DISM without knowing what changed can be tedious. Outbyte PC Repair can scan for issues and show what it finds, while repair is handled by the full version; it is optional, and reinstalling the program remains the definitive fix when that program owns the DLL.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 7: Check drivers only when the timing points to a driver problem

A graphics or chipset driver does not normally supply vcomp140_app.dll, so driver replacement is not a first-line DLL repair. It becomes relevant if the failure started after a graphics driver installation, the application also crashes with display errors, or several games began failing together.

Use Windows Update first

1. Open Settings.
2. Select Windows Update.
3. Open Advanced options.
4. Select Optional updates.
5. Expand Driver updates if available.
6. Select the appropriate driver.
7. Choose Download and install.
8. Restart Windows.

Check Device Manager

1. Press Win+X.
2. Select Device Manager.
3. Expand Display adapters for a graphics driver, or the relevant hardware category.
4. Right-click the device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if a driver was installed.

If the problem began immediately after a driver update:

1. Open Device Manager.
2. Expand the affected device category.
3. Right-click the device.
4. Choose Properties.
5. Open the Driver tab.
6. Select Roll Back Driver if Windows makes that option available.
7. Restart and test the application.

Do not uninstall a graphics driver merely because a DLL error appears. First identify whether the driver is connected to the timing and symptoms. A clean reinstall from the hardware manufacturer may be appropriate when Device Manager reports a failed device, but it will not replace a missing application runtime by itself.

Manually comparing hardware driver versions across graphics, chipset, audio, and storage devices can involve hunting through many entries. Outbyte Driver Updater can scan and show which drivers need attention, while installing drivers is handled by the full version; it is optional, and it does not replace repairing the application that owns vcomp140_app.dll.

Windows Features are usually not the fix

vcomp140_app.dll is not restored by enabling a generic Windows Features checkbox.

To inspect Windows Features:

1. Press Win+R.
2. Enter optionalfeatures.exe.
3. Press Enter.
4. Review the available features.

There is no general “Visual C++ Runtime” feature in this window. Do not enable random features in the hope of restoring the DLL.

Features such as .NET Framework or Legacy Components can matter when an application explicitly reports that it needs them, but they do not replace VCLibs or the Visual C++ Redistributable. DirectX, .NET, and graphics-driver repairs are not first-line fixes unless the application identifies those components as separate missing dependencies.

Do not use regsvr32 for this DLL

regsvr32 is for registering certain COM and ActiveX DLLs that expose a registration entry point such as DllRegisterServer. A Visual C++ runtime library is not normally repaired by registering it.

Microsoft explains the limitations and error conditions of Regsvr32.

Running commands such as these is not an appropriate repair:

regsvr32 vcomp140_app.dll
regsvr32 VCOMP140.DLL

They can produce a registration error without fixing the missing dependency. If you already ran regsvr32, the error itself does not usually damage the runtime. Continue with application repair, VCLibs repair, or the matching redistributable.

Do not copy the DLL into System32 or SysWOW64

Manual copying fails for several reasons:

• the replacement may be the wrong architecture;
• the version may not match the application;
• the program may require additional runtime files;
• package registration may still be broken;
• Windows servicing can later replace or ignore the manually copied file;
• a downloaded DLL may be modified or malicious.

The correct location may be an application directory, a packaged framework directory, or a publisher-managed runtime location. The Windows loader searches locations according to the application and package deployment rules. Putting a file in a system directory can hide the real ownership problem and create failures for other programs.

Microsoft’s guidance on redistributing Visual C++ files favors deploying the supported runtime package rather than distributing an isolated runtime file.

Fix 8: Test another Windows user account

A VCLibs framework can exist on disk but fail to register correctly for one user profile.

To test this:

1. Open Settings.
2. Select Accounts.
3. Select Other users.
4. Choose Add account.
5. Create a temporary local user if necessary.
6. Sign out of the current account.
7. Sign in to the test account.
8. Launch the affected application.

If the application works in the second account, the problem may be per-user package registration or profile corruption rather than a missing DLL. Copy important personal data before changing profiles. Avoid taking ownership of WindowsApps or applying broad permission changes.

There is no single universal registration command that safely repairs every affected Store application. Repairing or reinstalling the specific application is the safer path.

Fix 9: Use System Restore when the timing is clear

System Restore can help when the application worked before a recent driver, program, or Windows change and other repairs have failed. It affects system files, registry settings, and installed programs, but not personal documents.

1. Press Win+R.
2. Enter rstrui.exe.
3. Press Enter.
4. Select Next.
5. Choose a restore point dated before the failure began.
6. Select Scan for affected programs if available.
7. Review the changes.
8. Select Finish.
9. Allow Windows to restart and complete the restoration.

Microsoft describes this process in its System Restore documentation.

System Restore does not guarantee that a game-local DLL will be recovered, and it may remove an application installed after the selected restore point. Use it when the cause is tied clearly to a recent system change, not as the first response to an isolated application failure.

What the error can reveal about the root cause

The surrounding circumstances often point to the correct repair:

What happened before the error	Likely direction
A Store app updated and stopped launching	Repair or reset the app, update the Store, check VCLibs
A game installation was interrupted	Verify or reinstall the game
Defender detected a file	Inspect Protection History, then reinstall from the official source
Only one traditional program fails	Repair that program and its matching VC++ architecture
Many Store apps fail	Windows Update, VCLibs deployment, DISM, and SFC
The error began after a driver update	Test driver rollback or a clean driver repair
The error appears only for one Windows account	Check per-user package registration or profile damage
The file is in a temporary or unrelated folder	Investigate the executable and scan for unwanted software

This is practical troubleshooting guidance rather than a measured statistical ranking. The filename alone cannot prove which cause applies.

Frequently asked questions

Is vcomp140_app.dll a Windows system file?

It is a Microsoft Visual C++ runtime file, but it is not normally a core DLL that you should manually restore to System32 or SysWOW64. It is commonly deployed through a VCLibs framework or bundled with the application that needs it.

Is it part of Visual Studio?

The runtime is produced from Microsoft’s Visual C++ toolchain, but most users do not need to install Visual Studio. They need the application’s packaged dependency or the supported Visual C++ Redistributable appropriate for the application.

Is it part of the Microsoft Store?

The _app variant is strongly associated with packaged applications and the Microsoft.VCLibs.140.00 framework. A Store application normally installs its framework dependencies automatically. A third-party game can also bundle an app-local copy.

Should I install both x86 and x64 redistributables?

Install the architecture required by the application. A 32-bit application needs x86, and a 64-bit application needs x64. Because 64-bit Windows runs both types of software, installing both official packages can be appropriate when you use applications of both architectures.

Will the normal x64 Visual C++ Redistributable fix this exact error?

It can fix a traditional desktop program that needs the ordinary VCOMP140.DLL runtime, and some application installers use the desktop runtime. It is not a universal substitute for the VCLibs framework expected by every packaged application. If the error specifically names vcomp140_app.dll, repair the owning application first.

Can I download just the DLL?

Do not use random DLL download sites. The file may be unsafe, incompatible, or the wrong architecture, and copying it may not repair the application package. Use the official application installer, Microsoft Store, publisher launcher, VCLibs dependency, or Microsoft Visual C++ Redistributable.

Does regsvr32 fix it?

No. Runtime DLLs of this type are not normally registered with regsvr32. Repair the application or deploy the correct runtime package instead.

Why does the error say “not designed to run on Windows”?

That wording can indicate a corrupted file, architecture mismatch, incompatible replacement, or a damaged application installation. It does not automatically prove malware. Check the file’s location, verify the application, inspect Defender Protection History, and reinstall from a trusted source.

Does SFC repair vcomp140_app.dll?

SFC repairs protected Windows system files. It may help when Windows components are broadly corrupted, but it will not necessarily recreate a deleted game-local file or reinstall a missing VCLibs framework. Use it after repairing the affected application when broader Windows problems are present.

What should I give the publisher if nothing works?

Collect:

• the exact application or game name;
• the complete error text;
• whether the filename is vcomp140_app.dll or VCOMP140.DLL;
• the executable path;
• the package name and version if it is a Store or MSIX application;
• the application architecture;
• the installation source;
• the Reliability Monitor or Event Viewer entry;
• any Defender Protection History event;
• whether Repair, Reset, verification, reinstall, and runtime repair changed the error.

That information tells the publisher whether it needs to redeploy an app-local file, repair a package dependency, correct an architecture mismatch, or update its installer.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.