[2022] LE:13 Authentication failed - PC freeze

Hello there!

I’m sorry to hear you’re suddenly running into these issues. I had a look into the account side of things, and everything appears correct there. Can you include some log files to have a look at?

• Any files stored in C:/Users/YOURNAME/AppData/Local/Temp/Eleventh Hour Games/Last Epoch/Crashes
  • If you can’t find the AppData folder, follow this guide
• Your Last Epoch log file if the above directory is empty
• Your system information

This will help us see if your system is reporting any sort of errors, and what the client is trying to do behind the scenes when this happens. Considering it was working fine just two days ago, there would certainly be interest in anything that has changed since that point. If you’ve made any hardware or software changes, or if you’re running any sort of programs which may potentially conflict such as anti-virus programs which could have received updates, or been inactive previously.

For the game log file, it would be in a slightly different directory - C:\Users[username]\AppData\LocalLow\Eleventh Hour Games\Last Epoch\Player.log

I had a look through the files, and I think Vapourfire summed it up fairly well. Based on the heavily truncated player-prev.log, and completely missing player.log, alongside a login authorization failure issue strongly makes me think there’s an antivirus program which is preventing LE from communicating or writing to the PC. In addition to checking EventViewer, a couple of things I might recommend trying:

• Check any anti-virus program to ensure LE isn’t being incorrectly tagged and isolated
• Backup C:\Users[username]\AppData\LocalLow\Eleventh Hour Games\Last Epoch\ then remove the folder entirely. Then Launch LE with administrator privileges so it can try to re-create the folder. It’s possible there’s a corrupted settings or save file that it’s trying to read. Something may have changed with LE’s permissions to this folder. Note this folder also contains save file information, so it’s important to back it up first.

I’ve reached out to our technical and QA team as well to see if they can provide some more insight as to what may be going on.