30 replies to this topic

[tkmops]

Hi,
Newbie to this forum....

I've been using Malwarebytes for a few years now, without problems. Just recently an error box
popped up, saying 'this application failed to start because MSVBVM60.dll was not found'.
I have this file in my windows system32 folder...I also copied it to my system folder, and to
my malwarebytes folder on my 'C' drive. I also downloaded a more recent version of this file..
my original was dated 2004, and this new one is 2009. I also un-installed my old version
of malwarebytes, and installed the new 1.38...and I'm still getting the same error msg.
Anyone know why my PC can't find this file?

[exile360]

Greetings and welcome .

Please try downloading and installing this from Microsoft and see if it fixes the error for you. Please post back and let me know how it goes.

Thanks.

[tkmops]

Thanks for that ...downloaded the file and ran it, still getting the same error . Do I need to reboot my PC for it to take effect? It didn't ask me to.
Also, in another post string, asking about the same missing file issue, someone responded: at the CMD prompt run this:'X' MSVBVM60.dll...but I can't recall what the 'X' was....I thought I wrote it down, but I guess not. Anyway it came back with an error of '0x800a0046'. I looked it up online, but the info didn't seem to relate at all to my issue
Why would my malwarebytes be working fine, and then just not be working fine? I've added no new software/hardware, nor un-installed any programs.

[exile360]

Ok, try the following command after a reboot (good idea in case it was needed, even though it didn't ask you to):

Open a command prompt and enter the following:

regsvr32 msvbvm60.dll

Let me know if it gives you any errors after running that command.

The next step if that fails would be to attempt following the instructions here to see if a complete reinstall of MBAM fixes the issue.

Please let me know how it goes .

[tkmops]

Yes, that was the Run CMD from the other post....'regsvr32 msvbvm60.dll', tried it again and got: The module 'msvbvm60.dll' was loaded but the call to
DIIRegisterServer failed with error code 0x800a0046. You know what that means, and how to fix it?

[AdvancedSetup]

You probably have more than one. Search your drive for all copies of it. Then use REGSVR32 /U MSVBVM60.dll to unregister it.
Then delete or move all copies to a new folder that is not in the path. Reinstall the file that Exile linked you to.

[tkmops]

OK, thanks, tried that. got rid of all my 'MSVBVM60.dll' files, ran that CMD and got 'The module 'msvbvm60.dll' was loaded but the call to DIIUnregisterServer failed with error code 0x8002801c. I have a restore point from about two weeks ago, if I restored, would that fix this?

[exile360]

It looks like this could be related to registry permissions based on this. I wouldn't try System Restore just yet. Take a look at that link and use Regmon as it instructs and see if it doesn't indicate which key in the registry is causing the problem. Once you find out, please post back here with the info.

Thanks .

[AdvancedSetup]

In most cases if that is the cause then this should fix it.

Please download and run the following fix from Microsoft How do I restore security settings to the default settings?
When completed please reboot your computer.

[tkmops]

exile360:Tried the MS Win troubleshooting, but the 'Regmon'' link was 'page not found', so I wasn't able to do that.

Advancedsetup:I downloaded the security settings file and ran it..it seemed to work OK, but I'm still getting the same error as before.
Let me ask, should the 'MSVBVM60.dll' file be in windows/system, or windows/system32, or in the 'C' drive programs malwarebytes folder?
I've tried it all 3 places(just one at a time, not all 3 at the same time)...makes no difference.
I uninstalled malwarebytes...it gave me a hard time, saying it couldn't find 'MSVBVM60.dll', but it seemed to work, as it's not in programs anymore, nor in my start menu. Tried reinstalling malwarebytes again, got the same error msg.

[exile360]

It should be in Windows\System32. The link for Regmon is here if you want to try investigating it further via that method.

edit: RegMon has apparently been replaced with ProcessMonitor so that would be the tool to use to investigate.

[tkmops]

OK, went out on the web and found 'Process Monitor'(according to MS, this replaces Regmon), downloaded and installed it. And while it was running, ran the 'regsvr32 /U MSVBVM60.dll' CMD, it's been over 30 mins, and it's still loading...over 6 million now. Did a filter for 'command line' and regsvr32, it brought 1492 entries...what do I look for? Ah, I see that someone has made a post while I was typing this one out.

[exile360]

Yeah, you want to look for entries from regsver32 when registering it or unregistering it and analyze one of those lines where it was accessing MSVBVM60.dll and figure out why it's getting blocked.

[tkmops]

Hmmm....I can't seem to get the filter to work now...a blank page comes up when using 'command line' and 'is' 'regsvr32'. I will have to continue this tomorrow(well, later today actually)...need to go sleepy time...zzzzzzzz. What drop down(s) should I using in Process monitor, and what verbage should I be putting in the blank box?

[exile360]

Aside from searching for the process by name (regsvr32) look for entries under the colum for Result and look for failures involving the registry. Don't worry too much though, I believe AdvancedSetup will be back tomorrow as well and he knows much more than I. He should be able to help you get it sorted once and for all (hopefully ). Have a good night.

[tkmops]

Ok, new day...started again. Ran the process monitor, and then the 'regsvr32' CMD, and after experimenting with the filters, 'Process name' 'begins with'
regsvr32 seemed to do the trick of filtering. I found the following:
Process Name:regsvr32.exe
PID:5664
Operation:CreateFileMapping
Path:C:\windows\system\msvbvm60.dll
Result:FILE LOCKED WITh ONLY READERS
Detail:Sync Type:Sync TypeCreateSection, PageProtection:PAGE_READONLY.

I hope this makes sense to someone ....this is quite a bit over my head

If and when I do get this fixed, I still would like to find out what caused it. Do regkeys all by themselves go bad...could this be a virus, or malware, or an email I opened(just the email, no .exe's, or pictures), that left something on my PC? Since I haven't been able to run malwarebytes, I only have Trend Micro Anti-Virus, and Spybot, and of course, the Vista 'Defender' and firewall...they all report no virus, no malware, everything is just fine.

[tkmops]

More experimenting...I couldn't figure out how to run CMD as administrator from two posts ago...finally figured it out...and was able to unregister the .dll.
At this point should I run CMD as administrator and run 'regsvr32 msvbvm60.dll?, and then try reinstalling malwarebytes?

[exile360]

Instead of re-registering the dll, please try installing the MS Runtime update that I linked to in post #2. Then try reinstalling Malwarebytes' and see if it works correctly. Also, since you have Trend Micro installed, please have a look at this topic and adapt the instructions to your version of Trend Micro to prevent any conflicts with Malwarebytes'.

An additional question, do you have User Account Control turned off? If you do you'll need to right click on the Malwarebytes' installer and select Run as administrator. Please also note that it is NOT recommended to run Vista with User Account Control turned off.

[tkmops]

Sorry for the delay in getting back...14 hour days at work....ughhhh. OK, did the above, still getting the same msg. I have UAC always turned on. Your Trend link went to a Trend Internet Security Pro, which I don't have, and I don't have those controls to play with. And I've never had a problem between Trend and Malwarebytes before, over the past year or so. The only problem I had was with Ad-Adware, which I uninstalled. Any other ideas? Maybe it's time to do a restore? Would a restore fix this? It would only wipe out a few weeks worth of changes...I could live with that.

[AdvancedSetup]

Just uninstall Trend and try it. That would be a lot quicker test to confirm it if was the issue.