Updated to newest version of Minecraft Bedrock 1.20.30 and when trying to open game I am stuck at 41%. I have tried to uninstall and reinstall multiple times with no success. I have all of my drivers updated and my windows 10 is fully updated. No other games, programs or utilities are having issues. Also, when I close out of the game and try and start it back up it just sits there at 35% spinning.
Linked issues
is duplicated by 11
Attachments
Comments 25

I have the same problem with minecraft 1.20.31 loading the main screen often freezes at 35% on win 10 and when minimizing minecraft the game suddenly exits. And if I can enter the game it is quite laggy and sometimes it causes the sound of the device to be broken
I have the same problem with minecraft 1.20.31 loading the main screen often freezes at 35% on win 10 and when minimizing minecraft the game suddenly exits. And if I can enter the game it is quite laggy and sometimes it causes the sound of the device to be broken
Please close. Went on Dell Support site for Realtek High Definition Audio Driver update as Driver Boosters update causes issues for the driver and their driver for May 2023 is inaccurate. For those with Dell XPS 15 7590 the most recent update for September 2021 is the best update and will allow Minecraft to work again with no sound issues. Do not use an alternative driver updater and only use what is on Dell for Realtek Drivers.
Please close. Went on Dell Support site for Realtek High Definition Audio Driver update as Driver Boosters update causes issues for the driver and their driver for May 2023 is inaccurate. For those with Dell XPS 15 7590 the most recent update for September 2021 is the best update and will allow Minecraft to work again with no sound issues. Do not use an alternative driver updater and only use what is on Dell for Realtek Drivers.
The issue is still persisting. My game gets stuck at 30% loading.
Closing the runtime broker before the perpetual loading crashes my game does allow the game to load.
Please see the fix in MCPE-175138
I had exactly this issue, and this fix resolved the issue for me, fwiw.
Please see the fix in MCPE-175138
I had exactly this issue, and this fix resolved the issue for me, fwiw.
If you experience that this problem has returned with the January Windows 11 patching, you may need to reapply the workaround given in: