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.
Related issues
is duplicated by
Attachments
Comments



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.

I have the same problem too.
Composition:
PC[Dell G3 3579]
OS[Windows 11 Home 22621.2361]
Minecraft[1.20.3101.0]
Symptoms:
In my case, it stops at 35% or 41%. The loading icon keeps moving or stops. In addition, the symptoms vary, such as stopping at the loading screen or forcing the game to close.
Also, (although this is just a feeling), Minecraft will successfully start up about 1 out of 10 times. When I succeed, I can play without any problems.
I checked the audio driver written above.
Installed drivers:
Realtek(R) Audio[6.0.9107.1(2021/01/19)]
I checked Dell's official page, but there was no update for this driver for my PC.

I have the same problem too.
Composition:
PC[Dell G3 3579]
OS[Windows 11 Home 22621.2361]
Minecraft[1.20.3101.0]
Symptoms:
In my case, it stops at 35% or 41%. The loading icon keeps moving or stops. In addition, the symptoms vary, such as stopping at the loading screen or forcing the game to close.
Also, (although this is just a feeling), Minecraft will successfully start up about 1 out of 10 times. When I succeed, I can play without any problems.
I checked the audio driver written above.
Installed drivers:
Realtek(R) Audio[6.0.9107.1(2021/01/19)]
I checked Dell's official page, but there was no update for this driver for my PC.

Hey i know how to fix that on my computer
its easy go to task manager open minecrafts tab and close the "runtime broker"
its works on me
please fiz that

Hey i know how to fix that on my computer
its easy go to task manager open minecrafts tab and close the "runtime broker"
its works on me
please fiz that

After I switch devices to the readmi note 9s, simply the minecraft did not work with keyboard and mouse which is strange since the keyboard and mouse work perfectly in other applications and even mesno in the chat. I have no locomotion, I have no way to do anything that a keyboard should do.

After I switch devices to the readmi note 9s, simply the minecraft did not work with keyboard and mouse which is strange since the keyboard and mouse work perfectly in other applications and even mesno in the chat. I have no locomotion, I have no way to do anything that a keyboard should do.

> go to task manager open minecrafts tab and close the "runtime broker"
I tried closing runtime broker, but the situation does not improve and the game cannot start.
The runtime broker starts immediately after starting Minecraft, so I tried deleting the runtime in the screenshot.
[media]

> go to task manager open minecrafts tab and close the "runtime broker"
I tried closing runtime broker, but the situation does not improve and the game cannot start.
The runtime broker starts immediately after starting Minecraft, so I tried deleting the runtime in the screenshot.
[media]

I had the exact same issue. Check out my comment in this ticket: MCPE-175138

I had the exact same issue. Check out my comment in this ticket: MCPE-175138

Go To Task Manager > Services > ClipSVC Right Click And Start (if It Stopped)
The Problem is Client Can't Connect The Server
(ClipSVC is Maybe Stopped)
ClipSVC Is The Conductor For Server

Go To Task Manager > Services > ClipSVC Right Click And Start (if It Stopped)
The Problem is Client Can't Connect The Server
(ClipSVC is Maybe Stopped)
ClipSVC Is The Conductor For Server

After setting up the sound as introduced by Tim Flick in MCPE-175138, Minecraft started working! I have the same symptoms.
NotAGanesh's starting the ClipSVC service had no effect.

After setting up the sound as introduced by Tim Flick in MCPE-175138, Minecraft started working! I have the same symptoms.
NotAGanesh's starting the ClipSVC service had no effect.

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.

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.

Still happenning on 1.21.1

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: