Open AKTheNoob opened 4 years ago
I don’t know why you guys keep asking what windows version it works on. The driver will work on any windows version... It depends how you map it which may require certain versions depending on what they hook (kdmapper etc).
If you sign the driver it’ll probably get blacklisted. And even if you do sign it why are you going to use shared memory? Just use regular IOCTLS, no point in trying to hide the communication if you’ve signed the driver.
I don’t know why you guys keep asking what windows version it works on. The driver will work on any windows version... It depends how you map it which may require certain versions depending on what they hook (kdmapper etc).
If you sign the driver it’ll probably get blacklisted. And even if you do sign it why are you going to use shared memory? Just use regular IOCTLS, no point in trying to hide the communication if you’ve signed the driver.
thank you for your quick reply, hope i didn't bother you..and what you said make sense :)
i attend to sign and use this driver for personal purposes with PUBG Lite PC so i was wondering if i will need a bypass! (NOTE about OBRegisterCallbacks) or the driver wouldn't be detected? 2nd, the question you never answered is which versions of W10 this driver will work with? only 1809 LTSC or 1903 just like the driver kit requires? or from 1703 up the way to 1909? (if the driver is signed and could be loaded on any version of windows, no kdmapper restricts) thank you in advance, i took a quick look at the driver and it's well written and organized with some premium features here such as handling all the features from kernel and no usermod communications, much loves <3