Article ID: 823746
Article Last Modified on 2/22/2005
APPLIES TO
- Microsoft Visual Basic 6.0 Learning Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 6.0 Enterprise Edition
SUMMARY
The version of the Msvbvm60.dll file that is included with Microsoft Windows Server 2003 is 6.0.96.90. It is a newer file version than the Msvbvm60.dll file that is included with Microsoft Visual Studio 6.0 Service Pack 5 (SP5). This article contains a link that you can use to download the latest available Microsoft Visual Basic 6.0 runtime. It also lists the article numbers for the bugs that have been fixed since the Visual Studio 6.0 SP6 version of the Msvbvm60.dll file was released.
Note Bug fixes for a particular component are cumulative and contain all the previous fixes for that component. Fixes with a particular version number contain all the fixes that have an earlier version number.
For additional information about the latest Visual Studio service pack, click the following article number to view the article in the Microsoft Knowledge Base:
834001 List of bugs that are fixed in Visual Studio 6.0 Service Pack 6
Note Visual Studio 6.0 Service Pack 6 contains the newest version of Msvbvm60.dll.
MORE INFORMATION
A compressed .cab file that contains a self-extracting executable file is available for download. To download this file, visit the following Microsoft Web site:
This file installs the latest versions of the Visual Basic run-time files. All applications that are created with Visual Basic 6.0 require the latest versions of the Visual Basic run-time files.
VBRun60.exe installs the following core files. These files are included with Microsoft Visual Studio 6.0. These files are the base dependencies for any component or application that is created in Visual Basic 6.0:
| File Name | Version | Size |
| Asycfilt.dll | 2.40.4275.1 | 145KB (147,728 bytes) |
| Comcat.dll | 4.71.1460.1 | 21.7 KB (22,288 bytes) |
| Msvbvm60.dll | 6.00.97.82 | 1.32 MB (1,386,496 bytes) |
| Oleaut32.dll | 2.40.4275.1 | 584 KB (598,288 bytes) |
| Olepro32.dll | 5.0.4275.1 | 160 KB (164,112 bytes) |
| Stdole2.tlb | 2.40.4275.1 | 17.5 KB (17,920 bytes) |
VBRun60.exe also installs the following files as supporting files for the VBRun60.exe self-extracting file:
| File Name | Version | Size |
| Advpack.dll | 4.71.1015.0 | 73.2 KB (74,960 bytes) |
| W95Inf16.dll | 4.71.704.0 | 2.21KB (2,272 bytes) |
| W95Inf32.dll | 4.71.0016.0 | 4.50KB (4,608 bytes) |
| Vbrun60.inf | Not Applicable | 1.04 KB (1,069 bytes) |
For more information about the command-line arguments that are available for VBRun60.exe, type the following at a command prompt:
VBRun60.exe /?
For additional information about command-line arguments for this file, click the following article number to view the article in the Microsoft Knowledge Base:
189520 Outlook Deployment Kit (ODK) Setup command-line options
To distribute this new version with the Package and Deployment Wizard (PDW), copy the new version of the Msvbvm60.dll file to the following file folder so that you can use it with the PDW:
\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist
The VBRun60.exe file is not intended to replace the PDW for distributing Visual Basic applications. For example, if your application includes components such as ActiveX controls or DLLs, use the PDW or a third-party setup package for distribution. However, if your Visual Basic application only depends on the files that are included in the VBRun60.exe file, you can distribute your application by providing end users with the executable (.exe) file and with VBRun60.exe.
To determine whether your application requires additional files for distribution, you can use the PDW to create a set of setup files as a test. When the PDW creates a setup package, the PDW also creates a Setup.lst file. You can open the Setup.lst file in any text editor (for example, Notepad). If the [Setup1 Files] section of the resulting Setup.lst file only lists your .exe file, an end user should be able to run your application after the user runs VBRun60.exe to install the core run-time files. However, if the [Setup1 Files] section contains multiple files, consider using the PDW or a third-party setup package for distribution instead.
In addition to distributing simple executable files, you can use the VBRun60.exe file for the following:
- To minimize the size of Internet downloads of Visual Basic applications
By running the Vbrun60.exe file ahead of time, users can download your application from the Web faster.
- As a troubleshooting step when an installation of Visual Basic fails or a Visual Basic application fails
If Setup fails with an error message that mentions one of the core files or if registration of a component fails during Setup, the core files on the destination computer might be mismatched. If the versions of the files in the VBRun60.exe file are newer than the versions on the destination computer, you might resolve the problem by running the VBRun60.exe file before you run Setup.
You can use the Extract utility to extract the VBRun60.exe file from VBRun60.cab. The Extract.exe file is located in your Windows folder or on your Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows NT 4.0 installation CD. From an MS-DOS command prompt, you can run the following command to extract the file in the CAB file to the current directory:
Extract Vbrun60.cab
For additional information about using the Extract utility, click the following article number to view the article in the Microsoft Knowledge Base:
129605 How to extract original compressed Windows files
REFERENCES
For additional information about the bugs that are fixed by the Windows XP version of the Msvbvm60.dll file, click the following article numbers to view the articles in the Microsoft Knowledge Base:
291103 BUG: InsertObjDlg method fails with "Unable to Access Source" error message
297108 BUG: Visual Basic SendKeys causes incorrect keyboard status or freezes keyboard
326345 "Invalid Procedure Call" error message or access violation when you try to assign user-defined type to variant
300850 BUG: GlobalMultiUse class does not terminate in multithreaded environment
308644 BUG: Memory leak when you bind a recordset to Visual Basic intrinsic controls
312218 BUG: Deadlock in multithreaded process if you use declare statements for APIs in Visual Basic ActiveX .dll files or .ocx files
321055 Deadlock may occur when you use Printer object in a multithreaded application
325568 WM_WININICHANGE message causes a deadlock in multithreaded Visual Basic 6.0 applications
326264 FIX: Microsoft Excel and Microsoft Word that have user controls stop responding when you save or print
327574 FIX: ListBox extended matching does not work for Hebrew or Czech characters
Keywords: kbinfo kbfile kbvbp600fix KB823746
