The "rogue issue" isn't a insubstantial ghost. There is something going on that's causing the issue you've essentially ruled out the Vive hardware. It's also not fair to compare simple USB devices with Vive. There's so much more going on than that. The GPU, the ports, the drivers, the firmware and the software all have to be working in concert and the Vive itself is acting as a USB Hub for all it's components as well. You should always be installing software you want as an administrator. If you don't do that, Windows UAC may block key files from running. If you have anti-virus programs or firewalls set up, they might block features as well. Third party software for policy management or custom drivers could cause problems. The point I'm getting at is that it would be impossible to test for all conditions and all possible software configurations. Error 108 headset not detected broadly breaks down into two possible culprits: 1) There is an issue with the headset: E.G. the headset is broken, the cable is broken, etc. If you can connect it to another computer and it works, then that isn't the problem. It's relatively easy to rule out Vive itself as the problem. 2) The other possibility is that something with the OS or PC is broken. Bad drivers. Bad ports. Conflicting software. User Access Control permissions. There could be hundreds of possibilties. Thousands, really. At that point, if the culprit is #2 then we've already ruled out Vive and the problem exists locally on the PC. If you can test the ports to work then it's probably OS/Software related and we'd need to reinstall SteamVR, or maybe the drivers. The quickest most certain solution though, is a fresh OS install. That covers all your bases. To summarize this, it's either something with the Vive kit or something related to the PC. If the Vive consistently fails across all PCs, it's probably the Vive. If the Vive works, but a PC consistently fails to run any Vive, it's the PC. There isn't really a middle ground. Thank you, -John C