Version used: eNSP 1.3.00.100+VirtualBox 5.2.44+WinPcap_4_1_3+Wireshark latest version .
It is best to install the win11 system according to the above version. Do not install a higher version of VirtualBox, otherwise incompatibility may occur. The Wireshark version requirements are okay. The installation order is VirtualBox 5.2.44+WinPcap_4_1_3+Wireshark ----> eNSP .
Attached is the installation tutorial link and installation package. The Wireshark version is a bit low. You can download and install the latest version yourself. I tested the latest version and there was no problem:
Download link: https://pan.baidu.com/s/1uDene9PD11AsT5-_J4D_vg
Extraction code: c08s
When installing VirtualBox 5.2.44 in WIN11 Home Chinese version, it will show that it is incompatible and cannot be installed. At this time, you can solve the problem by turning off memory isolation and continue the installation. Method: turn on the memory isolation settings and turn off memory integrity.
After completing the installation according to the above, I thought everything was fine. I started eNSP and added several AR devices. After starting, I found an error: startup failed, error code: 40.
After that, first try to solve it according to the official documentation, mainly checking whether the virtual network card and VirtualBox network settings are added and whether the status is normal. Ignore the process. After finding that everything is normal, eliminate this cause.
Then open VirtualBox and try to run the AR_Base virtual machine manually. It turns out that it cannot run and it shows that the new task cannot be run. The error message is in English, which probably means: there is a running hyper-v. Hyper-V software is not compatible with VirtualBox.
Therefore, the solution is to completely shut down all Hyper-V services or functions. However, this complete shutdown took a long time on the Chinese version of WIN11 Home with Hyper-V installed:
The first is to turn off hyper-V using the command line in CMD administrator mode: bcdedit /set hypervisorlaunchtype off. Restart and run the AR_Base virtual machine, but it fails for the same reason.
Then check the windows function, close the relevant virtual machine and hyper-V (cannot be seen in WIN11 Home Chinese version!!), restart, and run the AR_Base virtual machine, but it fails with the same reason.
Then check the windows services, stop all services related to hyper-V, and change to manual. Restart and run the AR_Base virtual machine, but it fails for the same reason.
Finally, I checked the system information and found that after the above operations, virtualization-based security displays the running status. The picture below is the result after I closed it. As long as it is in the running status, VirtualBox will fail to start the virtual machine and report an error hyper-V. , so it needs to be closed.
The reference here is the ultimate solution of this master, use Microsoft's official tool to turn it off: dgreadiness_v3.6:
After shutting down and restarting, to be on the safe side, I ran bcdedit /set hypervisorlaunchtype off again and checked the services. After restarting again, I successfully entered the login interface by running the AR_Base virtual machine. After shutting down the virtual machine, I opened eNSP and successfully started the device. The network is also running normally!
I will share my method later: After using dgreadiness_v3.6, I turned on memory isolation and found that it was different from the state before I used it. The difference is that firmware protection was turned on before, and I used dgreadiness_v3.6 to turn off "virtualization-based Security" turned off, so I guessed that the effects of these two settings were the same, so I turned on the firmware protection again, restarted, and ran the AR_Base virtual machine. I found that it failed for the same reason. I checked the system information and found that "Virtualization-based security" is operational again. So I turned off the firmware protection and restarted, and it was successful! I checked the system information and found that "virtualization-based security" was not enabled.
This also confirms my conjecture, so you can consider this method to solve it without using tools.
