https://bugs.winehq.org/show_bug.cgi?id=35903
--- Comment #19 from Zebediah Figura z.figura12@gmail.com --- I'm not sure we're running the same installer, because mine (which I downloaded from the link in the URL field) is behaving differently. I don't have the relevant device, but I don't think the installer is checking for it. Instead, it copies an INF file into the C:\windows\inf directory:
04bc:04c0:trace:setupapi:SetupCopyOEMInfA "C:\1401\WinDrv\CED_1401.INF", (null), 1, 8, 00000000, 0, 00000000, 00000000
When the device is plugged in (or the prefix started, which may require shutting down the prefix first), that INF file should be picked up by our Plug and Play manager.
However, I don't see any such calls to SetupCopyOEMInf() in your log, but I do see an attempt to enumerate the USB device, which I don't get. It then seems to be trying to install the same INF file through difxapi, which is a stub.
Does your sha1 match?
hazel@watership:~/Downloads$ sha1sum winsupp.exe 8081a20bbc0c9b99f37b98a823ce07ab25f15e9d winsupp.exe