Fixing the VCRUNTIME140.dll error in Windows

The “VCRUNTIME140.dll is missing” message usually appears when Windows cannot find a Microsoft Visual C++ runtime file required by an application. It may prevent a program from starting, display an error such as “The code execution cannot proceed,” or appear after installing software, a game, or a Windows update.

VCRUNTIME140.dll is part of the Microsoft Visual C++ Redistributable package. It is not normally a file that should be downloaded separately from a random website. A missing, damaged, or incompatible runtime installation is the more common cause, although malware, accidental deletion, and system corruption can also be involved.

The problem can occur on Windows 10 and Windows 11 computers, including systems used for work, study, gaming, and home administration. Whether you are in Sydney, Melbourne, Perth, or a regional Australian town with a slower internet connection, the safest fix is to restore the official runtime and check the wider health of Windows.

Check which program is causing the error

Read the error window carefully and note the name of the application that fails. The issue may affect only one program rather than Windows as a whole. If the message appears when opening a game, video editor, accounting application, or business tool, that software probably depends on the missing runtime library.

Restart the computer before making changes. A reboot can complete a pending Windows installation or release a file that was locked during an update. Try opening the affected application again after Windows loads fully. If the same message returns, avoid repeatedly reinstalling the application until the Visual C++ components have been checked.

Confirm that the program came from a trusted source. A modified installer or unofficial software package may contain damaged files or unwanted programs. If the error appeared alongside browser redirects, unusual pop-ups, very slow performance, or unfamiliar applications, run a malware scan before repairing system files. Movian Security’s Windows troubleshooting approach treats DLL errors as possible symptoms of a broader computer problem rather than isolated messages.

Install the official Visual C++ package

The most reliable solution is to install or repair the Microsoft Visual C++ Redistributable for Visual Studio 2015–2022. Download it from Microsoft’s official website rather than a third-party DLL library. Search for the Microsoft Visual C++ Redistributable latest supported downloads page and choose the correct installer.

Most modern Windows computers use 64-bit Windows, but a 64-bit system can still run 32-bit applications. For that reason, install both the x64 and x86 packages when appropriate. The x64 package supports 64-bit programs, while x86 supports 32-bit applications. If you are unsure which architecture you need, checking Windows Settings under System and About can help.

Run each installer as an administrator and accept the licence terms. If the installer offers a Repair option, select it first. If it reports that the package is not installed, choose Install. Restart Windows when the process finishes, then test the affected program. This repair restores VCRUNTIME140.dll through the supported Microsoft installation instead of copying an unknown file into a system folder.

Repair or reinstall the affected application

If the runtime installation completes but the application still will not open, repair the program itself. Open Settings, go to Apps, select Installed apps, choose the affected software, and look for Advanced options. Some applications provide Repair and Reset commands. Use Repair first because Reset may remove preferences, local data, or saved settings.

Desktop programs may instead include their own repair tool in Control Panel under Programs and Features. Select the application, choose Change, and follow the repair wizard. If no repair option exists, uninstall the program, restart Windows, and reinstall it using a current installer from the developer’s official website.

Check the application’s system requirements before reinstalling. An older program may require a particular Visual C++ version, DirectX component, .NET runtime, or a 32-bit installation. Compatibility Mode can sometimes help with legacy software, but it should not replace security updates. On a shared family PC or a small business computer in Brisbane or Adelaide, record important licence details and back up application data before removing the software.

Use Windows tools to repair damaged files

Windows includes System File Checker, which can replace corrupted protected system files. Open the Start menu, type Command Prompt, right-click it, and select Run as administrator. Enter the following command:

sfc /scannow

Allow the scan to reach 100 percent. It may report that it repaired files, found no integrity violations, or could not fix everything. Do not close the Command Prompt window while the scan is running. Restart the computer after it finishes and try the application again.

If System File Checker cannot complete its repair, use the Deployment Image Servicing and Management tool first:

DISM /Online /Cleanup-Image /RestoreHealth

This command checks the Windows component store and may need an active internet connection to obtain replacement files. After DISM finishes, run sfc /scannow again. These tools are useful when a failed update, power interruption, or disk problem has damaged Windows components. If an Australian home connection has limited data or drops out frequently, allow extra time for the process and avoid interrupting the computer.

Check updates, security, and system changes

Open Windows Update and install pending security and quality updates. Microsoft sometimes distributes runtime fixes or compatibility improvements through normal Windows servicing. Restart whenever Windows requests it, then check whether the error has disappeared. Also update the affected application and, where relevant, graphics or chipset drivers from the computer or hardware manufacturer.

Run a scan with Windows Security. Choose Virus & threat protection, update the security intelligence, and perform a Quick scan. If suspicious activity or repeated file deletion is present, use a Full scan or Microsoft Defender Offline scan. Malware can damage or replace DLL files, so downloading a replacement from an unknown website can make the situation worse.

Think about what changed immediately before the error appeared. A newly installed cleaner, registry optimiser, driver package, or “free” utility may have removed shared runtime files. System Restore can reverse certain recent software changes if restore points are available. It does not normally affect personal documents, but applications and drivers installed after the selected restore point may be removed.

Avoid unsafe DLL downloads and know when to seek help

Do not copy VCRUNTIME140.dll from another computer or download an individual DLL from an unfamiliar website. The file may be the wrong version, may not match the application architecture, or may contain malicious code. Placing it in System32 or the application folder can also create additional errors and make future repairs harder.

If the error persists after installing both official runtime packages, repairing the application, running DISM and SFC, and checking for malware, investigate the storage drive and Windows installation. Repeated DLL corruption can point to failing hardware, insufficient free space, damaged user profiles, or a wider operating system problem. Back up important documents, photos, business records, and Outlook data before more advanced repairs.

Professional assistance can be worthwhile when the computer is used for invoicing, remote work, school records, or essential services. Movian Security can help diagnose Windows file corruption, remove infections, restore missing components, improve slow performance, and arrange data backup before repair work. This is especially practical for users who rely on a computer every day and cannot risk losing files while trying several uncertain fixes.