Distinguish libwdi driver name from previous one. about libwdi HOT 4 CLOSED

it's always guesswork

It doesn't have to be. Just right click the device in Device Manager → Properties → Details tab and look for the Service property. There you will find if it's libusbk (libwdi installed driver) or something else (native driver) which allows you to identify which is which.

Also the device description you provided in libwdi (which can be changed by the user during installation) should appear somewhere in the properties, and I'm not sure what exactly you believe can be changed by libwdi, when a lot of what appears in the Device Manager is decided by Windows on its own, according to the USB device descriptors. There's no Windows API allowing you to "tag" a driver, and the best you will get as a "tag" is what I described above.

I will now close this issue.

from libwdi.

Mhh, I guess I couldn't explain good enough.
I'm talking of this window.

And when I said "tag" I just meant something in the name so that I don't have to, indeed, guess what's what.

from libwdi.

Have you tried modifying the proposed name in Zadig/libwdi?

I am not sure how you install your libusbK driver - libwdi is only a library that applications can use to install drivers. It already offers the possibility to change the driver name. If you use Zadig , which is the user facing application I provide, you will have a field that you can edit to set the name, and I would expect this to be reflected in the dialog you show above. But if you don't use Zadig, then you will have to contact whoever created the libwdi based driver installer application you use, because it'll be up to them to allow you to edit the name. And, no, I will not add default driver name tagging in libwdi, because very few people need to differentiate 2 drivers, and it would be out of place for libwdi to add its mark here and there as it could break applications that rely on looking up the default driver name.

Again, please try to uninstall your libusbK driver completely (make sure the driver files are deleted) and then reinstall it using Zadig while making sure you edit the driver name in the Zadig interface when you install it. Then check what you get in the dialog you showed above.

from libwdi.

I didn't ask for default driver name tagging, and I don't see how applications would look for a driver instead of the OS interface, but thanks for replying.
I'll ask whoever in charge.

from libwdi.