That means if you are trying to create 20 instances, you'll need to set up 4 of them manually.Īnyway, hope these help! If you have any other tips or tricks to get around these silly networking or cloning issues, please share them! Instead, I try to create a new Fresh Instance, set it up manually, then clone that no more than 5 times. You can try cloning one of the original cloned instances, but YMMV. Did you clone an instance 5 times? Did you then try to clone it another 5 times? Don't do that :) After you've cloned an instance 5 times, any further clones will conflict with the original. If you clone instances too much, you may notice that some instances can't run at the same time as others, but can run when their counterpart is stopped. Change the last part of that port range to increase it, ie make it `2860-2999` & apply.Ĭan't run some cloned instances simultaneously.You should see the `Local Port` set to `Specific Ports` with a value of `2860-2XXX` (i forget the value). To fix this, we need to increase the port range. When trying to run more than this, the Bluestacks runs out of the ports that it has allowed through the firewall. It seems like the default limit is about 10. This often happens if you are running a bunch of instances. Does that mask match the one we saw in Step 3? If not, remote that entry and add the correct one & Apply. 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:

Bluestacks hyper v cannot start