Windows Server 2003 includes a new version of Msvbvm60.dll (823746)

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: For additional information about command-line arguments for this file, click the following article number to view the article in the Microsoft Knowledge Base:
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: 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: For additional information about using the Extract utility, click the following article number to view the article in the Microsoft Knowledge Base: