Jump to content
bikoe

Runtime Error (at 14:76) with MB 3.0.6

Recommended Posts

I am experiencing the same issue on 2 computers, and I have been following this thread since it got started. I noticed the original poster stopped responding so let me say that I have tried to install 3.0.6 version and similar error occurs. Same error, slight difference. 

Runtime Error (at 14:76):

Could not call proc.

Edited by bikoe
spelling error

Share this post


Link to post
Share on other sites

Hello @bikoe

I split your post from the last thread so we can trouble shoot your issue better.

Please download Farbar Recovery Scan Tool from here 

FRST 32-bit version: https://downloads.malwarebytes.com/file/FRST
FRST 64-bit version: https://downloads.malwarebytes.com/file/FRST64


Note: You need to run the version compatible with your system

•Double-click to run it. When the tool opens click Yes to the disclaimer.

Note: If you are prompted by Windows SmartScreen, click More info followed by Run anyway.

•Click the Scan button.

•When the scan has finished, it will save 2 logs in the same directory the tool was run from. Please attach the following logs in your reply.

Addition.txt
FRST.txt

Share this post


Link to post
Share on other sites

Looks like your FRST log is incomplete.

Can you please run the tool again and enable all the optional scans and run the scan again.

Please send us the new FRST log file .

Share this post


Link to post
Share on other sites
On 5/19/2017 at 3:47 PM, nikhils said:

Can you please try and download MBAM chameleon: https://www.malwarebytes.com/chameleon/

Run the tool and open the HTML page and try to install MBAM 2.x . Also please save your scan results as a txt file and post it to this post.

Thank you,

I apologize for the delayed response. I tried MBAM chameleon. Nothing detected. Scan results attached. 

MBAM_ScanResults_5-30-2017_0858.txt

Share this post


Link to post
Share on other sites

I just got off the phone with a friend who is having the exact same issue installing MBAM 3.x

Could this possibly be a issue with the installer itself? 

Share this post


Link to post
Share on other sites

Hello @bikoe

Can you please check the instructions below to see if it resolves your issue:

  1. Press Windows Key + R to bring up the run dialog
  2. In the dialog window, type certmgr.msc and click Ok
  3. In the window that comes up, on the left side, double click Untrusted Certificates so you can see the folders beneath it
  4. If a Certificate folder exists, click it
  5. Delete any certificates in this folder that have the name Malwarebytes in it
  6. Reboot
  7. After reboot install Malwarebytes product.

Share this post


Link to post
Share on other sites
Quote
  1. Press Windows Key + R to bring up the run dialog
  2. In the dialog window, type certmgr.msc and click Ok
  3. In the window that comes up, on the left side, double click Untrusted Certificates so you can see the folders beneath it
  4. If a Certificate folder exists, click it
  5. Delete any certificates in this folder that have the name Malwarebytes in it
  6. Reboot
  7. After reboot install Malwarebytes product.

I don't know about our friend @bikoe issue, but this solved my problem, and I don't even needed to reboot. Thank you, man

Edited by Brsvtzk

Share this post


Link to post
Share on other sites

Can you check in your %temp% folder for files that start with "Setup Log" and upload them in your reply? This should give us an idea of what's going on

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.