You will likely see `These IP address` selected, with a single IP mask entered. Go to the `Scope` tab and look in the `Remote IP address` list.Click `Inbound Rules` and look for a rule named `BlueStacks Service Hpyer-V` - double-click it.Press Start and type in `Firewall` - open Windows Defender Firewall.In the details, you'll see the IPv4 address and subnet mask for this adapter.You should see an entry for BluestacksNetwork - ie, `vEthernet (BluestacksNetwo)` - right click -> status -> details.Press Start and type in `Network Connections` - open View Network Connections.However, it often gets this wrong! I don't know why, but I do know how to correct it :) The official help docs give some cut/paste firewall rules that you can try from the CLI, but they don't work if your virtual network ended up in a different IP network. The instances need to be able to communicate with the host process, so the installer attempts to permit this by adding a new rule to the Windows firewall.
Hyper-V creates a private network for VMs, and BlueStacks creates it's own second private network. This is usually due to a problem with how the BlueStacks installer configures your firewall.
Can't run some cloned instances simultaneously.But the problem still persists, Bluestacks won't start and Arch kept crashing.I've been struggling with Bluestacks Hyper-V startup issues and finally found a solution! There are three types of issues: So I decided to restore to a point that was a few hours ago, before all this emulator mess. All of them pointed that Hyper-V was enabled. I checked services.msc and also the BIOS. I checked Task Manager to see if virtualization was enabled. I tried reenabling it through cmd DISM and Admin Powershell. I did reenable the necessary Windows (10 Pro) features and rebooted it. The problem is Bluestacks began to fail to recognize that Hyper-V is enabled and my ArchWSL2 instance started to crash on startup. So I uninstalled it completely with Revo Uninstaller and reenable Hyper-V from the control panel.
Instead it just disabled it, but apparently in a somewhat harmful way I will soon discover. I checked and it did, so I assumed repair would allow Memu to run with Hyper-V. I searched around online and found that Memu is able to run with Hyper-V if Program Files\Microvirt\MEmuHyperv exists. Memu however said that it wont work with Hyper-V enabled and told me to repair. Bluestacks handled it fine and was able to run. Some of the recommended ones were Bluestacks (v4.260) and Memu (v.7.3.3), so I installed them. I wanted to try Android gaming emulators on my PC.
0 kommentar(er)
