11-03-2017 03:57 PM
I haven't been able to. I'm wondering if it's something with the OS. Could you do a re-install or set it up on another computer to rule that out?
11-09-2017 01:19 PM
Are you 100% certain it's not the cable? It could be the USB isn't working and that's why. At least, it seems that way.
11-09-2017 11:38 PM
How sure can one be? I got a whole new 3-in-1-cable and if it was that before, it should not be broken again. I bought a new USB-expansion-card and also a brand new USB-cable. The only thing unreplaced is the HDMI cable but I assume that has nothing to do whether the drivers are going to be installed or not.
Later today I will use a PC with Windows 10 from a friend and we will try that. If that does not work I will have to wait for Apple to finish their supposed AR-glasses in maybe 2020 I am afraid. Apple hardware just works.
11-10-2017 08:57 AMSolution
So I could not wait and did a fresh install of Win10. What can I say, the Vive gets recognized and I can now do the room setup.
Thanks, but HTC should really point out that Win 7 is not fully supported/suitable.
11-10-2017 09:42 AM
We're not aware of any Windows 7 compatibility issues. We have test machines set up here and customers who use Windows 7 without any issues. Sometimes a fresh OS install does the trick, for whatever reason.
11-10-2017 02:36 PM
I actually prefer Win 7 to Win 10 for my personal VR installations. I think in this case, it's specifically that there may be an issue with that specific installation of Windows. Windows (and iOS installs for that fact) become very complex and messy after usage. Things like drivers and registry entry become complete messages through the course of daily usage. Windows generally isn't very friendly with how it handles updates. I personally reinstall my OS'es every 3 months (both Win and iOS) because it provides the best user experience and in many cases I've fixed SteamVR errors by simply reinstalling the OS.
11-27-2017 09:14 AM - edited 11-27-2017 10:41 AM
Same problem here.. extremely frustrating. It's been plaguing our production for months across 3 totally different pcs (windows 7/10). No rhyme or reason. Nobody at Vive has any helpful advice beyond the same suggested solutions found online. All of which fix nothing. This post says solved?? What was the solution? I see no happy ending. For us it's just hours spent mindlessly unplugging crap hoping it'll come back on, somteimes it does for a while. Believe me, we've tried the smart methodical approach, each failure leading to less reason to live.
I don't recommend using these in a professional situation. We have clients, and right now we're scared **bleep**less about this happening on their installed VR machines. Sometimes my boss will say hey, we have this world leader client visiting from overseas. Let's wow them with our VR. The drumroll never stops, no symbod gets crashed. And I walk away feeling totally awesome.
11-27-2017 12:35 PM
My first experience of the error 108 was solved by installing Win 10 (maybe a fresh install of Win7 might have done the work too), so I marked this as solved. Unfortunately it is not possible to unmark this because the „solution“ lasted one or two hours max. Since then:
Hope you have better luck than me.
01-18-2018 06:14 AM