Mr.Vince, when you use bootcamp you have a normal Windows with normal access to the hardware. All bootcamp does is prepare the hard drive, hardware drivers and the software that enables touchpad, boot menu. There is nothing emulated, especially in regard to USB hardware.
Ive tried directly connecting got to the MacPro 2013 USB on the back and also a Dell 30” Montiel that has a usb hub on it. Neither working.
For now the only option is to use bootcamp or a Virtual Machine with Windows.
MrVince, again, bootcamp is just a way to get a regular Windows booting on regular hardware. C'mon inform yourself before you say stuff like this. No bogus stuff and no messing with drivers needed...
It's emulating a BIOS within an EFI environment for example and it comes up with its own hardware drivers for USB. Over the years, there are several problems with usb ports reported which don't apear with "real" hardware (use google if you don't believe it)...
All theese issues, have nothing todo with DTC or Kryoflux! But they show that there are still difference in the way a real windows machine behaves in contrary to a bootcamp installation!
Apple is doing a bit like Commodore back in 1985 when they said the C128 has a C64-modus built in and every C64 program will work
FYI: my daily driver is a Mac, so yes, I know how it works. I know what's great and I know about its shortcomings.
I don’t understand why you can fix it to work with 10.12 and above? All my other usb/FireWire and thunderbolt devices work on my Mac except my Kryoflux
There obviously a problem as more users have complained about the exact same error when using anything above 10.12.
Is this MacOS 10.13/10.14 bug the the same or a different bug than the one that broke things in 10.11?
(I wouldn't know, the only Macs I have are PowerPC )
Could someone post the technical details of this bug, or post a link to it if is out there somewhere already? (I thought I saw a post about that a long time ago, but a bit of searching turns up nothing specific)