msvbvm50.dll Error

[mcp6453]

We have a program that we are installing on three computers. Two of them
are XP Pro and one of them is Windows 2000. The installation went fine
on one of the XP machines and on the 2000 machine. On the second XP box,
we got an error regarding msvbvm50.dll. (I'm not in front of the machine
so I don't have the exact language, but is was not a file not found error.)

In viewing the details of the file in c:\windows\system32, it has a date
of 1980. The version matches the version on the machine that works fine.
Thinking the file is corrupt, we tried to rename it to .old, but the
file is in use, so I cannot rename it. We download msvbvm50.exe from
Microsoft support download, but it could not install, probably for the
same reason.

How do I stop the file from running? I realize that it is part of Visual
Basic, but I don't know what part of the boot process is starting the
file or which process I can end to stop the file from being in use.
Another post mentioned unregistering it, but I don't remember much about
that process.

 

[Tom Porterfield]

We have a program that we are installing on three computers. Two of them
are XP Pro and one of them is Windows 2000. The installation went fine
on one of the XP machines and on the 2000 machine. On the second XP box,
we got an error regarding msvbvm50.dll. (I'm not in front of the machine
so I don't have the exact language, but is was not a file not found error.)

In viewing the details of the file in c:\windows\system32, it has a date
of 1980. The version matches the version on the machine that works fine.
Thinking the file is corrupt, we tried to rename it to .old, but the
file is in use, so I cannot rename it. We download msvbvm50.exe from
Microsoft support download, but it could not install, probably for the
same reason.

How do I stop the file from running? I realize that it is part of Visual
Basic, but I don't know what part of the boot process is starting the
file or which process I can end to stop the file from being in use.
Another post mentioned unregistering it, but I don't remember much about
that process.

The command regsvr32 /u msvbvm50.dll would unregister it. Try booting into
Safe Mode and see if you can delete from there. Then boot back into normal
Windows and install the runtimes that you downloaded from Microsoft.
--
Tom Porterfield
MS-MVP Windows
http://support.telop.org

Please post all follow-ups to the newsgroup only.

 

[mcp6453]

On Fri, 03 Jun 2005 16:03:33 -0400, mcp6453 wrote:

The command regsvr32 /u msvbvm50.dll would unregister it. Try booting into
Safe Mode and see if you can delete from there. Then boot back into normal
Windows and install the runtimes that you downloaded from Microsoft.

Thanks, Tom. I'll check it out this weekend.

Why is the file in use for this computer but not in use on a machine
next to it? To my knowledge, no VB applications are running on either
machine.

Is the 1980 date on the present file a big red flag, a little red flag,
or no problem?

 

[Tom Porterfield]

Thanks, Tom. I'll check it out this weekend.

Why is the file in use for this computer but not in use on a machine
next to it? To my knowledge, no VB applications are running on either
machine.

Something on that machine is using the file. The file is not used by
anything by default in XP so it is some other app that has been installed
that is using the file. After deleting the file in safe mode, boot into
normal windows and see if any errors get generated after logon. Then
investigate to see which app produced the error.

Is the 1980 date on the present file a big red flag, a little red flag,
or no problem?

The 1980 date is curious. I would call it a little red flag if both the
size and version number of the file match a known good copy.
--
Tom Porterfield
MS-MVP Windows
http://support.telop.org

Please post all follow-ups to the newsgroup only.

 

[DanS]

Thanks, Tom. I'll check it out this weekend.

Why is the file in use for this computer but not in use on a machine
next to it? To my knowledge, no VB applications are running on either
machine.

Is the 1980 date on the present file a big red flag, a little red
flag, or no problem?

This free utility: http://mstsoftware.com/c_mst_IsUsedBy.aspx will tell you
what is using any file on the PC. Install, run, and drag and drop any file
to it and it displays what has the file open.