MTP do not use the Zadig drivers, need his own drivers, normally are installed by the O.S. (windows, linux, etc.) by default.
In general, on a Windows computer you end with several installed drivers for the Switch.
"Zadik ones"
Using the Zadig program you can add two generic drivers for two states of the Switch:
RCM mode, is the mode of the switch on the RCM state, waiting for the payload to be injected:
View attachment 339299
View attachment 339314
View attachment 339298
When you run Homebrew like Goldleaf, AtmolXL Installer, etc. the "
Homebrew Mode" is enabled:
View attachment 339301
View attachment 339316
View attachment 339302
"Windows Integrated Drivers"
When you full load the console, the HOS present to windows as:
View attachment 339300
If you Run DBI and then start the MTP Responder, Windows "see" a MTP device, the drivers should be installed by windows itself because MTP is a standard device/protocol definition.
View attachment 339303
View attachment 339304
View attachment 339305
View attachment 339306
, but in some cases windows don't do it.
As stated by
@binkinator before, YOU NEED to ensure what your computer "sees" the console even as a "unknow device" before try any solution. Test different cables and ports combination.
Then when you will be able to see a device connected start DBI and then start the MTP Responser. if you device manager shows a invalid device, try to
View attachment 339307
Select “Let me pick from a List of device drivers on your computer”. The list will show installed driver software compatible with the device.
View attachment 339310
View attachment 339311
Remove the tick of "Show compatible hardware", then select Standard MTP Device and on the right, select MTP USB Device
View attachment 339312
Then RESTART your computer and try again, now your DBI MTP device should work fine:
View attachment 339313