VBox startup failed, Genymotion startup failed, Vagrant migration

VBox startup failed, Genymotion startup failed, Vagrant migration

VBox startup failed, Genymotion startup failed, Vagrant migration

2023.10.9 The latest version vbox7.0.10, Genymotion3.5.0

Vbox failed to start

1. Check the log

Error -610 in supR3HardenedMainInitRuntime! (enmWhat=4)
Failed to locate 'vcruntime140.dll'

How to view log information -> Find the location of the virtual machine ->
Find the Logs folder.

Find this file.

You can quickly find error information by searching for Error and Failed!

The actual problem is the error here

can be seenFailed to locate 'vcruntime140_1.dll'
The search engine found information and found that it was a problem with Wireshark -> open the Wireshark software -> update to the latest version

Other errors of this type may be caused by installing the latest Microsoft Visual C++ runtime files, including 32-bit and 64-bit runtime files. The installation program will automatically detect and install the runtime files required by the system. Supports silent installation, one-click installation, convenient operation.

Here is a download of the runtime installation file: https://www.52pojie.cn/thread-1821877-1-1.html

VBox can be started normally when found!

Source: https://forums.virtualbox.org/viewtopic.php?t=108749

Genymotion failed to start

The error I encountered here was the problem with vbox above, as well as network problems.

Find the largest vbox network,
right-click to view properties

Note: To enable the last network, the network used when checking the properties for connection must also be enabled. If it still does not work, check whether the network used uses other unopened networks.

So turn on these two networks here -> How to turn on: right-click and select Enable

Start genymotion again and find that the startup is successful!

Vagrant migration

Due to the above problems, I have tried uninstalling and installing, modifying the registry, etc., but none of them took effect and the environment was messed up.
Here is the virtual machine generated by our Vagrant.

Open Vbox and select registration -> select our vbox file

. Registration is successful!

If the machine is in hibernation or abnormally shut down at this time, just select Clear and restart.

View this file in the folder.

Copy the uuid
and open the upper-level directory.

The path is as follows: vbox.vagrant\machines\default\virtualbox

Check whether the IDs are the same.

At this time, retry the vagrant up command to restart the virtual machine originally generated by vagrant instead of regenerating a virtual machine.