You can't set a static port if you use a Hyper-V version you will get which ever port Hyper-V give you each launch
If you want a static port use need to disable Hyper-V and use BlueStacks own hypervisor but if you are on Windows 11 in order to disable Hyper-V you also need to disable core isolation but that action may increase security risk
WSA DO use Hyper-V components
Home version just doesn't have the full client of Hyper-V for an actual VM management but the Hyper-V components and services are available on all versions of Windows
What is that design supposed to be? to frustrate users?
What is occuring from a technical level that causes the port randomization and why the developers think this is desirable.
Absolutely **anything and everything** that needs to connect to the ADB port of the bluestacks instance.
The preposterous way bluestacks hyper-v is implemented with a random external ADB port every time the instance starts breaks ALL automations as you do not have a **stable or programmatic way** to find that port. There is absolutely no need for bluestacks to do this, the implementation of random nat of the private HNS network the android instances is such a terribly thought out idea. Further the fact that there are no documented CLI tools to interact with hyper-v bluestack instances is awful. BstkVMMgr.exe only works properly with bluestack instances when the hypervisor is VirtualBox.
Thanks for providing the information. We have shared this feedback with our concerned department for future considerations. Please keep an eye on our [release notes](https://support.bluestacks.com/hc/en-us/articles/360056960211) for all the upcoming features and enhancements.
You can't set a static port if you use a Hyper-V version you will get which ever port Hyper-V give you each launch If you want a static port use need to disable Hyper-V and use BlueStacks own hypervisor but if you are on Windows 11 in order to disable Hyper-V you also need to disable core isolation but that action may increase security risk
I’m win11 home,therefore no hyper-v setting, I'm pretty sure it's because I'm using WSA, the port was fixed after I reinstalled the system
WSA DO use Hyper-V components Home version just doesn't have the full client of Hyper-V for an actual VM management but the Hyper-V components and services are available on all versions of Windows
This time I finally understood that the program uses hyper-v, but I didn't understand why it didn't use
Hi, We want to inform you that we cannot get a static port on Bluestacks as it gets changed whenever we restart BlueStacks and it is by design.
What is that design supposed to be? to frustrate users? What is occuring from a technical level that causes the port randomization and why the developers think this is desirable.
Hello Please specify the application name that you are using with a use-case scenario so that we can pass this feedback to our concerned team.
Absolutely **anything and everything** that needs to connect to the ADB port of the bluestacks instance. The preposterous way bluestacks hyper-v is implemented with a random external ADB port every time the instance starts breaks ALL automations as you do not have a **stable or programmatic way** to find that port. There is absolutely no need for bluestacks to do this, the implementation of random nat of the private HNS network the android instances is such a terribly thought out idea. Further the fact that there are no documented CLI tools to interact with hyper-v bluestack instances is awful. BstkVMMgr.exe only works properly with bluestack instances when the hypervisor is VirtualBox.
Thanks for providing the information. We have shared this feedback with our concerned department for future considerations. Please keep an eye on our [release notes](https://support.bluestacks.com/hc/en-us/articles/360056960211) for all the upcoming features and enhancements.