6 ms·

This also causes the most infuriating issue I've ever had with a controller and Windows 10. The "official" driver from the manufacturer hasn't been updated sinc

This also causes the most infuriating issue I've ever had with a controller and Windows 10. The "official" driver from the manufacturer hasn't been updated since a final revision in like Windows 7. Windows 10 offers a basic driver, but it's totally broken and the Windows driver constantly updates and overrides the old one. Anytime I want to play a game with this controller, I have to uninstall from device manager and install the old driver but ignore the restart. It works, for some reason, but as soon as the machine gets restarted, the driver is replaced and I get the yellow exclamation point in Device Manager again. Not a great workaround, but I'm glad it works for most things.

lousken 10y ago
I've had the same issue with my TV card. This troubleshooter fixed it for me https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-windows-10 https://support.microsoft.com/en-us/help/3073930/how-to-temp...
- dkonofalski 10y ago
  Thanks! I'll give that a try!
justin66 10y ago
> This also causes the most infuriating issue I've ever had with a controller and Windows 10. According to the text, it's designed to prevent the problem you describe: When the system looks for a driver to use for a particular piece of hardware, it ranks them according to various criteria. If a driver provides a perfect match to the hardware ID, then it becomes a top candidate. And if more than one driver provides a perfect match, then the one with the most recent timestamp is chosen. If there is still a tie, then the one with the highest file version number is chosen. I don't know where this is going wrong for you but both the file version and the timestamp are things you can manipulate on that driver file. Might help, although you're in trouble if the manufacturer's driver isn't a perfect match to the hardware ID.
- dkonofalski 10y ago
  It does, but I have to assume that the Windows version also is a perfect match for the hardware ID. Since the older driver from the manufacturer supports all the features, but the date is before June 21, 2006, the MS driver is used instead which is, essentially, neutered for some functions. The text shows that the driver is working as intended. The newer driver is being chosen automatically. The problem is that the newer driver is the Microsoft one. The sad thing is that I don't even know the Manufacturer of the driver anymore. It was painted on the controller and has since rubbed off and the driver file itself just shows up as "Generic Joystick Driver" or something like that. At one point, it got identified as an XBOX 360 controller. :(
  - justin66 10y ago
    I see what you mean. I just took a look at how you might go about tweaking the date on these files manually, either by tweaking an extended attribute or using a hex editor (I'm not sure) and it occurred to me... digital signing. I don't know, might be worth a try, but it might not work if the driver is signed.
    - chinhodado 10y ago
      Even if the driver is signed, can't you just ignore the signature error when installing it?
      - simcop2387 10y ago
        Yes, http://windowsreport.com/driver-signature-enforcement-windows-10/ http://windowsreport.com/driver-signature-enforcement-window...
  - syntheticnature 10y ago
    That driver must predate Windows 7, then, which was released in 2009. I've found drivers from Vista or before don't want to work with Windows 10 in some fashion anyhow (perhaps the 32-bit to 64-bit transition?).
snarfy 10y ago
Find the driver files and change the owner to 'TrustedInstaller' and then make them read-only by everybody. As far as I can tell the only way to remove a 'TrustedInstaller' file is in safe-mode.
deleted 10y ago
[deleted]

lousken 10y ago

I've had the same issue with my TV card. This troubleshooter fixed it for me https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-windows-10 https://support.microsoft.com/en-us/help/3073930/how-to-temp...

dkonofalski 10y ago
Thanks! I'll give that a try!

justin66 10y ago

> This also causes the most infuriating issue I've ever had with a controller and Windows 10. According to the text, it's designed to prevent the problem you describe: When the system looks for a driver to use for a particular piece of hardware, it ranks them according to various criteria. If a driver provides a perfect match to the hardware ID, then it becomes a top candidate. And if more than one driver provides a perfect match, then the one with the most recent timestamp is chosen. If there is still a tie, then the one with the highest file version number is chosen. I don't know where this is going wrong for you but both the file version and the timestamp are things you can manipulate on that driver file. Might help, although you're in trouble if the manufacturer's driver isn't a perfect match to the hardware ID.

dkonofalski 10y ago
It does, but I have to assume that the Windows version also is a perfect match for the hardware ID. Since the older driver from the manufacturer supports all the features, but the date is before June 21, 2006, the MS driver is used instead which is, essentially, neutered for some functions. The text shows that the driver is working as intended. The newer driver is being chosen automatically. The problem is that the newer driver is the Microsoft one. The sad thing is that I don't even know the Manufacturer of the driver anymore. It was painted on the controller and has since rubbed off and the driver file itself just shows up as "Generic Joystick Driver" or something like that. At one point, it got identified as an XBOX 360 controller. :(
- justin66 10y ago
  I see what you mean. I just took a look at how you might go about tweaking the date on these files manually, either by tweaking an extended attribute or using a hex editor (I'm not sure) and it occurred to me... digital signing. I don't know, might be worth a try, but it might not work if the driver is signed.
  - chinhodado 10y ago
    Even if the driver is signed, can't you just ignore the signature error when installing it?
    - simcop2387 10y ago
      Yes, http://windowsreport.com/driver-signature-enforcement-windows-10/ http://windowsreport.com/driver-signature-enforcement-window...
- syntheticnature 10y ago
  That driver must predate Windows 7, then, which was released in 2009. I've found drivers from Vista or before don't want to work with Windows 10 in some fashion anyhow (perhaps the 32-bit to 64-bit transition?).

snarfy 10y ago

Find the driver files and change the owner to 'TrustedInstaller' and then make them read-only by everybody. As far as I can tell the only way to remove a 'TrustedInstaller' file is in safe-mode.

deleted 10y ago

[deleted]