Startup Issue with Palworld - cannot start after update

System Information

Field Value
Operating System Windows - Windows 11 Home on x86_64
Product AMP ‘Phobos’ v2.6.5.0 (Mainline)
Virtualization None
Application Palworld
Module GenericModule
Running in Container No
Current State Failed

Problem Description

Issue

I updated the Instance, but I cannot get it to relaunch at all, and updated the AMP Instance and everything, new update came out for the game and had me do an INSTNACE update, but it still wont do anything I need some assistance.
idk what it is but there is an thing that is wrong with some kind of files in the log files, but I dont know what is happening

Reproduction Steps

  • updated everything i needed to update the GAME, INSTANCE, and PC restart
  • restarted the pc
  • other servers started just fine but Palworld isnt starting
1 Like

im having the same problem here after the update. Code 3 exit in logs. I tried the same steps, updated amp, the instance, and restarted

same issue, exit code 3 in logs

I did do these steps, thank you! I even tired the .bat file stuff, and when that didnt work I hit the assistance button in the AMP application, I’m just kind of lost at this point

1 Like

In the same boat, followed same steps. I think the update overnight caused something to break, but not finding answers yet.

I was having the same issue. In the crash logs, there was an error that had the following text:

SECURE CRT: Invalid parameter detected.

This made me think it was a parameter issue - i.e. Palworld’s update last night silently disabled one of the command line arguments that was being passed in. After some experimentation, I discovered the option Enable Multi-Threaded Performance Improvements in the Palworld Server settings tab was the culprit for my machine. Disabling that allowed the server to start. You may want to try that.

4 Likes

That did the trick here - haven’t attempted to connect to it or anything yet, but it’s run for over a minute already. Nice catch!

1 Like

Did you manage to fix this?