Cheat Engine

hamodi01 · How do I cheat? Reputation: 0 Joined: 07 Oct 2019 Posts: 5

Keep getting this error, custom compiled CE, haven't changed much though.
Compiled the dbk driver as 64 bit no signing, testsigning is on can load other drivers fine... don't know what to do

t328163 · Posted: Mon Oct 07, 2019 9:18 am Post subject:

this started happening after the new windows update? things internally might have changed and requires db to update the software driver.

Dark Byte · Posted: Mon Oct 07, 2019 10:15 am Post subject:

unload the old ce driver first.(run the kernelmodule unloader snd perhaps an actual reboot) If the released driver is loaded it won't talk to your selfcompiled CE

also, try naming it something else than dbk64.sys perhaps windows blocks it on purpose (rename it in dbk32functions or driver64.dat as well)

hamodi01 · How do I cheat? Reputation: 0 Joined: 07 Oct 2019 Posts: 5

so i made driver64.dat file in the same directory as my CE executeable,

BLA62
PL62
TL62
wtfdriver.sys
76543210
fedcba98

still doesn't work, was sure that the kernel unloader said no drivers found in registry before i loaded. Same problem though. Imo i cant delete wtfdriver.sys after i load it even though it fails until i restart pc, so it seems something is happening

Also tried to manualmap the driver on my own but CE seems to need to load it itself for it to work, wasn't able to find any code related to driver loading in the CE source

Dark Byte · Posted: Mon Oct 07, 2019 11:02 am Post subject:

and you're sure you're compiling the driver using the debug or release no sig ?

Release (with sig) won't work

And check with dbgprint from wininternals to see what happens

hamodi01 · How do I cheat? Reputation: 0 Joined: 07 Oct 2019 Posts: 5

Positive, nothing in dbgprint.

Edit: tried loading the driver with osrloader or process hacker and i get the error message "it is not possible to create a file that already exists"

Okay soo...., i did a fresh reboot, loaded DBK64.sys with osrloader, everything worked fine, however i then ran cheat engine and clicked the DBVM thing only to be greeted with the same message as before. Then i ran kernel unloader, and it said that it unloaded DBK32? not sure whats going on here.. Working with cheat engine 6.8.3 (public release) though so maybe i compiled it wrong or somth? not sure what i could have done, I've used this on 64 bit games so it cant be that i compiled it as 32 bit

Dark Byte · Posted: Wed Oct 09, 2019 3:51 am Post subject:

with dbgview you can configure it to record kernelmode dbgprint messages as well

Compile your driver in debug mode and check the output it gives

note: In windows 10 dbgview can not unload it's driver properly, so once it's running DO NOT close dbgview as the second time you run it it won't load.
If you do close it, rename dbgv.sys in system32 to something else first. And if all esle fails restart (DO NOT shut down and back on as windows 10 will save all drivers currently loaded to disk and load that back in memory if you do a shutdown instead of reboot making a shutdown useless to get rid of it)

hamodi01 · How do I cheat? Reputation: 0 Joined: 07 Oct 2019 Posts: 5

Dark Byte · Posted: Wed Oct 09, 2019 11:16 am Post subject:

Is there really no other messages besides loaded?

Try adding prints where it creates the device dos name,

Are you sure you didn't edit the driver? Also, let CE load the driver as it is responsible for configuring the registry before the driver loads