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.I've been struggling with Bluestacks Hyper-V startup issues and finally found a solution! There are three types of issues:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |