VCRUNTIME140.dll / MSVCP140.dll not found
The game needs the Microsoft Visual C++ 2015–2022 runtime.
Install both x64 and x86 versions from the Redistributables page.
Troubleshooting index
Find the message. Check the likely cause. Try the sensible fix.
The game needs the Microsoft Visual C++ 2015–2022 runtime.
Install both x64 and x86 versions from the Redistributables page.
The game needs the Visual C++ 2012 runtime.
Install the official Visual C++ 2012 Redistributable.
The game needs the Visual C++ 2010 runtime.
Use Microsoft’s official Visual C++ download guidance to locate the legacy package.
A legacy DirectX component is missing. Windows does not include every older optional DirectX library by default.
Install the DirectX End-User Runtime linked on the Redistributables page.
The game depends on a legacy DirectX controller component.
Install the DirectX End-User Runtime from Redistributables.
This component is normally supplied by supported versions of Windows. The system files may be damaged or the game may be running in an unusual environment.
Run Windows Update and check system files. Do not download individual DLL files from third-party DLL sites.
The game uses the OpenAL audio library.
Check the game’s included prerequisites or install OpenAL from the Redistributables page.
The game needs a legacy XAudio component associated with older DirectX packages.
Install the DirectX End-User Runtime from Redistributables.
The Universal C Runtime or a required Visual C++ runtime component may be missing or damaged.
Run Windows Update, then install the appropriate Visual C++ Redistributable from Redistributables.
The game requires the Visual C++ 2013 runtime.
Install the official Microsoft Visual C++ Redistributable for the required version.
Often caused by a 32-bit/64-bit mismatch, damaged runtime files, or an incompatible DLL.
Install the required x86 and x64 runtimes from Redistributables, update Windows, and avoid copying random DLLs into the game folder.
A missing prerequisite, unsupported hardware/OS, permissions issue, or conflicting overlay may be responsible.
Check the game’s requirements and included notes, temporarily disable overlays, and review Windows Event Viewer for the crash details.
Possible display mode, driver, resolution, overlay, or shader-cache issue.
Try Alt+Enter, update your GPU driver, disable overlays, and check the game’s configuration options.
The game may be loading an incompatible or outdated library.
Repair or reinstall the relevant official runtime and verify the game files. Do not replace system DLLs manually.
Windows permissions or security software may be blocking access to the game or its files.
Install or move the game to a normal writable folder such as C:\Games, check folder permissions, and review your security software’s protection history.
Windows cannot establish enough reputation information for the app, or the publisher is unverified.
Only continue if you trust the source and have verified the download. Scan the files and check the publisher before running anything. Do not disable SmartScreen globally.
A required Visual C++ runtime or application manifest may be missing or damaged.
Install or repair the runtime specified by the game. Windows Event Viewer may identify the exact missing assembly.
The executable may target a different Windows architecture, be damaged, or be blocked by system policy.
Check system requirements, re-download from a trusted source, and confirm that the executable matches your Windows version.
A runtime, Windows feature, or game file may be missing.
Read the complete error text, install only the named prerequisite from Redistributables, and verify the game files.
Often related to corrupted archives, memory instability, insufficient temporary space, or security software interference.
Check the installer’s integrity, free disk space, restore any files only if you trust the source, and test system memory if errors persist. The DLL name itself is not usually the fix.
The downloaded or extracted data does not match its expected checksum.
Re-check the download and archive parts, ensure all parts are present, and download a fresh copy from a trusted source if needed.
Installation needs room for both the final game and temporary extraction files.
Free space on the target drive and the Windows temporary drive. Leave additional headroom beyond the game’s listed size.
The installer may be unpacking a large file, waiting on disk I/O, or blocked by another process.
Check Task Manager for CPU and disk activity, wait if work is continuing, and confirm that the drive has free space and no hardware errors.
One or more archive parts may be missing or truncated.
Confirm every part is present and named correctly, then verify or re-download the incomplete part.
The target folder may be read-only, protected, or on a drive with filesystem errors.
Choose a writable folder, check available space and permissions, and scan the drive if write errors continue.
The installer cannot write to the selected path or temporary directory.
Use a writable installation directory, check Windows Security history, and run the installer with elevated permissions only when you trust its source.
Modern games may compile shaders or build caches during the first session.
Allow the first run to finish and check whether later sessions improve. If not, update drivers and check CPU, memory, and disk usage.
The game may use integrated graphics, a restrictive power mode, high settings, or be limited by CPU performance.
Select the high-performance GPU in Windows Graphics settings, update drivers, and check temperatures and per-process usage.
A GPU driver reset, unstable overclock, overheating, or game/driver bug may be involved.
Return GPU/CPU tuning to stock, update or clean-install the GPU driver, check temperatures, and lower graphics settings for testing.
Driver issues, audio enhancements, device format mismatch, or high system load can cause glitches.
Update audio drivers, disable audio enhancements, and test a standard 44.1 kHz or 48 kHz format in Windows sound settings.
A slow or failing drive, limited memory, shader compilation, or background activity may be responsible.
Check drive health and Task Manager, close unnecessary background tasks, and move the game to an SSD if practical.
The game may exceed available VRAM/RAM or use settings beyond the system’s capacity.
Lower texture quality and resolution, close other applications, and confirm the GPU meets the game’s requirements.
Windows or the driver selected the power-saving graphics processor.
Open Windows Settings → System → Display → Graphics, select the game executable, and choose the high-performance GPU.
The game may require a specific Windows version or an older compatibility component.
Check the game’s minimum OS requirements, install Windows updates, and try the Compatibility troubleshooter for older titles.
Some older games depend on the optional legacy DirectPlay Windows component.
Open “Turn Windows features on or off” and check Legacy Components → DirectPlay if the game specifically requires it.
The game or its configuration may be trying to write into a protected directory.
Move it to a writable folder and check Properties → Compatibility for an unnecessary “Run this program as administrator” setting.
The game cannot write to its save directory, or Windows security controls are blocking it.
Check the game’s save location, folder permissions, available disk space, and Controlled folder access notifications.
The game retained an old display configuration or does not handle multi-monitor layouts well.
Try Windows+Shift+Arrow to move the window, use Alt+Enter, and reset the game’s display settings if needed.
The title may rely on an online service, launcher, or account entitlement.
Install the official launcher, sign in with the account that owns the game, and check the publisher’s service status and support notes.
The anti-cheat service may be missing, damaged, disabled, or incompatible with the current system.
Use the game’s official repair option, verify files through the supported launcher, and follow the publisher’s anti-cheat troubleshooting guide.
The update may have changed files, settings, drivers, or compatibility requirements.
Verify or repair the installation, reset custom mods temporarily, update drivers, and check the publisher’s patch notes.
Security software detected a file as suspicious; false positives are possible, but malware is also possible.
Do not blindly disable protection. Check the detection name, verify the file’s source and signature, and restore it only when you can establish that it is safe.
The service may require an account, supported game version, network access, or anti-cheat support.
Check the game’s official online requirements, service status, firewall permissions, and whether the current version supports multiplayer.
RPCS3 requires official PS3 system software to provide system modules.
Download the PS3 system software from PlayStation’s official site and install it through RPCS3’s File menu.
Compatibility varies by game, build, and configuration.
Check the RPCS3 compatibility list and the game-specific wiki notes.
Renderer settings or game-specific workarounds may be required.
Start with the game’s recommended RPCS3 settings and test Vulkan/OpenGL or native resolution only when the game’s wiki suggests it.
The selected input handler or controller mapping may be incorrect.
Open RPCS3 pad settings, select the correct handler, and test the controller mapping before launching the game.
PCSX2 requires PS2 system firmware to boot games.
Dump the BIOS from your own PS2 console and follow the PCSX2 documentation to configure it.
The BIOS, game image, or emulator configuration may be incorrect.
Confirm the BIOS is configured, verify the game image, and check the game’s compatibility notes.
Some games use rendering techniques that do not work correctly with every hardware renderer.
Check the game-specific PCSX2 wiki entry and test the recommended renderer or settings.
The controller may not be mapped to the active input profile.
Open PCSX2 controller settings, select the correct device, and bind the buttons again.
Xbox 360 compatibility varies widely, and some titles need specific settings or are not playable.
Check the Xenia compatibility tracker and use the emulator’s current documentation.
Some games or features require system files that are not included with the emulator.
Read the Dolphin documentation and provide files dumped from your own console when required.
CPU/GPU limitations, backend selection, shader compilation, or inaccurate settings can reduce performance.
Check the emulator’s recommended settings for the game, update drivers, and close other CPU/GPU-heavy applications.
The selected input backend or controller profile may be wrong.
Select the appropriate input device in the emulator settings and test button mappings before starting the game.
A general PS4 application crash code; causes can include damaged data, software issues, or a game-specific bug.
Restart the console, update the game and system software where appropriate, and check the game’s official troubleshooting guidance. Back up important saves before rebuilding databases or reinstalling.
The package may be incomplete, incompatible, or intended for a different system setup.
Check the file integrity, available storage, package compatibility, and the documentation for your specific console environment.
The content may not be licensed for the current account, may require a different system version, or may not match the installed game version.
Confirm the account entitlement, region, game version, and system requirements. For purchased content, restore licenses through the console settings.
Damaged game data, an incompatible update, storage trouble, or a game-specific issue may be responsible.
Check the game’s compatibility notes, verify the package source, and reinstall or update through a supported method if necessary.
The download may be incomplete, storage may be failing, or there may not be enough free space.
Check free space, verify the download, test another known-good storage device, and check the drive for errors.
Account, game-version, storage, or system-software differences may affect saves and trophies.
Back up saves, confirm the correct user profile and game version, and consult official support before using save-management tools.
No matching errors. Try a DLL name, error code, or broader keyword.