Главная » Error » Solution: Malwarebytes runtime error

Solution: Malwarebytes runtime error

What is the cause of the runtime error when installing Malwarebytes (Couldn’t Install Proc)

  • Damaged Malwarebytes installation: If this problem occurred after a failed Malwarebytes installation, you are probably seeing this error code because you still have leftover files from the corrupted installation. In this case, you can use the Malwarebytes support utility to remove the remaining files.
  • Untrusted Malwarebytes certificate: if you are experiencing this problem on Windows 10, you are most likely seeing this error code because your system has classified the security certificate that Malwarebytes needs as “untrusted”. In this case, you can solve the problem by using the certificate manager to remove the Malwarebytes certificate and install any pending Windows updates before attempting the installation again.
  • Damaged system files: in more severe conditions, you can expect this problem to occur due to some kind of corruption of some Windows files. In this case, the first attempt to solve the problem is to use some built-in utilities that can fix corrupted system files (DISM and SFC). If this fails, you should consider repairing or a new installation.
  • The %TEMP% folder is in a different location: It turns out that one of the most common cases where this problem occurs is in a scenario where the TEMP folder is on the network or on RAMDRIVE or RAMDISK, rather than in its default location. If this is the case, you should be able to solve the problem by moving the Temp folder back to its default location.
  • Logical errors on the operating system disk: According to some concerned users, this problem can also occur in situations where the operating system disk contains logical errors that affect its ability to safely store newly created files. In this case, you should run a CHKDSK scan and see if it solves the problem.
  • Residual malware/emergency files: according to the Malwarebytes team’s security post, this problem can occur if the operating system disk currently stores files that actively prevent certain security packages from being installed. Users who also encountered this problem were able to resolve it by running a scan with a third-party Security Scan.

Решение ошибки «Runtime error»

Решение №1 Ликвидация кириллицы

Ошибка «Runtime error» может возникать при запуске тех программ и игр, в расположении которых присутствуют кириллические символы. Например, на данную ошибку можно наткнуться, если запускаемое приложение находится по пути C:Users[ИМЯ АККАУНТА НА РУССКОМ]Downloads[КОРНЕВАЯ ПАПКА ПРИЛОЖЕНИЯ]. Избавьтесь от русского языка по пути к приложению и попробуйте запустить его еще раз.

Решение №2 Изменение языка программ, не поддерживающих Юникод

Появление ошибки «Runtime error» возможно в том случае, если в параметрах региональных стандартов для приложений, не поддерживающих Юникод, задан русский, а не английский язык.

  • Нажмите WIN+R и выполните значение «CONTROL»;
  • кликните на пункт «Изменение форматов даты, времени и чисел» в разделе «Часы и регион»;
  • перейдите во вкладку «Дополнительно» в появившемся окошке «Регион»;
  • нажмите на кнопку «Изменить язык системы…»;
  • в ниспадающем меню выберите «Английский (США)» и сохраните внесенные изменения;
  • перезагрузите ПК.

Запустите проблемное приложение, чтобы проверить наличие ошибки.

Решение №3 Переустановка Visual Studio C++ и .NET Framework

Некорректно установленные (либо отсутствующие в системе) распространяемые библиотеки Microsoft Visual Studio C++ и .NET Framework могут вызвать появление «Runtime error». Чтобы переустановить эти библиотеки, вам нужно сделать следующее:

  • вызовите перед собой Панель управления, как это было показано выше;
  • кликните на «Удаление программы» в разделе «Программы»;
  • найдите в списке программ все версии Visual Studio C++ и удалите их;
  • перейдите на официальный сайт Майкрософт и загрузите необходимые установщики VS C++;
  • проделайте тоже самое с различными версиями .NET Framework на своем ПК;
  • вернитесь к окошку «Программы и компоненты» и кликните на пункт «Включение или отключение компонентов Windows»;
  • убедитесь, что возле всех версий .NET Framework стоят галочки;
  • закройте все открытые окна и перезагрузите ПК.

Решение №4 Удаление недавно установленных программ

Определенные программы могут входить в конфликты с приложениями на компьютере. Ошибка «Runtime error» начала появляться практически сразу после установки какой-то программы или игры? Удалите ее, перезагрузите ПК и попробуйте запустить нужное вам приложение еще раз. Возможно, на сей раз никакой ошибки не появится. Заняться удалением программ можно в «Программы и компоненты» (показано выше ↑).

To fix Malwarebytes installation runtime error (Failed to install Proc)

September 2022 Update:

You can now prevent PC problems by using this tool, such as protecting you against file loss and malware. Additionally it is a great way to optimize your computer for maximum performance.
The program fixes common errors that might occur on Windows systems with ease – no need for hours of troubleshooting when you have the perfect solution at your fingertips:

  • Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
  • Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
  • Step 3 : Click “Repair All” to fix all issues.

download

To fix Malwarebytes installation runtime error (Failed to install Proc)

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:

  1. Open your default browser and visit the official download page of Farbar Recovery Scan to download the latest version. Keep in mind that you’ll need to choose between the 32-bit and 64-bit versions depending on your OS architecture.
    Downloading the Farbar Security Scan
  2. Once the executable is successfully downloaded, right-click on it and choose Run as administrator from the context menu. When you see the UAC prompt, click Yes to grant admin access.
  3. Next, follow the on-screen prompts to complete the installation, then restart your computer and wait for the next startup to complete.
  4. After your computer boots back up, open the Farbar Recovery Scan tool and click Scan on the first screen. leave the default settings intact and click on Fix to start the operation.
    Running a Farbar Recovery Scan
  5. Once the operation is complete, restart your computer once again and see if the issue is fixed at the next computer startup.

If the same problem is still occurring, move down to the next potential fix below.

How to fix the “Malwarebytes Installation Runtime Error: Could Not Call Proc” issue?

FIX 1: Move the %TEMP% folder back to the Default Location:

As mentioned above in the causes as well, the wrong placement of the %TEMP% folder. The folder is mostly located at RAMDRIVE, RAMDISK, or on a network rather than its original location. In this case, all you can do is move the %TEMP% folder into the correct location and then retry the installation process. For doing so,

  • To begin with, download Malwarebytes’s latest version from its official website.
  • Now launch the RUN prompt by pressing WINDOWS + R altogether.cmd .net framework
  • In the empty dialogue box, type “cmd” and then click on OK. It will open the Command Prompt window for you. If you see the UAC (User Account Control) option, click on Yes, and it will grant you admin access on the Command Prompt window.
  • On the Command prompt window, type or Copy + Paste the following commands one after the other and press Enter after each one of them.

set TEMP=C:Windowstemp

Advertisements

set TMP=C:Windowstmp

cd “%USERPROFILE%Downloads”

  • After all the Commands you have entered are processed, you can now close the Command Prompt window.
  • Now navigate to the Malwarebytes setup executable (that you downloaded in the 1st step), right-click on it, and select Run as Administrator from the sub-menu.
  • Now try to install Malwarebytes and check whether the said issue persists, and you see the “Runtime error (83:120): Could not call proc” or not.

FIX 2: Run a CHKDSK scan:

Any issue related to the solid-state drive or traditional hard drive can also trigger the “Runtime error (83:120): Could not call proc” issue for some users. A data block inconsistency or a logical error can also be responsible for the same. The suffered users tried to resolve this situation by running a CHKDSK scan. For doing so,

  • Firstly, press WINDOWS + X simultaneously for opening the WinX menu.
  • Now from the WinX Menu, click on Command Prompt (Admin) to launch the elevated Command Prompt. (In case you see the UAC (User Account Control) option, click on Yes, and it will grant you admin access on the Command Prompt window.)

Or

Advertisements

  • Launch the RUN prompt, and in the empty dialogue box, type cmd and then click on OK. It will open the Command Prompt window for you. If you see the UAC (User Account Control) option, click on Yes, and it will grant you admin access on the Command Prompt window.
  • Now in the Command Prompt window, type chkdsk X:

NOTE: Here, ‘X’ will be the drive letter corresponding (that you want CHKDSK to scan) to the partition of your computer’s hard drive. Following it will be the parameters you wish CHKDSK to perform the scan with. After that, press Enter. Running the CHKDSK utility from an elevated Command Prompt, you can use any of the following parameters:

/f – Tells CHKDSK to fix any and all errors that it finds

/r – Tells CHKDSK to locate bad sectors on the drive and try to recover any and all readable information from them

Advertisements

/x – Tells CHKDSK to forcefully dismount the selected drive before scanning it

  • The final Command you type into the elevated Command Prompt will look either of these:

chkdsk D: /f /x (if you want CHKDSK to dismount your computer’s D drive and then scan it for errors and fix any that it finds).

Or

chkdsk C: /f (if you want CHKDSK to scan your computer’s C drive for errors and try to fix any that it finds)

  • Now, wait for the CHKDSK scan to process. Once done, it will attempt to fix most of the available errors in your system. After that, try to install Malwarebytes and check whether the issue is resolved or not.

Note: The above method will work on Windows 7, 8, 8.1, and 10.

FIX 3: Run SFC and DISM Scans:

Advertisement

There might be a possibility that you are dealing with some type of system corruption that is also responsible for triggering the “Runtime error (83:120): Could not call proc” issue. Following the case, it is advisable to Run the SFC, and DISM scans one after the other. For doing so,

For SFC scan:

  • Firstly, open the Command Prompt window. Make sure you open it with Admin access.
  • Now in the Command Prompt window, type “sfc /scannow” and press Enter. It will start scanning for corrupt or outdated system files.

Note: The SFC scan is entirely local and does not require any internet connection for running. However, for running the DISM scan, users need a stable running internet connection on hand.

For DISM scan:

  • Firstly, open the Command Prompt window. Make sure you open it with Admin access.
  • Now in the Command Prompt window, type the following commands and then press Enter after each one of them:

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

  • The scanning process might take a while, wait for some time and let the scanning process gets completed on its own.
  • When you have successfully run both the scans, try to install the Malwarebytes and check whether the “Runtime error (83:120): Could not call proc” issue is resolved or persist.

Способ №1. CCleaner

Самое простое решение заключается в том, чтобы воспользоваться программой для чистки реестра. Как это работает?

Все просто – чистильщик реестра, собственно, и предназначен для того, чтобы исправлять всевозможные проблемы, вроде той, которую рассматриваем мы, систематизировать файлы и добавлять то, чего недостает ему для нормальной работы.

Лучшей по праву считается CCleaner, хотя вы можете воспользоваться и другой.

Чтобы использовать ее, сделайте вот что:

  1. Скачайте (вот ссылка на бесплатную) и установите программу.
  2. Запустите. Перейдите на вкладку «Реестр» на панели слева.
  3. В разделе «Целостность» поставьте галочки на всех возможных пунктах – никто не знает, в чем именно проблема.
  4. Нажмите кнопку «Поиск проблем». Когда этот процесс закончится, нажмите кнопку «Исправить…».

Использование

  1. Подождите, пока приложение исправит все проблемы. Перезагрузите компьютер.

После этого runtime error должен перестать появляться. Если нет, переходим к следующему решению.

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:

  1. First things first, start by downloading the latest version of Malwarebytes from the official web page .
  2. Next, press Windows key + R to open up a Run dialog box. Next, type ‘cmd‘ and press Ctrl + Shift + Enter to open up an elevated Command prompt. When you see the UAC (User Account Control), click Yes to grant admin access.
    Opening an elevated Command Prompt
  3. Once you’re inside the elevated Command Prompt, type the following commands in the same order and press Enter after each line to move the %TEMP%, %TMP%, and Download folder to the default location:set TEMP=C:Windowstemp
    set TMP=C:Windowstmp
    cd “%USERPROFILE%Downloads”
  4. Once every command has been successfully processed, you can safely close the elevated Command prompt.
  5. RIght-click on the Malwarebytes setup executable you downloaded at step 1 and click on Run as Administrator from the context menu that just appeared.
    Running the Malwarebytes installation executable as administrator
  6. Carry on with the installation normally and see if the problem is now fixed.

If the same ‘Runtime error (83:120): Could not call proc.’ problem is still occurring, move down to the next potential fix below.

Способ №2. DirectX

Вполне вероятно, что ее появление вызывают какие-то проблемы с DirectX. Возможно, какие-то файлы исполняемых библиотек были повреждены или же существующие библиотеки банально устарели.

В любом случае, лучше всего просто установить наиболее актуальные варианты и, опять же, перезагрузить компьютер.

Для этого зайдите на сайт Microsoft, на страницу с возможностью скачать DirectX. Запустите скачанный файл и выполните все действия, подразумевающие установку исполняемых библиотек.

Здесь нет никаких особых рекомендаций – обычная.

Страница загрузки DirectX

Если после установки и перезагрузки компьютера ошибка не исчезла, идем дальше.

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 .


Running 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.

Reset the %TEMP% folder to the default folder

As mentioned above in the reasons, improper placement of the %TEMP% folder. The folder is usually located on RAMDRIVE, RAMDISK, or on the network, not in the original location. In this case, all you can do is move the %TEMP% folder to the desired location and then try the installation process again. To do this,

  1. First, download the latest version of Malwarebytes from the official website.
  2. Now run the RUN prompt by pressing the WINDOWS + R key combination at the same time.
  3. Type “cmd” in the empty dialog box and click OK. This will open a command prompt window for you. If you see the UAC (User Account Control) option, click “Yes” and you will have administrator rights for the command prompt window.
  4. In the command prompt window, type or copy the following commands in turn and press Enter after each command.
    set TEMP=C: Windows emp
    set TMP=C: Windows mp
    cd “%USERPROFILE%Loads
  5. Once all the commands you have entered have been processed, you can close the command line window.
  6. Now navigate to the Malwarebytes installer executable (which you downloaded in the first step), right-click on it, and select Run as administrator from the submenu.
  7. Now try to install the malware bytes and check if the mentioned problem persists and if you get the message “Runtime error (83:120) : Could not call proc” or not.

Способ №3. Visual C++

О распространяемом пакете Visual C++ в контексте рассматриваемой проблемы можно скачать то же самое, что и о библиотеках DirectX.

Возможно, какие-то файлы были повреждены или версия устарела.

Бывают в данном случае и другие ситуации, когда установленная C++ попросту не подходит для вашей операционной системы.

Ниже приведена таблица с вариантами, которые подходят для разных версий ОС.

Таблица 1. Требуемые версии Visual C++ для Windows

Операционная системаТребуемая Visual C++
Windows XP и ниже C++2008
Windows 7 C++2010
Windows 8 и 10 Наиболее актуальная на данный момент

Так вот, в зависимости от того, какая у вас ОС, вам следует скачать и инсталировать на свой компьютер C++2008 (64-бит, 32-бит), C++2010 (64-бит, 32-бит) или же C++2015 обновление 3.

Это наиболее актуальная версия по состоянию на июнь 2017 года. В будущем выйдут новые, поэтому следите за новостями на официальном сайте Microsoft.

Скачивание происходит одинаково – выбираем язык распространяемого компонента и жмем кнопку «Скачать». После этого останется запустить загруженный файл.

После этого перезагрузите компьютер.

Страница загрузки Visual C++

Run the CHKDSK scan

Any problem with the semiconductor or traditional hard drive can also cause a “Runtime error (83:120): Could not call proc” message for some users.

It can also be caused by inconsistent data blocks or a logical error. Affected users have tried to fix this situation by running a CHKDSK scan. To do this,

  1. First, press WINDOWS + X to open the WinX menu.
  2. Now, in the WinX Menu, click Command Prompt (Admin) to run the extended command line (if you see the UAC (User Account Control) option, click Yes to grant yourself administrator privileges in the command line window).

Or

  1. Run the RUN prompt and type cmd in the empty dialog box, then click OK. A command prompt window will open. If you see the UAC (User Account Control) option, click Yes, and you will have administrator access to the command line window.
  2. Now type Chkdsk X in the command line window:

NOTE: Here, “X” is the drive letter that corresponds to the partition on your computer’s hard drive (which you want to scan with CHKDSK). Next are the parameters that you want CHKDSK to use to perform the scan. After that, press the Enter key.

When running the CHKDSK utility from the extended command line, you can use any of the following parameters:

/f – Tells CHKDSK to fix any errors it finds.

/r – Tells CHKDSK to find bad sectors on the disk and try to recover all readable information from those sectors.

/x – Tells CHKDSK to forcibly disconnect the selected drive before scanning it.

  • The last command you enter on the extended command line is as follows:

Chkdsk D: /f /x (if you want CHKDSK to shut down the D drive on your computer and then check for errors and fix them).

Or

Chkdsk C: /f (if you want CHKDSK to look for errors on your C drive and try to fix them).

  • Now, wait for the CHKDSK scan to finish. After that, it will try to fix most of the bugs available on your system. After that, try to install the malware bytes and see if the problem is solved or not.

Note: The above method works on Windows 7, 8, 8.1, and 10.

Источники

  • https://windowsbulletin.com/solution-malwarebytes-runtime-error-could-not-call-proc/
  • https://GamesQa.ru/games/runtime-error-28564/
  • https://appuals.com/runtime-error-when-installing-malwarebytes/
  • https://www.getdroidtips.com/malwarebytes-installation-runtime-error/
  • https://pomogaemkompu.temaretik.com/1702206922594454476/samye-legkie-sposoby-ispravit-oshibku-runtime-error/
[свернуть]
Решите Вашу проблему!


×
Adblock
detector