v6.6.1

v6.6.1 — Atomic hook install (crash test build)

What changed

Every hook is now installed with all game threads suspended for the duration of the write (suspend → write the JMP → resume), instead of writing it while the game runs freely.

Why

A crash minidump from a v382.893 user showed the game dying with 0xC000001D (illegal instruction) — the CPU executed an invalid opcode in a hot code path. The most likely cause was a non-atomic hook install: the trainer overwrote a few bytes of a function the game calls every frame, and the CPU ran the half-written instruction. Suspending the game around the write makes the patch appear atomically, the same way established hooking libraries (MinHook, EasyHook) do it.

What this build tests

This is a focused experiment to settle the crash cause:

• If the crash is gone → the non-atomic install race was it. Fixed.
• If it still crashes the same way → it's something else (e.g. anti-cheat reacting to the modified code), and we move to a data-write-only approach.

Please test (especially v382.893 users)

1. Download and extract the zip.
2. Run FH6AllInOneTrainer.exe as Administrator.
3. Start Forza Horizon 6, load fully into the world, attach.
4. Enable a cheat (e.g. Drift Score Multiplier) and play for a few minutes.

Reply with: did it crash (and after how long), which cheats worked, and your game version + platform (Steam/GamePass). If it still crashes and you can grab the Exception Code from Event Viewer (Windows Logs → Application → the forzahorizon6.exe error), that pins it down completely.

This is a pre-release.