Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →msvbvm60.dll errors commonly appear as “This application has failed to start because MSVBVM60.DLL was not found” or “The program can’t start because msvbvm60.dll is missing from your computer.” The file is the 32-bit Microsoft Visual Basic 6.0 runtime used by older Windows programs and games.
Do not start by downloading a standalone copy from a DLL website. First determine whether one application is broken, several applications are affected, or Windows has quarantined or damaged the runtime.
Which fix applies to you
Use this quick decision list before changing anything:
- Only one application or game fails: Repair, verify, or reinstall that application from its official installer or launcher.
- Several old applications fail: Repair Windows with DISM and SFC, then restart.
- The file was quarantined: Check Windows Security Protection History and verify the application source before restoring or reinstalling anything.
- The installer specifically asks for the VB6 runtime: Use the original application installer or a legitimate Microsoft-distributed Visual Basic 6.0 runtime package.
- The error names an OCX file: This is a separate ActiveX component problem, not necessarily an
msvbvm60.dllproblem. - The file exists but the error remains: The application may be loading another missing dependency, using an invalid local copy, or encountering an architecture mismatch.
- Many unrelated programs show DLL or “Bad Image” errors: Repair Windows components and investigate recent system changes.
What msvbvm60.dll is
msvbvm60.dll is the Visual Basic Virtual Machine, the core execution runtime for compiled Visual Basic 6 applications. Microsoft identifies the VB6 runtime as supported on current supported Windows versions, including Windows 10 and Windows 11.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
VB6 applications remain 32-bit. On 64-bit Windows, they run through WOW64, the compatibility environment that allows 32-bit applications to run. This is why installing a 64-bit runtime or copying a file into a location chosen at random does not solve the problem.
The file is genuine Microsoft software, but an error involving it does not automatically mean that Windows itself is missing the file. An application can report a DLL as missing when another dependency cannot load, when the application is using an invalid private copy, or when the file is the wrong architecture.
Microsoft documentation also states that a compiled Visual Basic application requires Msvbvm60.dll on the client computer. It is not the Visual C++ Redistributable, DirectX, .NET Framework, a device driver, or a native 64-bit DLL.
Fix 1: Repair or reinstall the affected application
This is the most likely fix when only one old program or game refuses to start.
Application installers may deploy more than the core VB6 runtime. They can also install application-specific OCX controls, configuration files, licenses, registry entries, and other dependencies. Reinstalling the runtime alone does not replace those files.
For a normal desktop application
- Close the affected application.
- Open Settings.
- Select Apps.
- Choose Installed apps on Windows 11, or Apps & features on Windows 10.
- Find the affected program.
- Select the three-dot menu on Windows 11, or select the program on Windows 10.
- Choose Repair if that option is available.
- Start the application again.
If Repair is unavailable or does not help:
- Return to the application’s entry in Installed apps or Apps & features.
- Select Uninstall.
- Restart Windows.
- Download or run the installer supplied by the application’s official vendor.
- Right-click the installer and choose Run as administrator if the vendor’s instructions require elevated installation.
- Start the application after setup finishes.
If the program was installed from physical media, use the original media rather than a random executable found online. If it is a business or legacy application, contact the vendor for a current installer or supported deployment package.
For a Steam game
Use Steam’s file verification feature instead of manually replacing files:
- Open Steam.
- Select Library.
- Right-click the game.
- Choose Properties.
- Select Installed Files.
- Choose Verify integrity of game files.
- Wait for the process to finish.
- Launch the game again.
If verification does not repair the error, uninstall and reinstall the game through its official launcher. A game may need additional files beyond msvbvm60.dll.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →How to tell whether this worked
The repair succeeded if the application opens without the missing-DLL message. If the next error names another file, record it exactly. That new filename may identify a missing ActiveX control or another application-specific dependency.
If other VB6 programs already work, do not replace the working Windows runtime merely because one application fails. Continue with the application’s own repair or reinstall process.
Fix 2: Repair Windows with DISM and SFC
Use this fix when several older applications fail, the expected runtime is missing from Windows, or the error began after a system problem. DISM repairs the Windows component store, while System File Checker checks and repairs protected Windows files.
Run DISM first, followed by SFC.
- Right-click Start.
- Select Terminal (Admin) on Windows 11, or Windows PowerShell (Admin) or Command Prompt (Admin) where available on Windows 10.
- Select Yes if User Account Control asks for permission.
- Enter this command and press Enter:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for DISM to finish. Do not close the window while it is working.
- Run:
sfc /scannow
- Wait until verification reaches 100 percent.
- Restart Windows.
- Test the affected application again.
If SFC reports that it found and repaired corrupt files, restart and test the program. If it reports that it could not repair some files, run DISM again, restart, and then run sfc /scannow once more.
Recommended Free Tools
These commands repair Windows components. They do not guarantee that an application’s private copy, OCX controls, configuration, or licensing files will be restored. If only one program remains affected, return to that program’s official repair or reinstall process.
Manually hunting through Windows folders and repeating SFC or DISM without knowing what changed can make troubleshooting difficult. Outbyte PC Repair can scan for problems and show what it identifies; repairs are performed by the full version, and it is not required for this fix.
Fix 3: Check Windows Security quarantine
Antivirus software may quarantine a runtime file after detecting a problem with the application, installer, or file. The missing-DLL message alone does not prove that the file was a false positive.
To inspect Windows Security:
- Open Start.
- Type Windows Security.
- Open the application.
- Select Virus & threat protection.
- Select Protection history.
- Review recent detections and quarantined items.
- Expand an entry to view its name, location, and action.
Before restoring anything, confirm that:
- The affected application came from a trustworthy vendor.
- The installer was obtained from the vendor or original distribution channel.
- A current security scan does not identify the application as malicious.
- The quarantined file belongs to the expected application or Windows location.
Microsoft warns that restoring or allowing a quarantined file can put the device at risk. Do not permanently disable antivirus protection simply to copy a DLL.
Rank #2
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
If the file is confirmed to have been removed from a trusted application, reinstall that application instead of restoring an unexplained file from quarantine. If security software identifies malware, follow the security product’s cleanup instructions first.
Fix 4: Install the correct Visual Basic runtime package when required
Some older application installers explicitly require the Visual Basic 6.0 runtime. In that situation, use the original application installer or a Microsoft-distributed runtime package rather than an isolated DLL.
The historical Microsoft package was called the Visual Basic 6.0 SP6 Run-Time Redistribution Pack. Its installer was named VB6.0-KB290887-X86.exe and contained vbrun60sp6.exe. Microsoft’s original Download Center page is archived rather than being a current direct download page.
Microsoft pages for later VB6 security updates and extended runtime files are not general replacements for the base runtime installer. Do not install the Visual Basic 6 development IDE solely to obtain msvbvm60.dll. The IDE is obsolete, while the runtime is supported for the lifetime of supported Windows versions.
Free tools Windows power users keep installed
One-click scans. No signup required.
If you use a legacy package, verify that it came through a trustworthy Microsoft-distributed source and that the affected application actually requires it. After installation:
- Restart Windows.
- Start the application.
- Record any new error message exactly.
If installation reports that the runtime is already present but the application still fails, continue with application repair, DISM and SFC, or dependency diagnosis. Do not keep installing unrelated redistributables.
Fix 5: Understand System32 and SysWOW64
The folder names are confusing on 64-bit Windows:
C:WindowsSystem32is associated with the native 64-bit system environment.C:WindowsSysWOW64is commonly associated with 32-bit components running under WOW64.- On 32-bit Windows, the corresponding system directory is normally
C:WindowsSystem32.
Because VB6 applications are 32-bit, a 32-bit application on 64-bit Windows normally uses the WOW64 environment. Do not copy files between these folders just because a website gives a universal folder instruction.
A file’s presence in a folder does not prove that it is valid, compatible, or the dependency that is failing. Windows can also redirect file and registry access for 32-bit applications, so manually browsing to a folder is not a complete test of how the application loads its dependencies.
Fix 6: Separate msvbvm60.dll from missing OCX controls
VB6 applications often use additional ActiveX controls. These are separate from the core runtime.
Examples include:
COMDLG32.OCXMSCOMCTL.OCXMSSTDFMT.DLL
If the next error names one of these files, do not assume that reinstalling msvbvm60.dll will fix it. Obtain the component from the application vendor or the appropriate Microsoft-supported package, then follow the vendor’s installation instructions.
An OCX error may say that the control is missing or not correctly registered. That is different from a core runtime error.
When regsvr32 is appropriate
regsvr32 is a registration tool for DLLs or ActiveX controls that implement the required registration entry point, such as DllRegisterServer. It is not a universal repair command.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Do not run this against msvbvm60.dll merely because a troubleshooting page recommends registering every DLL:
regsvr32 msvbvm60.dll
That is normally not the appropriate fix for the VB6 runtime.
If the application vendor specifically instructs you to register an OCX, use the correct 32-bit regsvr32 from an elevated Command Prompt on 64-bit Windows:
Rank #3
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
C:WindowsSysWOW64regsvr32.exe "C:PathToComponent.ocx"
On 32-bit Windows, use:
C:WindowsSystem32regsvr32.exe "C:PathToComponent.ocx"
Replace the example path with the actual path supplied by the vendor. If registration reports that the entry point is missing, the file may not be a self-registering component, or the wrong architecture may have been used. Do not force registration of the core runtime.
Fix 7: Investigate drivers only when diagnostics point to them
A driver reinstall is not a normal fix for msvbvm60.dll. Consider drivers only if Event Viewer, the application vendor, or a separate device error identifies a driver or hardware problem.
To check Device Manager:
- Right-click Start.
- Select Device Manager.
- Expand the device category related to the reported problem.
- Right-click the device.
- Select Properties.
- Open the General tab and review Device status.
- Open the Driver tab to review the provider, date, and version.
- Use Update driver only when a driver issue is established.
- Restart Windows and retest the application.
Do not install a driver simply because it is old or because a DLL guide recommends it. Outbyte Driver Updater can scan and identify driver versions, which may reduce the work of checking many devices manually; the full version performs driver installation, and it is not needed for an ordinary msvbvm60.dll error.
Why the file can exist but still be reported as missing
Windows applications load dependencies according to the application’s architecture, search paths, and dependency chain. An error that names msvbvm60.dll can still have another cause.
Common possibilities include:
- The application is 32-bit and is looking in a different environment than expected.
- A damaged copy exists in the application’s own folder.
- The file is present but corrupt.
- Another DLL required by the runtime or application is missing.
- The program depends on an OCX control that was never installed.
- The application installer stopped before registering or copying all components.
- Security software removed a secondary file.
- The program itself is incompatible with the current system configuration.
To verify what is actually failing:
- Record the complete error text, including the path and filename.
- Check whether the error names
msvbvm60.dll, an OCX, or another DLL. - Note whether one application or several applications fail.
- Check the application’s installation directory for recently removed or quarantined files.
- Review Event Viewer by right-clicking Start, selecting Event Viewer, and checking Windows Logs and Application around the time of the failure.
- Compare the result after repairing or reinstalling the application.
Do not treat a generic “missing DLL” message as proof that the named file is the only problem.
Do not download a random standalone DLL
Avoid DLL download websites and unofficial file mirrors. A standalone download can contain malware, have the wrong architecture, be the wrong version for the application, or overwrite a valid Windows file without repairing the underlying installation.
Manual copying can be appropriate only when the application vendor explicitly designed the program for private deployment and supplied the verified file. It is not a general Windows repair method. Never overwrite a protected system file with an arbitrary internet download.
The safer sources are:
- The affected application’s official installer or launcher.
- A Microsoft-distributed Visual Basic runtime package where the application requires it.
- Windows component repair through DISM and SFC.
- The application vendor’s documented package for separate OCX controls.
If reinstalling still does not help
When the normal fixes fail, collect evidence before making further changes:
- The exact error text.
- The application name and version.
- The Windows edition and build.
- The full path shown in the error.
- The reported file version, if available.
- Whether the program is 32-bit or 64-bit.
- Whether one application or multiple applications fail.
- Whether Windows Security quarantined a file.
- Any new OCX or secondary DLL named after reinstalling.
- Recent Windows updates, application updates, or system changes.
- Relevant Application errors in Event Viewer.
If the problem affects only one old application, test it with a newly created Windows user account. If it works there, the issue may be limited to the original user profile.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesIf many unrelated programs show “Bad Image” or DLL errors, run DISM and SFC, install pending Windows updates, restart, and check disk health. If the issue began immediately after a system or software change, System Restore may revert system files, registry settings, and installed programs without normally affecting personal files.
FAQ
Is msvbvm60.dll safe?
It is a legitimate Microsoft Visual Basic 6 runtime file. However, a file with the same name from an untrusted download is not automatically safe. Verify its source and scan the application and installer.
Does Windows 10 or Windows 11 include it?
Microsoft supports the VB6 runtime on current supported Windows versions, including Windows 10 and Windows 11. A particular installation can still have corruption, a servicing problem, quarantine activity, or a missing application-local dependency.
Should I install Visual C++, DirectX, or .NET?
No, not for this file by itself. msvbvm60.dll belongs to the Visual Basic 6 runtime. Install another runtime only when the exact application error or vendor documentation identifies that dependency.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchDo I need the 64-bit version?
No native 64-bit VB6 runtime exists for the VB6 application model. VB6 applications are 32-bit and run through WOW64 on 64-bit Windows.
Should I register msvbvm60.dll?
Normally, no. regsvr32 is for self-registering DLLs and ActiveX controls. It is not a general repair command for the Visual Basic runtime.
What if the error changes to COMDLG32.OCX?
That indicates a separate ActiveX control or application dependency. Follow the application vendor’s instructions for that component rather than repeatedly reinstalling msvbvm60.dll.
What is the best first step?
If only one program fails, repair or reinstall that program from its official source. If several VB6 programs fail, run DISM followed by SFC, restart, and test again.
Quick Recap
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.
