Quote:
Originally Posted by knc1
I read that you tried removing/de-installing the device -
Have you tried removing/de-installing the custom driver (the info file).
Perhaps your recent update included a change to the MS included driver that creates a conflict.
Hmm...
Does your version of Windows still keep a detailed log of all changes made by an update of the system?
If so, perhaps there is something helpful in the list of things the update touched.
Does your version of Windows still set a 'restore point' just prior to begining any update changes?
If so, perhaps rolling back the system to that restore point would get you back to the behavior prior to Windows self-destructing.
Or perhaps you just need to update the OS information in the signed driver -
See second post of this thread, step 3.
Consider what I suggest very carefully, my Windows experience is very, very old.
|
Thank you for your response. In the meanwhile I got it working. Unfortunately, I did not protocol the steps I did. Somehow it started working. I do not know what exactly made the difference. But evidently I did something wrong in my previous trials, and did it correctly now by chance.