In Bedrock Edition, the chat bar repeatedly displays the error message: "At least one resource or behavior pack failed to load."
This occurs in all scenarios – when loading a world, during gameplay, returning to the main menu, and even after a clean installation with no active packs.
The message appears regardless of whether any resource/behavior packs are installed or enabled. It cannot be cleared or dismissed. No actual pack loading failure is observed; worlds load and run normally except for this persistent chat warning.
Linked issues
is duplicated by 9
Attachments
Comments 13
This issue has been reviewed by our team.
Please add new, relevant information if it helps us understand or reproduce the issue. To show that you’re affected, use the vote feature rather than commenting.
If a fix is implemented, it will be listed in our official changelogs.
For major outages or urgent assistance, visit the Minecraft Help Center.
Also, it’s not always true, either. I keep getting it, only to find that the packs I’m using are working just fine.
Also, if this ticket is closed as a duplicate, what is the primary open ticket number so that I may track the suggested solution?
Same Issue Here - even removing all RP/BP folders and repairing game and clearing caches had it come up in a brand new vanilla world with no addons even in the game/global etc
Happened to me last night (BE v26.52 on Windows 11) on Oct 25. The red “resource or behavior packs failed to load” banner appears in brand-new vanilla worlds with no packs enabled. It started after Gaming Services app (Microsoft Store) updated during gameplay and the game crashed.
I found that it depends on %APPDATA%\Minecraft Bedrock\premium_cache. With that folder renamed, the banner disappears, but worlds using Marketplace add-ons lose their cached assets and show achievements disabled. With the original cache restored, assets and achievements work but the banner returns.
The Content Log from a fresh world load shows no pack, manifest, or dependency errors. This suggests the banner is a false positive tied to the cache state rather than an actual pack failure. Haven’t had any issues with packs in testing.