I know it's not the best solution, but before Hyper-V Beta I worked with this solution without any problems. Same for "runBluestacks.ps1", after rebooting you are able to use Bluestacks. Now if you want to use WSL2 run "runWSL2.ps1" shortcut, after rebooting you can use it. Go to preferences of each shortcut and add to path: powershell -f "YOUR_PATH_TO_FILE" for example: powershell -f C:\Users\username\Desktop\runWSL2.ps1 In installation progress of Bluestacks Hyper-V beta gave permission to current user for Hyper-V.Īlternatively, if it won't nothing work you can turn hypervisorlaunchtype off / auto (I did this before the Hyper-V version of bluestacks): In the detail window, locate the following entry: A hypervisor has been detected. I disabled Windows-Hypervisor Platform & activated WSL2Īfter rebooting I installed BlueStacks Hyper-V (BETA) Original KB number: 3204980 Determine whether the Hyper-V hypervisor is running To determine whether the Hyper-V hypervisor is running, follow these steps: In the search box, type msinfo32.exe. Once your PC restarts, Hyper-V will be disabled and you can now use BlueStacks 5. Please click on 'OK' to restart your PC so that the changes can take effect. My CPU (Intel HD Graphics 4000) don't support Virtualization Technology, but still working. After the process is completed, you will see a pop-up that requires you to restart your PC, as shown below.
It's working for me, too (Windows 10 Home).
0 kommentar(er)
