I recently came across a computer, on which certain programs could not be run and a warning window appeared with the following description: «Application failed to start because MSVBVM60.DLL was not found. Re-installing the application may fix the problem" (zoom in).
The obvious thing was that said file, library (dll) as it is known in computer terms, had been deleted with certainty by a virus. Well then the first action to follow was to perform an analysis of the system, with the antivirus updated of course, after a few minutes several were detected, I proceeded to eliminate them without mercy.
Then I used CCleaner to clean the system, and finally it was time to do the most important thing; reinstall the MSVBVM60.DLL library file.
For this, I visited the paradise of bookstores dll-files and I downloaded it, there I also found precise information on where to install it and how to register it. The route is as follows: C: WINDOWSsystem32 (Windows 7 / Vista / XP), it was just a matter of copying it there. Now, to register it you must go to the menu Start> Run (Win + R) and write: REGSVR32 c: windowssystem32msvbvm60.dll
Finally accept and restart the computer, with that the problem was solved.
To take into account:
MSVBVM60.DLL ó Visual Basic Virtual Machine It is a library file that includes the Windows operating system in all its versions, the location of this library / library may vary depending on the version of Windows: C: WindowsSystem32msvbvm60.dll (Windows 7 / Vista / XP), C: WindowsSystemmsvbvm60.dll (Windows Me / 98/95), C: WINNTSystem32msvbvm60.dll (Windows 2000 / NT).
When it is removed (manually or by virus), it causes problems related to the following warnings:
- “Does not find the file/file msvbvm60.dll” – “dll file not found”
- “Explorer has caused an error in msvbvm60.dll”
- “File msvbvm60.dll is missing” – “Can't find file msvbvm60.dll”
- “The entry point or module for msvbvm60.dll is not found”
- “Error loading file msvbvm60.dll”
- “Call to undefined dynalink” – “Call to undefined dynalink”
- "Run dll error"
There are times when it is not necessary to register the library, since it is enough to just copy it, likewise there are circumstances in which said file is already in that case it is necessary to enter Windows in «Safe Mode» (F8 after loading the BIOS), delete the file MSVBVM60.DLL and replace it with the one we downloaded. There are also exceptional cases, in which it is required to copy the library in the main folder of the application that gives the error.
Link: Download MSVBVM60.DLL
(More info: joy)
Thank you very much for your participation dear friend, it is fortunate that this type of problem has never happened to you, we hope it never happens to you. Although from today you will know how to solve it ... that is one of the purposes of this post.
Best regards colleague 🙂
Very good article to fix that problem.
I have never been missing any .dll, so much to fix I do not know lol. Greetings and thanks for the information.
It is a generic solution not only for the Visual Basic 6 DLL that you mention in the article, since any DLL or OCX that is missing in the system can be registered.
Good article.
@Fitoschido: You are absolutely right dear friend, because it happens that I wrote it in the way of an experience that had happened to me recently, specifically with that problem.
In addition, this post helps to position me on the first page of Google, you will understand 🙂
Greetings Fitoschido, thank you very much for your participation ...
How good it is to see you here again!