Ah
Good to be back here after finishing that nasty medical licencing exam...
@Pretentious would you mind me fixing DSLIA with the new offsets you provided?
I'm also revisiting the patching process with your findings
EDIT:
After crawling through the thread I saw that @DonnerPartyOf1 had already...
The CA issue will never be solved since resigning the driver blob involves pulling off the original driver signature and will cause other driver components refuse to load.
Besides, resigning the driver blob with non-testsigning certs will seriously violate the EULA and will cause severe legal...
Can somebody kindly provide me an win7 driver file of 387.92
Discovered some crap in the os detection mechanism
Win7/8/8.1 users should use version 1.7.1 with 387.92 just fine
Meanwhile Win10 users please use the version attached to this post
I've also included an updated version of Install.cmd
I think I really should do a rewrite of this thing and add more dummy-proof functions like “your driver is too old!” or “please read the instructions THROUGHTOUT CAREFULLY ”
BTW, been trying another approach to live-patch the driver and avoid force driver signing
Tell me if you're interested in...
Please do a full cleanup and follow the instructions to install
Make sure you delete all diffsli certs form cert store before reinstalling
Did you load windows into testsigning mode?
Fix : Added OS Detection, seems that starting from 384.xx the win10 driver has a new pattern
Thanks bryllstyles for testing
File updated
----------------------------------------------------------
Update is here ft. my anatomy grades exploding...
Beware!!
Haven't test it on actual hardware...