patatkoning

It's working for me now. The 1.2GB Cosmos download still gets interrupted (but it I saw it actually downloading now) by Steam starting and the guide starting, but I did notice it was still running in the background due to CPU usage. After a while I got a popup saying that it was done installing. The VIVE console no longer shows an error and the headset booted up fine 🙂 So my theory is that it's supposed to download the bigger software in the background, but because the servers weren't working properly it was too slow and/or never got completed. Now that they do, it seems to work fine, just make sure you wait for it to finish before turning on the link box. Hope the same goes for anyone else experiencing the issue.

Nogal "dikke pech" ja 😛 Got this one from CoolBlue, full price even. I can send it back, but I really don't want to until I know for sure it's a faulty unit and not something on my end. I'll hopefully cover some ground tomorrow. If I find something that works, I'll be sure to post it, but I can't fix the software if the problem lies there. I also just noticed that the VIVE console doesn't report a version number:

I am experiencing the same (I think). I can't get the cosmos to start up. Opening the VIVE console only gives me a 205 error with no possibility of waking up the headset, no matter how much I clear or restart it. The light on the cosmos stays red all the time and I've only seen it turn green for a very brief moment once. Pairing controllers works fine. The 1.2GB cosmos software download also doesn't start/complete, but the former one (which is about 600mb) does. I didn't think it was much of an issue but here I am with a useless headset. I also don't notice windows installing any device drivers - there's no popup in the task bar or anything but USBDeview does show the USB devices but they all use the regular windows drivers from 2006. I did notice that connecting the headset and turning on the power enables most USB devices, but the audio ones disconnect short thereafter (also reflected in USBDeview). Surprisingly, it does seem to work for as short as it does as the audio sometimes does come through the headset and then immediately disconnects again. If the cosmos drivers indeed are not downloading then I hope this gets fixed, but if it's somehow related to my mobo/usb ports then I'm afraid I'm screwed. I'm going to try and disable overclocking and flashing the bios tomorrow to see if that helps anything, but the 205 error seems to signify that something in the software is not working as intended. I'm running Windows 10 1909 on a Vega 56 and a MSI Hawk B450 mobo with a Ryzen 2700 OC'd to 4ghz. Haven't had any USB or system problems before and Windows MR worked perfectly fine.