Incompatibility between a virtual USB host controller and Intel USB 3.1 extensible Host Controller

After installing a remote USB host controller (virtual) on Windows 10, one of my two native USB controllers fails with a Device Status of:
“This device is not working properly because Windows cannot load the drivers required for this device. (Code 31). Object Name already exists”.
If I disable the remote USB Host Controller, it works. Interestingly enough, there is also a second Intel USB 3.1 extensible Host Controller which works fine. It looks like it’s a naming conflict, but I’m not sure where to look to pinpoint it. It’s a production machine so I cannot break into it via Windbg. Any suggestions on how to pinpoint the problem?

If i had such a problem i would check Object Manager \GLOBAL??\HCD* first and where these symboliclinks point with and without “remote USB Host Controller”.

You checked the system even log already I assume?

Peter