Runtime Error (at 47:120): Could not call proc.

[fafa]

i was trying to install malwarebytes and i get this error

Runtime Error (at 47:120): Could not call proc.

[Porthos]

12 minutes ago, fafa said:

i was trying to install malwarebytes and i get this error

Runtime Error (at 47:120): Could not call proc.

 

 

 Hello and Welcome.

Let us try this first. If that does not work we will need some logs.

** Download MB-Clean Here **

How to use it?

1. Download the latest version of MB-Clean by clicking the link above
2. Close all open applications
3. Double-click and run mb-clean.exe 
4. A prompt with an option to clean up the system will appear:
   • Yes - will proceed with backing up the license key (Malwarebytes 3.x only) and initiating the cleanup process
   • No - will exit the utility
5. Once the cleanup process is completed, a prompt will appear:
   • Yes – will proceed and post reboot you will be prompted to continue with the downloading, installation and activation of latest version of Malwarebytes 3.x
   • No – will exit the utility and you will not be prompted (post reboot) to download, reinstall and re-activate (not recommended)
     • We recommend rebooting immediately. Additionally, stopping at this step is not recommended and will most likely not resolve your issue(s).
6. Upon reboot, a prompt will appear:
   • Yes - will download, install and activate the latest version of Malwarebytes 3.x
   • No - will exit the utility and the cleanup process is complete
     • Choose this option if you do not want to download, install and activate the latest version of Malwarebytes 3.x
   • A log file ("mb-clean-results.txt") will be on your desktop 

Edited May 13, 2017 by Porthos

[AdvancedSetup]

Hello @fafa

By any chance are you using a RAM drive or have your %temp% folder redirected to another drive besides the OS drive? Are you using any type of file or drive encryption programs?

 

[John A]

Sorry to butt in here - Ron, out of interest, what issues can occur if the %temp% folder is on another drive?  I have it set on a different drive on two computers.

Thanks

John

[dcollins]

17 hours ago, John A said:

Sorry to butt in here - Ron, out of interest, what issues can occur if the %temp% folder is on another drive?  I have it set on a different drive on two computers.

Thanks

John

It doesn't have to do with being on another drive, but on a temporary ramdrive. We are still tracking down the issue, but it seems the installer we use doesn't like being run from a ramdrive and can cause this issue.

[John A]

Thanks Devin

[nikhils]

Hello @fafa

If you still experience issues after running MB-Clean please use the following post below and get us the following logs:

MB-Check, FRST and Addition.txt.

Also could you please grab the set up logs from the Temp folder:

1. Press Windows Key + R 
2. In the box that comes up, type %temp% and press Ok 
3. In this folder that comes up, there should be at least one file that starts with Setup Log followed by a date (for example:: Setup Log - 05-08-2017). 

This will help us get to the bottom of this issue,

Thank you,