Palworld Errors and Fixes: Crashes, Launch Issues, and Server Problems

Palworld is preparing to leave early access, but players may still run into technical issues: crashes, black screens, connection errors, server failures, and co-op bugs. For example, some players get a black screen on launch, others crash with an Unreal Engine error, and some users cannot connect to a world or a dedicated server. In this guide, we have collected possible problems and errors, as well as ways to fix them.

After major updates and the release of version 1.0, some old errors may return due to the influx of players, network changes, and heavy server load. Before trying more complicated fixes, first check the server status, game updates, and file integrity.

Before launching Palworld, check the system requirements and make sure the game is installed on an SSD. If your system does not meet the minimum requirements, the game may not run correctly or may fail to launch at all. Check this before looking for other ways to solve the problem.

The Not Found Session 91 error code can appear when a player tries to connect to a server that no longer exists, a closed world, or a session where multiplayer is not enabled. You can fix it by connecting to a different server or contacting the host and asking them to check the co-op settings.

If you have confirmed that the server you are trying to connect to is running and stable, check whether the Multiplayer option is enabled for that server.

If Multiplayer is enabled but the error still appears, check your network connection.

If you are connected to the internet through Wi-Fi, we recommend switching to a wired connection and checking whether the problem still occurs. Otherwise, try restarting your modem or router to restore the default connection state.

Xbox players in Palworld who try to return to worlds they created may encounter the "Failed to Host Multiplayer Session" error. In most cases, it is related to the network session or multiplayer settings. As a temporary workaround, you can disable multiplayer for that world and try entering it again.

Sometimes, after joining a world again, your character may spawn in water under the map. In this state, you will not be able to get back to shore and will remain stuck in the water. To fix the problem, simply end the game session and try launching it again. If that does not help, turn the Multiplayer setting on or off in the world settings. You can also try re-entering the game.

Your camp will be attacked by enemies regularly, but sometimes Pals do not leave combat mode even after the fight ends. They may simply freeze in place while the red icon above them keeps flashing. Below, we explain why this happens, how to avoid it, and what to do if you have already encountered the bug.

Based on our observations, the bug can happen if you quit the game during a raid. This lets you avoid the battle itself, but when you return to the game, you may run into this problem. The Pals will just stand still and stop doing their jobs. In this state, they may not even be able to reach the feed box to satisfy their hunger.

Conclusion: do not quit the game during a raid. It is better to put all your Pals into the Palbox and use fast travel to the nearest fast travel point. The enemies will have no one to attack, spend some time at the base, and eventually leave.

If this has already happened, first try putting the stuck Pals into the Palbox, returning them to the base, restarting the world, and checking whether buildings or the path to the feed box are blocking them. If nothing helps, you can try the last-resort option: destroy the Palbox. Along with it, some objects will be removed from the camp, such as rest areas and other Pal-related structures. If the bug persists even after restarting the world and moving your Pals, check whether a new patch is available, and try moving base structures or temporarily disabling base raids in the world settings.

The "OnCreateSession Complete Delegate bWasSuccessful == false" error is usually related to creating or connecting to a network session. As a temporary workaround, you can disable Multiplayer in the world settings and enter in single-player mode. If you are playing on a server, also check its availability, game version, and connection settings.

Some users encounter a black screen when launching the game. Nothing happens afterward: there are no crashes or error messages. According to player reports, the issue is more common in the PC version of the game. To fix this problem, you can try some of the tips listed below.

Sometimes, during the first launch, the game may stay on a black screen for a long time. Wait a few minutes, especially if Palworld is installed on an SSD and is launching after an update. If the screen does not change for too long, move on to the next methods.

In the Steam version on PC, changing compatibility settings can sometimes help. Here is what to do:

If the previous recommendations do not help fix the black screen when launching Palworld, you may need to verify the integrity of the game files in Steam. To do this:

Another way to get rid of the problem is to reinstall the game on an SSD. Completely uninstall Palworld from your computer through Steam, then choose an SSD as the installation location.

The final recommendation that can help fix the black screen on launch is to install the latest graphics card driver or completely reinstall the driver.

You can also check for updates using NVIDIA GeForce Experience or AMD Software: Adrenalin Edition. To do this, launch one of the apps, go to the Driver tab, and click Check for updates.

A small number of PC players get the "UE Pal Crashed — Exception Access Violation" error while playing Palworld. In most cases, this error is followed by a crash to desktop, meaning the game crashes and closes. There is no universal fix for this error, but it is usually best to start by verifying game files, updating your graphics card driver, disabling overclocking, and fully reinstalling Palworld. File verification and repair are available in both the Steam version of Palworld and the Xbox/Game Pass version on PC.

The BP Class Human Error Pop Up may appear after you catch a Syndicate Thug, then approach him and try to view detailed information. In practice, the error is harmless, since all you need to do is press OK to close the dialog window. After closing the window, the Syndicate Thug model may disappear.

Many Palworld players have encountered the "No password has been entered" error when trying to connect to a co-op server, even while using the password set by the server owner. The issue has been known since the early access period.

If the error still appears, check whether the password is correct, make sure the server and client versions match, and try temporarily switching the server to community server mode if that works for your game. This workaround lets you play with friends on a password-protected server until an official fix arrives.

Connection issues in Palworld are most often related to an unstable internet connection, different client and server versions, port settings, or temporary server load. Before playing, make sure your internet connection is stable. If you are using Wi-Fi and run into problems, try a wired connection through an Ethernet cable.

If you are playing on PC and errors appear after installing updates, verify the integrity of the game files.

Dedicated server requirements:

If you want to play on private servers in Palworld, first read the official technical guide from the developer. It describes the full requirements for creating a dedicated server. If you have setup problems on PC, check whether your computer meets these requirements. The same guide also contains instructions for port forwarding.