We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Hi Glenn and team,
Running Snappy Driver Installer Origin v1.18.0 on Windows 11 64-bit.
I’m getting a flagged update for an MTP Device that is actually working correctly. The tool suggests installing an older driver from the packs, but the current Microsoft driver is newer and functions perfectly with my tablet.
Device Details:
Manufacturer: Vortex
Device: T10M (T10M Pro Plus tablet)
Hardware ID: USB\VID_0E8D&PID_2008
Installed Driver: Microsoft (wpdmtp.inf) – Version 10.0.26100.8115 (6/21/2006)
Suggested Driver: MTP Device (Version 5.2.5326.4762 from 2/22/2016)
The tablet connects fine for file transfer (MTP) after the built-in Windows driver was refreshed. Installing the suggested driver would likely break functionality, as older MTP drivers are known to cause issues with MediaTek-based Android devices.
I’ve attached a screenshot of the SDIO window showing the details.
Would it be possible to improve the detection logic for MTP devices so it doesn’t flag the working Microsoft driver as needing an update? Or add this specific hardware ID to an exclusion list in future driver packs?
Thanks for all the hard work on SDIO Origin — it’s a great tool overall!
Screenshot of working device with installed drivers showing.
It's a good thing you follow the "3 Rules Of Windows Drivers".Hi Glenn and team,
Running Snappy Driver Installer Origin v1.18.0 on Windows 11 64-bit.
I’m getting a flagged update for an MTP Device that is actually working correctly. The tool suggests installing an older driver from the packs, but the current Microsoft driver is newer and functions perfectly with my tablet.
Device Details:Manufacturer: Vortex
Device: T10M (T10M Pro Plus tablet)
Hardware ID: USB\VID_0E8D&PID_2008
Installed Driver: Microsoft (wpdmtp.inf) – Version 10.0.26100.8115 (6/21/2006)
Suggested Driver: MTP Device (Version 5.2.5326.4762 from 2/22/2016)The tablet connects fine for file transfer (MTP) after the built-in Windows driver was refreshed. Installing the suggested driver would likely break functionality, as older MTP drivers are known to cause issues with MediaTek-based Android devices.
I’ve attached a screenshot of the SDIO window showing the details.
Would it be possible to improve the detection logic for MTP devices so it doesn’t flag the working Microsoft driver as needing an update? Or add this specific hardware ID to an exclusion list in future driver packs?
Thanks for all the hard work on SDIO Origin — it’s a great tool overall!
The installed driver date is June 21 2006 which makes it the default driver installed by Windows during hardware installation. I note it also has a version number that matches the Windows version.
ref: https://devblogs.microsoft.com/oldnewthing/20170208-00/?p=95395/
The suggested driver is shown because it has a later date despite having a lower version number. Everything else checks out. In this case it turns out the Windows installed driver works better than the suggested driver. This, obviously, is unknowable in advance, which is why we have the "3 Rules Of Windows Drivers"
This situation is not specific to MTP devices, it's one of those gotchyas that catch out the those who blindly update everything just because.
I've been thinking something along the lines of providing a tool to allow the end user to create an ignore list of hardware IDs.
Hi Glenn,
Now if only Microsoft would follow their own rules 😂 It’s exhausting — every clean install, no matter how fast I disable Windows driver updates, it still forces in all the Intel extensions. Even when the newest one should make the older three redundant, they stay loaded in the system and refuse to be fully removed.
Anyway, thank you again for the detailed explanation and the link — super helpful.
I was actually going to suggest something very similar to your idea. A simple right-click option like “Add this Driver to Ignore List” (tied to the specific driver version or update ID) would be fantastic. That way it wouldn’t keep surfacing the same suggestion on future scans, while still allowing newer updates to show up normally.
Would something like that be feasible on your end?
Thanks again for the great support!
Would something like that be feasible on your end?
I dunno, we'll find out in the fullness of time.
