Hello Guys. Thx alot for the driver. i was searching for a working driver for ages. i get the same error 39 from george's driver. only the headset doesnt work. tried with trs and trrs on a xbox series x controller.
thanks for the report. i also didnt manage to get a headset working, but after my initials findings i decided it is the OS fault
So how to install now and which link works? I tried from @George King and got Error 39. Have a Series X controller
I think i know why the headset dont work. My Xbox series x Controller only work with an old xbox360 driver for win7. And this driver have no headset port support. I this case we need a new win 10 driver for the controller prepared for win7
today i got random bluescreen errors after connecting the controller to the wireless adapter. kernel power id 41 error. And i found out the adapter is gets very hot...
Thanks again for your feedback. BSODs didnt show up on my machines, neither with my nor with Georges drivers (it is the same anyway), but i didnt play for hours. As you can see in my findings about the differences between old and new official MS driver in the first few posts, part of the code changes are dealing with handling of Idle and Suspend modes. Therefore im not completely suprised about the temperature topic. Backporting the newer driver to be NDIS 6.20 compatible imho is not impossible, but sadly beyond my skills.
Hello kebapstorm, thanks for your attempt. Happy to see that my initial analysis wasnt that wrong In order to give your version a chance i had to fix or try out a few things. inf x64 section still had the 6.2 flag security cookie was unmodified replaced the mov eax, 0 before the SetOptionsHandler with the proper lea eax, nullsub Unwind_Info_HDR in Runtime_Function_Definition doesnt match anymore Therefore tried to include the stack handling before and after your check/GoTo OID Getting complete freezes / BSODs on every attempt.
Yeah, I didn't really do much except carving out the SetOptionsHandler func to house the redirected functions for checkhandlerex and ndismresetminiport. There is also another problem which I missed before, the NdisMSetMiniportAttributes function, as multiple structures there have changed their size/layout in 6.3, which would need to be replaced with their pre 6.3 counterparts. It can't obviously work when the structures aren't aligned properly and the data becomes garbage. About the security cookie part though, afaik it's function is just to be a stack guard/DEP guard? So if stack is handled properly it wouldn't need to be modified? the execution shouldn't ever reach the int29 fastfail anyway?
Ah okay, i thought it was more a beta-test than a first try Thats exactly the point where i gave up. Technically thats correct, but when i did my first experiments i ran into that problem all the time so i killed it immediately. But as we do have misaligned structures or changed function definitions i just wanted to rule out that annoying part.
I got the Bluescreens random between 2-4h every 5 session or so. Does something got changed? the signed driver from @egalerst doesnt work for me anymore. Also file got deleted at anonfiles. Could someone please reup?