Error relaunching virtualbox vm process 5 как исправить

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Google [Bot] and 37 guests

Теги:  Error relaunching VirtualBox  Проблема установки VirtualBox  

Интеллектуальная рекомендация

Вам также может понравиться

Я следовал нескольким учебникам, думая, что я делал что-то не так при установке виртуальных машин с использованием VirtualBox.

Важно сказать, что я использую Virtual Box на Windows 8.1

Проблема в том, что после создания виртуальной машины я получаю следующую ошибку при попытке ее запустить.

---------------------------
VirtualBox - Error In supR3HardenedWinReSpawn
---------------------------
Error relaunching VirtualBox VM process: 5<br>Command line: '81954AF5-4D2F-31EB-A142-B7AF187A1C41-suplib-2ndchild --comment Kali --startvm 823fc23c-d310-4972-b3ef-6c40742d89f3 --no-startvm-errormsgbox' (rc=-104)
---------------------------
Abort   
---------------------------

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

Я пытался создавать не только виртуальные машины Linux, но и виртуальные машины Windows.

Я нашел очень мало информации в Google об этой проблеме … заявлено, что это может быть вызвано другой программой, такой как антивирус. Я попытался удалить некоторые программы и отключить антивирус, но не смог добиться успеха.

Спасибо, что нашли время, чтобы прочитать это. Ваша помощь очень ценится.

A few days ago, I had a very nauseaful mistake when I re-use VirtualBox.

Baidu has not found a suitable solution for a long time. Hard work pays off, and discovers many solutions to this issue when reviewing VB related forums. Below I will summarize the content of this forum, I hope to help everyone.
Forum link:Diagnosing VirtualBox Hardening Issues

The small partner of time can be seen directly Solution

The main reason for this error is that the Windows operating system is incompatible with Oracle VB. There are two aspects, one is that the non-official Windows system contains some DLL files that have no signature, and the VB’s security mechanism does not allow loading such a DLL file. Because it is possible that the virtual machine is maliciously injected into the DLL, then the DLL uses the virtual machine to increase its permissions to attack the host; the other is that some Windows systems bring McAfee anti-virus software, and the cooperation of VB and this kind of anti-virus software is not very it is good.

• In order to solve the first problem, VB is part of the VB system from a portion of the VB system from a version 4.3.14.Really VB4 has problems, now VB6 is still present. .But this does not solve the problem because many legitimate Windows applications need to be installed in other processes, including:
  • Unofficial Windows Theme providers often use the Hacker version of the Windows theme DLL, such as uXtheme.dll. In Baidu this issue, there is a big giant to give this solution, which is to download the genuine unmodified UXTHEME.DLL to replace the DLL in / Windows / System32 / in. But did not solve this problem.
  • Anti-virus software usually has invasiveness, and its behavior is difficult to distinguish between malware. So reject VB operation. Common Windows comes with McAfee and some ads to disable plugins may result in VB exceptions. So uninstall it. Personally think that Windows Defender is already enough unless you often download unhealthy things haha.
  • Graphics drivers (such as NVIDIA drivers) can inject DLL, and the subject also has NVIDIA drivers and always uses it. It is not its problem.
  • Some auxiliary tools, etc.

Later, VB relaxed rules:

• «Signed» external DLL can be used in the VB process space, so-called signature is embedded in the software to provide a trusted certificate. Malware authors or pirated Windows system authors do not want to be identified, so there may be no signature.
• When you find unsigned DLL files, VB directly discards the wrong DLL and proceed, not an error.

View /logs/vboxhardening.log file, find the last line error code:

• If the error code is 0, there is no hardening problem, the blade has not encountered it, it is recommended to reinstall it repeatedly.
• If the error code is 1 (0x1) is generally a DLL problem, you can go to the CMD to run «sfc / scannow» to resolve.The title master error code is 1. After running this command, then reload VB will be reloaded by the administrator.
• If the error code is: Error Code 0xC0000005. Generally, the graphic related DLL error is recommended, it is recommended to replace the unofficial UXTHEME.DLL file. However, I found it in Baidu is

These three DLLs are replaced. If you don’t do it, you will try it. However, themervice and uXtheme are running, even if the administrator privilege is not good,Be cautious, it is possible to cause unknown consequences. You can also check the graphics driver update.

If you can’t do it, try the way below:

• Disable existing anti-virus software to test whether it is conflict with VB. However, it has been proved that Windows Defender and VB do not conflict. If you don’t feel relieved, then directly uninstall the anti-virus software because there is a very nausea.
• Make sure to disable Hyper-V, if Hyper-V has the hardware resources required for virtualization, the modern VirtualBox virtual machine is usually unable to run. This may first appear as a Hardening error, so it is worth checking. Please note that this suggestion may change soon, because VirtualBox V6.x adds experimental support for the Windows10 virtual machine monitor platform.
• Restart VB, restart the host
• Uninstall VB completely, then right-click administrator to reinstall VB. Sometimes the DLL that causes problems, or replaces the order of Windows calling the driver.

I hope to help everyone ~