asked on

VB runtime files out of date

Hello Experts. My setup file prompts the user with the following Retry/ Cancel message:
Setup has detected that your Microsoft Visual Basic 6.0 run-time files are out of date. Click OK to install this technology now or Cancel to abort the setup.

Why is this happening?--what can I do to prevent prompt from apprearing on the users desktop?

I'm using Service Pack 6...and I dont recall this ever happening under Service Pack 5.

Dabas

Hi JohnLucio:
The way I see it, your installation is using a DLL that is in use by the user.
Probably there is an essential SP6 file that is blocked by that DLL from being installed.
Probably, after OK is clicked, you will be prompted to reboot your computer.
It is the only way Setup.exe has to ensure that the problematic DLL is updated.

Dabas

John Account

ASKER

Hmmmmnnnnn...that's very interesting, Dabas, because incidently shortly thereafter, this message box appears:
The following file is in use and can not be updated: C:\WINDOWS\System32\winmm.dll
Close all other applications and choose Retry. Choose Cancel to install this file on reboot.

Dabas

JohnLucio:
That just shows that I was barking up the right tree.
Any idea which application is using winmm.dll?
I would follow the advice. Close all applications and choose Retry. If that does not work, then reboot, if possible into SafeMode, then retry the install

Dabas

Erick37

You receive multiple "System files are out of date" error messages when you install a Visual Basic 6.0 application
http://support.microsoft.com/default.aspx?scid=kb;en-us;831491

Erick37

and another...

PRB: Multiple "System Files Are Out of Date" Errors
http://support.microsoft.com/default.aspx?scid=kb;en-us;191096

John Account

ASKER

Dabas, I don't know which application is using winmm.dll, but I do know that every machine I've installed it on--about 6 of them!--have all prompted the same message!

I'm not using the setup & deployment package, Erick37. I'm using Setup Factory 7.

Dabas

John:

A Google search seems to indicate that winmm.dll is "System APIs for Multimedia"
Woud that point you in the right direction?

Dabas

John Account

ASKER

As part of the installation, wmv9VCMsetup.exe is being installed--(Windows Media)--so perhaps that uses the same dll as well.

Dabas

Probably, but then I am not acquainted with Setup Factory 7. The PDW has a file named setup.ini that gives you a list of dll files that are going to be installed.
I am sure that Setup Factory will have something similar that will allow you to verify

John Account

ASKER

Okay. Here's what's happening: If the user already has MSVBVM60.DLL present on his system when running the setup, he does not get the message box that "Setup has detected that your Microsoft Visual Basic 6.0 run-time files are out of date." However, if MSVBVM60.DLL is not present on his system, he gets that message box.

ASKER CERTIFIED SOLUTION

Dabas

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

John Account

ASKER

Thanks, Dabas.

Dabas

YOure welcome!