Exetools  

Go Back   Exetools > General > General Discussion

Notices

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #3  
Old 02-25-2018, 21:27
chants chants is offline
VIP
 
Join Date: Jul 2016
Posts: 836
Rept. Given: 47
Rept. Rcvd 52 Times in 32 Posts
Thanks Given: 742
Thanks Rcvd at 1,148 Times in 531 Posts
chants Reputation: 52
The correct strategy is as far as I know to update to the vendor specific driver. PCI001 will be broken, so you go into device manager, do a "driver rollback", and it will go back to a working driver for that device only, and it will blacklist the new driver for that device. Probably some special exclusion registry key gets set on a per device basis.

Changing the .inf is not the right approach as you point out because of signing. Likely there is no automatic loading. What is most certain is the driver installation oversteps. So you have to let it overstep, then undo the damage on a device by device basis such as with a rollback.
Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
making patch hex editing in .net js78955 General Discussion 4 01-21-2015 04:26
editing Debug Information Directory in a PE file jonwil General Discussion 6 01-15-2005 06:18
Editing a .key file? peedizzle General Discussion 1 09-09-2004 00:49


All times are GMT +8. The time now is 20:11.


Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX, chessgod101
( Since 1998 )