BlueStacks is stuck on engine splash screen
BlueStacks is one of the popular Android emulators which allows users to install and run Android apps on their computers. The application is completely free and available for Windows and Mac. You can download it from its official website. After installing BlueStacks, you can access Google Play Store directly from your Windows device and install all Android apps and games on your Windows PC. Occasionally, BlueStacks gets stuck on engine splash screen. If you have such a problem with BlueStacks on your computer, the solutions listed in this article may help you fix it.
To run particular software on your Windows computer, it must meet all the hardware requirements. You will also encounter this problem if your system is not compatible with BlueStacks. Therefore, before installing BlueStacks on your system, it will be better to check the BlueStacks hardware requirements from the official website.
BlueStacks is stuck on engine splash screen
If BlueStacks gets stuck on the engine splash screen and won’t go any further, you can try the solutions explained in this article to fix the problem. Before proceeding, we suggest you try the following quick fixes and see if they help:
- Restart your computer.
- Kill unwanted background processes and apps to free up RAM.
- Check if your system is running on the latest version of Windows 11/10. Otherwise, install the latest Windows 11/10 updates.
- Repair corrupted system files by running SFC and DISM scans.
If after trying the above quick fixes you are still facing the same problem then you can move on to the troubleshooting methods given below.
- Enable virtualization
- Allocate more CPU cores and RAM to BlueStacks
- Temporarily disable your antivirus
- Update your graphics card driver
Let’s see all these solutions in detail.
To use BlueStacks, your Windows computer must support virtualization technology. If your computer supports virtualization, you must enable it. Computers of different brands have different methods of enabling virtualization. After enabling virtualization, launch BlueStacks and check if it gets stuck on the engine splash screen this time or not.
2]Allocate more CPU cores and RAM to BlueStacks
If your system supports virtualization and despite enabling virtualization, you still face the same issue with BlueStacks, allocating more CPU cores and RAM to BlueStacks may fix the issue.
The following steps will guide you on how to allocate more CPU cores and memory to BlueStacks:
- Launch BlueStacks 5.
- Click the gear-shaped icon at the bottom right of the interface. This will open its settings.
- Select the Performance category on the left side.
- Click on the CPU Allocation drop-down menu and select a higher number of CPU cores.
- Now click on the Memory allocation drop-down menu and select a higher value to allocate more memory to BlueStacks. You can also select the Custom option to assign a custom memory value to BlueStacks.
Allocating the highest CPU cores and memory to BlueStacks will increase the performance of apps and games running in BlueStacks. But it will also increase the strain on your CPU and RAM. This may affect the performance of laptops with low specs, for example 4 CPU cores and 4 GB of RAM. In this case, if you run another app alongside BlueStacks, your system may crash or freeze. On the other hand, increasing the number of CPU cores and RAM for BlueStacks will not affect laptops with a good configuration, say laptops with 8 or more CPU cores and 8 GB or more of RAM.
Do not allocate all CPU cores and all memory to BlueStacks. When increasing CPU cores and RAM for a particular application, always select a value that is lower than the total number of CPU cores and RAM your system has.
3]Temporarily disable your antivirus
Your antivirus may interrupt the working of BlueStacks. To check this, first temporarily disable your antivirus software and then launch BlueStacks. If BlueStacks does not get stuck on the Start Engine screen, your antivirus is preventing BlueStacks from working properly. In this case, you can disable your antivirus while using BlueStacks and re-enable it after exiting BlueStacks.
4]Update your graphics card driver
You may also experience this issue with BlueStacks if your graphics card driver is outdated or corrupted. In such a case, updating the graphics card driver solves the problem.
When it comes to updating the graphics card driver, Windows 11/10 users have the following options:
- Installing the latest graphics card driver via Windows Optional Updates.
- Visit the official website of the graphics card manufacturer, download the latest version of the graphics card driver and install it manually on the system.
- Update the current version of the graphics card driver without uninstalling it via Device Manager. In this case, you need to follow the steps below:
- Right click on To start up and select Device Manager.
- In Device Manager, expand the Screenshot taken node.
- Right-click on your graphics card driver and select it. Update driver option.
- Now select the Automatically search for drivers option to allow Windows to automatically install the latest version of the driver.
This should solve the problem.
How to Fix BlueStacks Stuck on Startup?
The BlueStacks crashing issue on startup or initialization screen may occur due to a minor bug in the software. In this case, uninstalling and reinstalling the latest version of BlueStacks may fix the problem. Apart from that, you can also try running BlueStacks in compatibility mode and check its administrative privileges.
Why is BlueStacks not working on Windows 11/10?
If BlueStacks is not working on your Windows 11/10 system, you should first check whether or not your computer meets the minimum hardware requirements for BlueStacks. If despite compatible hardware, BlueStacks is not working on your system, you can try a few other things like enabling virtualization, updating your graphics card driver, etc. If nothing helps, uninstall and reinstall BlueStacks after downloading the latest version from its official website.
If BlueStacks won’t start when Hyper-V is enabled, you need to check and configure Hyper-V settings.
I hope this helps you.