Borderlands: The Pre-Sequel Message Board  

have you set the exclusions in your anti-virus software?

I've been having similar issues (trainer closing) when I run the trainer without administrator mode. When I run the trainer as an administrator, the trainer gives me error during activation about health AOB. The trainer is in an excluded AV folder.

I think the game was updated because the game version on the exe is different than the version on the trainer. I reported in the trainer update notification system, but so far it says I am the only report. Bummer!

[Edited by cheatingjohnny, 3/31/2022 7:36:29 AM]

Yeah, I have allowed it, when I press F1 I hear please wait then the trainer disapears. I did look in the event viewer and it just shows up that there was a crash with ntdll.dll and the ~CheathappensTrainer2543.tmp file. I'm using Windows 11. Also it says something about FTH.

[Edited by mazzy2u, 4/8/2022 10:03:36 AM]

[Edited by mazzy2u, 4/8/2022 4:04:59 PM]

I'm having a similar bit of trouble with this.
F1 @ main menu > trainer waits a few seconds then just closes. > Re-run trainer > F1 @ main menu and I get the following error text:
~CheathappensTrainer4829.tmp Information: 0 : Borderlands Pre Sequel, 1.0.94.1838608, STEAM
~CheathappensTrainer4829.tmp Information: 0 : Trainer version: 1.107
~CheathappensTrainer4829.tmp Information: 0 : Trainer is up to date.
~CheathappensTrainer4829.tmp Information: 0 : Attaching to process: BorderlandsPreSequel
~CheathappensTrainer4829.tmp Information: 0 : Successfully attached
~CheathappensTrainer4829.tmp Error: 0 : health: Cannot find aob!

I can confirm I've done the usual suspects in excluding the trainer from AV, running trainer and/or game as Admin, alt-tabbing out to trainer for F1. Fresh install of game, freshly downloaded trainer. Even ran the old Purge CH script to clear our temp files etc. No joy.

Anyone got any ideas? Or is there anything I can do to help narrow down the problem further?

@cheatingjohnny - Also posted for an update for the same reason, the exe version seems different (don't know how to tell in-game) but have been told it works fine. Will keep hunting for something on my end and report back.

[Edited by SLyric, 4/25/2022 3:19:09 AM]

EDIT::
I've also tried downloading the Trainer fresh, using a fresh install of Borderlands TPS after having purged all files in the game install location and the following folders:
C:\Users\USERNAMEHERE\AppData\Local\Temp
C:\Users\USERNAMEHERE\Cheathappens\Work
C:\Users\USERNAMEHERE\AppData\Roaming\Cheat Happens\0x90
C:\ProgramData\CheatHappens
C:\ProgramData\CheatHappens Temp

Still the same behaviour. Not working.

[Edited by SLyric, 4/25/2022 12:19:58 PM]

EDIT2: Same behaviour for both Steam and Epic releases.

[Edited by SLyric, 4/25/2022 1:39:46 PM]

Originally filed report that game had been updated, but was told that the game hadn't been updated and the trainer was still working normally for the individual that responded. Using whatever the latest Steam version is. My meta data shows:
File ver: 1.0.155.39227
Prod. ver: 1.0.155.2464059

Current trainer is listed as for 1.0.94.1838608

Reproduceable error, trainer crashes the first time I attempt to activate it. Relaunching the trainer and trying to activate a second time works, but reports that the health value cannot be found. Inf. Health cannot be "activated" until after I take damage.

Following items do not work at all:
All editor functions
Inf. Health
Inf. Shield
Unl. Ammo
Save Pos./Teleport/Undo Teleport/Tele to WP
Super Speed
Super Jump
Unlimited Action

Following items do work as intended:
No Recoil
Unlock Golden Chests

Did not test infinite O2 or mission timer.

With a bit of help from some lovely people in the Discord, I've tried much of everything in the CH trainer troubleshooting thread.

I've also tried a few things of my own, such as overriding the application exploitation protection for both game and trainer.

Sadly still get the same 1st = crash , 2nd = AOB error.

I can see a Event 1000 in the application logs showing an access violation error todo with ntdll.dll or ch-lib64.dll (it seems to always be one of the two). And I can see a bunch of "locked with only readers" events from a procmon capture as the trainer's .tmp cycles through a bunch of .dlls.

Could it be a weird Windows 11 difference? Some sneaky security feature? Just a different way of structuring information in the registry maybe? I don't know as I don't know what a "good" call is supposed to look like (understandably, I'm not in the trainer making business).

So as it is, I'm stumped. If anyone works this out or has another thing for me to try, I'd be happy to hear it!

I'm glad I am not alone in all this. Lately I've been wondering if this is a Windows 10 vs 11 thing also. I only have access to Windows 11 at the moment, but I can install 10 on an older machine and see if it works. I might do that in the next couple of days and report back.

I'm getting all the same errors as described in the past few posts.

Edit: The trainer works perfectly with Windows 10. Looks like Windows 11 is the problem here. Not really sure how to solve that... Win11 doesn't let me run the trainer in compatibility mode set to Win10.

[Edited by cheatingjohnny, 5/5/2022 10:15:52 AM]

aah makes sense. Thanks for testing that out @cheatingjohnny. Spinning up a W10 VM for testing was on my TODO list somewhere but haven't got round to it yet. May still do that to see if it's a subtle change in registry or environment paths that's causing it.