After investigating the issue, this problem is reported to occur for a variety of different reasons. Here’s a shortlist of potential culprits:
Method 1: Moving %TEMP% folder back to the Default Location
According to some affected users, this problem can occur in instances where your OS is unable to temporarily save the files used by Malwarebytes during the installation in the %TEMP% folder. In most cases, this problem will occur due to the fact that the folder is either located on a network or a Random Access Memory Drive (also known as RAMDRIVE or RAMDisk). If this scenario is applicable, you should be able to fix this problem by using an elevated Command Prompt to set the %TEMP% folder in the correct location before retying the installation. In case you’re looking for step by step instructions, follow the short guide below: If the same ‘Runtime error (83:120): Could not call proc.’ problem is still occurring, move down to the next potential fix below.
Method 2: Running a CHKDSK scan
According to some affected users, this problem can also occur due to an issue related to your traditional hard drive or solid-state drive. In most cases, you can expect this issue to occur due to a logical error or a data block inconsistency. Users that found themselves in a similar situation have confirmed that they managed to fix the issue by using the CHKDSK utility to fix (or at least replace) hard drive errors and bad sectors that might be contributing to the apparition of this error code. You can initiate a Check Disk utility from an elevated Command prompt. But in order to make sure that you maximize your chances at fixing the Could not call proc. error, our recommendation is to open the CMD prompt with admin access. Here are some instructions that will show you how to run a CHKDSK scan. Note: These instructions will work on every recent Windows version including Windows 7, Windows 8.1, and Windows 10. In case you already initiated a Check Disk utility scan and you’re still seeing the same Runtime error (83:120): Could not call proc. error when you attempt to install Malwarebytes, move down to the next potential fix below.
Method 3: Running a Farbar Security Scan
According to some affected users, this problem can also occur if you’re dealing with some kind of remnant adware or malware files that are inhibiting your OS ability to install security suites – As it turns out, certain malware will actively try to block the installation of security suites. If this scenario is applicable, you should attempt to fix the problem by running a 3rd party scan with a 3rd party suite like Farbar Recovery. Note: This is not an official Microsoft product. Even though a lot of users have confirmed it’s effective in fixing this problem, it will handle and potentially replace critical kernel data belonging to your Windows installation. If you are determined to use this utility, follow the instructions below to use Farbar Security Scan to initiate a security scan to fix the Runtime error when installing Malwarebytes: If the same problem is still occurring, move down to the next potential fix below.
Method 4: Running the Malwarebytes Support tool
If your Windows has crashed in the past while Malwarebytes was in the middle of a scan or while you were trying to install it, it’s possible to see the “Runtime error (83:120): Could not call proc.” because the installation has become corrupted. Malwarebytes support team is aware of this issue and they even have a tool that’s capable of fixing the application in this kind of scenario. If this scenario is applicable, you can fix the problem by running the official Malwarebytes Support tool to clean any remnant files from a botched installation before reinstalling the tool from scratch. To make things easier for you, follow the instructions below: If you’re still seeing the same Runtime error (83:120): Could not call proc. the error even after using the specialized utility to clean remnant files from a botched installation, move down to the next potential fix below.
Method 5: Fixing the Certificate Issue
As it turns out, this problem can also occur due to the fact that your operating system ends up labeling the Malwarebytes certificate that’s needed to install the tool as an ‘untrusted certificate’. This is a well-known glitch that’s known to occur on certain Windows 10 builds that are missing a series of key security updates. If this scenario is applicable, you’ll be able to fix the problem by using the Certificate Manager utility to remove the Malwarebyte-related entry from the list of untrusted certificates before installing every pending Windows Update and retrying the installation. Here’s a quick step by step guide that will walk you through the entire process: In case the same problem is still occurring, move down to the next potential fix below.
Method 5: Running SFC and DISM Scans
If none of the fixes above have worked for you, you should seriously start to consider the fact that you might be dealing with some type of system corruption. This scenario is even more likely if you’re encountering similar issues when trying to install different programs. In this case, you should be able to fix the problem by utilizing a couple of utilities that are capable of fixing OS-related file corruption: DISM (Deployment and Image Servicing and Deployment (DISM) and SFC (System File Checker) These two utilities are similar, but they go about fixing corrupted instances in different ways:
SFC Scan – This type of scan is entirely local and doesn’t require an internet connection. System File Checker works by utilizing a local archive to replace corrupted files from your operating system with healthy equivalents.Running a System File Checker ScanDISM Scan – Think of this as a revised version of SFC. The main advantage of the Deployment and Image Servicing and Deployment utility is that it uses Windows Update to download healthy equivalents to replace local corruption. So even if the locally cached archive is affected, you’ll still be able to fix the problem without having to reinstall the entire operating system.Running a DISM checkNote: In order to use this utility, you’ll need to ensure that you have a stable internet connection.
Once you’ve successfully run both types of scans, attempt to install Malwarebytes once again and see if the same problem is still occurring. If the same problem is still occurring, move down to the next potential fix below.
Method 6: Refreshing every OS Component
In case you’ve tried every potential fix below and you’re still seeing the same ‘Runtime error at 44:134: could not call proc.’ error when you’re trying to install Malwarebytes, you’re probably dealing with some kind of system file corruption that you won’t be able to fix conventionally. If this scenario is applicable, your last chance at fixing this problem is to refresh every relevant Widnows component in an attempt to fix the installation infrastructure. This can be done in two different ways:
Clean installing your Windows installation – This is the easy way out since it won’t require you to use a compatible installation media. However, the main disadvantage is that unless you backup your data in advance, you will lose any personal information present on the OS drive.Repair installing your Windows installation – This operation will allow you to keep all your personal files present on the OS drive. However, going for a repair install (in-place repair) is a more tedious process that requires you to insert a compatible installation media (flash drive or DVD).
Once you refresh every OS component using one of the methods above, repeat the installation procedure and see if the problem is now fixed.
Fix Error Could not find Java SE Runtime EnvironmentHow to Fix Malwarebytes not Opening on WindowsHow to Fix Error Code 403 with MalwareBytesHow to Solve Malwarebytes Real-Time Web Protection Won’t Turn on Error
