Vive Headset not detected (108)

[SirBruce]

So I played with my Vive VR yesterday and all was well. I try to play today and woops! Headset not detected.... What happened?? Any help would be real nice.

- Already unplugged the linkbox
- Already changed USB ports
- Nvidia card is up to date
- Windows 10 is up to date
- Did all the troubleshooting on the Vive webpage

- Did not throw the headset threw the window yet...
- Did not slam it on the floor yet...
- Cursed a lot but it didn't work

[--ranXerox--]

unplug and replug power to the lighthouses, wait, then retry. make sure you have power going to the headset too.

[RustedDunn]

did you find a fix to this yet? I'm having the same problem. Not sure if it is related to an update, recent software uninstalled or what. Very annoying.

[SirBruce]

Update:
- I'm using HTC Vive headset
- I formatted my SSD and reinstalled Win10. Reinstalled everything from scratch.
- All is up to date
- Everything is plugged in right and on the first use of Steam Vr this is what I get:

"Please plug in your vr headset"

- Again I did all the troubleshooting I found on the web and issue is still not solved.
- I'm going CRAZY!!

EDIT:
This is my system report if it helps


SteamVR System Report created Sun Nov 03 19:48:26 2019

<Report>
SteamVR Version: 1.7.15 (1567818841)
SteamVR Date: 2019-09-06
Steam: Public
Steam Branch:
Steam AppID: 250820
Tracking: No Driver
OS: Windows 10
OS Version: 10.0.0.18362
Direct Mode Vendor: NVIDIA
Direct Mode Version: 441.08
Admin: No
Performance drops: 0/1 0/2 0/3 0/4 0/0
Display Mode: Extended Display
</Report>

<Displays>
DeviceName: \\.\DISPLAY1
DeviceDirectMode: No
DevicePrimary: Yes
DeviceRect: 1216x676 @ (0, 0)
DeviceString: NVIDIA GeForce GTX 1070 Ti
DeviceID: PCI\VEN_10DE&DEV_1B82&SUBSYS_C3071462&REV_A1
DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{14D8219B-FDF2-11E9-9098-ED94A0D8B44F}\0000
DeviceMonitorCount: 1
Monitor 0 DeviceName: \\.\DISPLAY1\Monitor0
Monitor 0 DeviceString: Generic PnP Monitor
Monitor 0 DeviceID: MONITOR\SHP0FE9\{4d36e96e-e325-11ce-bfc1-08002be10318}\0006
Monitor 0 DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0006

DeviceName: NvAPI
DeviceDirectMode: Yes
DevicePrimary: No
DeviceRect: 2160x1200 @ (0, 0)
DeviceString: NVIDIA
DeviceID:
DeviceKey:
DeviceMonitorCount: 0

</Displays>

<Devices>
</Devices>

<USB>
[HostController] USB xHCI Compliant Host Controller
Manufacturer: Generic USB xHCI Host Controller, Provider: Microsoft, 2019-06-19, 10.0.18362.207
Root Hub
[Port1]: USB Composite Device (VID:04F3 PID:0103)
[Port2]
[Port3]
[Port4]
[Port5]
[Port6]
[Port7]: Generic USB Hub (VID:0BB4 PID:2210)
[Port1]: Generic USB Hub (VID:0BB4 PID:2134)
[Port1]: USB Composite Device (VID:28DE PID:2000)
[Port2]: USB Composite Device (VID:0BB4 PID:2C87), Alpha Imaging Tech, HTC Vive
[Port3]
[Port4]
[Port5]: USB Input Device (VID:0BB4 PID:2C87), HTC, HTC Vive, 205835585734
[Port6]: USB Input Device (VID:28DE PID:2101)
[Port7]: USB Input Device (VID:28DE PID:2101)
[Port2]: Broadcom BCM20703 Bluetooth USB Device (VID:0BB4 PID:0306)
[Port3]
[Port4]
[Port8]: USB Input Device (VID:0461 PID:4D64), USB Optical Mouse
[Port9]
[Port10]
[Port11]
[Port12]
[Port13]
[Port14]
[Port15]
[Port16]
[Port17]
[Port18]
[Port19]
[Port20]
[Port21]
[Port22]
[Port23]
[Port24]
[Port25]
[Port26]

</USB>

[Noppsie]

did you ever solve this? im in the same boat

[ymo1965]

"Tracking: No Driver
OS: Windows 10
OS Version: 10.0.0.18362"

I've had this issue too though only when my wireless adaptor is used. If I use the cable it's ok. Valve support are always harping on about sending in system reports. I sent in two.. one working and one with this error (looks to be base stations issue/bluetooth). Valve did nothing. Never heard anything back. What a waste of space they are.

If you have Windows 10 2004 update installed then either try rolling back, though you only get about 7 days to do this... or reinstall windows. This option to rollback btw is in 'recovery'.

Failing that you could try the patch that's supposed to solve bluetooth issues as well as others. Might help, might not but I'm just trying to help. I got abuse from someone called 'BUM' cause that didn't work for him but it did for someone else. Very fitting name, idiot.

The patch is here: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4568831

[xevious]

I installed the Linux beta version of SteamVR on my Windows computer and that solved the persistent error 108 for me. Headset was detected, I played Space Engine for a while.

[ymo1965]

Originally posted by xevious:

I installed the Linux beta version of SteamVR on my Windows computer and that solved the persistent error 108 for me. Headset was detected, I played Space Engine for a while.

Someone else suggested that and it worked for me as well. The only thing though, there was no games library. In my Vive headset I saw nothing. It was really bare-bones. How was it for you? If there's a way to fix this library thing, I would love to know. I did also notice that the linux version I used was 1.8.21. I have a backup from Nov last year that is 1.8.20. So no linux updates since last year?? amazed it worked on PC.

[xevious]

Originally posted by ymo1965:

Originally posted by xevious:

I installed the Linux beta version of SteamVR on my Windows computer and that solved the persistent error 108 for me. Headset was detected, I played Space Engine for a while.

Someone else suggested that and it worked for me as well. The only thing though, there was no games library. In my Vive headset I saw nothing. It was really bare-bones. How was it for you? If there's a way to fix this library thing, I would love to know. I did also notice that the linux version I used was 1.8.21. I have a backup from Nov last year that is 1.8.20. So no linux updates since last year?? amazed it worked on PC.

Yeah, I couldn't see my library from the menu, but I could see my 'most recent' games and open them from the 3D 'Home' environment after I enabled it. As far as I can tell, opening and closing games can just be done from the desktop.

[Turbolego]

Originally posted by xevious:

I installed the Linux beta version of SteamVR on my Windows computer and that solved the persistent error 108 for me. Headset was detected, I played Space Engine for a while.

I also have the 108 error on my Vive today.
Selecting the linux version of SteamVR in the "BETAS" tab did not work for me.
Anything else i can try to resurrect my HMD?

[ymo1965]

Originally posted by Turbolego:

Originally posted by xevious:

I installed the Linux beta version of SteamVR on my Windows computer and that solved the persistent error 108 for me. Headset was detected, I played Space Engine for a while.

I also have the 108 error on my Vive today.
Selecting the linux version of SteamVR in the "BETAS" tab did not work for me.
Anything else i can try to resurrect my HMD? :cozycastondeath:

Only thing to try is remove the 2004 update if the option is there in 'recovery'. If you don't have that option then not sure what else to suggest. Worst case scenerio is reinstall Window10 and block the 2004 update for a month (updates/advanced settings)

[Turbolego]

Originally posted by ymo1965:

Originally posted by Turbolego:

I also have the 108 error on my Vive today.
Selecting the linux version of SteamVR in the "BETAS" tab did not work for me.
Anything else i can try to resurrect my HMD?

Only thing to try is remove the 2004 update if the option is there in 'recovery'. If you don't have that option then not sure what else to suggest. Worst case scenerio is reinstall Window10 and block the 2004 update for a month (updates/advanced settings)

I have a device under "Devices" in the windows settings called "STM32 BOOTLOADER" that shows up when i connect my Vive to my computer... Did you also have that, or do you?

[ymo1965]

No I don't have one of them. TBH im not really sure what they are. I googled it and saw that its a little programmable boot-loader.

https://www.youtube.com/watch?v=wGbiT6IxGP0

Not sure if that's a possible issue for you but I don't have one and my Vive is ok. Maybe you should check as it seems like it's in your pc and your not sure why it keeps appearing. Personally I don't think its anything to do with your VR setup. These boards are hobbyist things. Not connected with VR at all. Maybe unplug it?

[Turbolego]

Originally posted by ymo1965:

No I don't have one of them. TBH im not really sure what they are. I googled it and saw that its a little programmable boot-loader.

https://www.youtube.com/watch?v=wGbiT6IxGP0

Not sure if that's a possible issue for you but I don't have one and my Vive is ok. Maybe you should check as it seems like it's in your pc and your not sure why it keeps appearing. Personally I don't think its anything to do with your VR setup. These boards are hobbyist things. Not connected with VR at all. Maybe unplug it?

Or maybe not?
I found this thread: https://www.reddit.com/r/Vive/comments/ajh6wx/htc_vive_stm32_dfu_mode_problem/

Did the recent firmware update get my Vive stuck in "DFU Mode"?

[ymo1965]

Originally posted by Turbolego:

Originally posted by ymo1965:

No I don't have one of them. TBH im not really sure what they are. I googled it and saw that its a little programmable boot-loader.

https://www.youtube.com/watch?v=wGbiT6IxGP0

Not sure if that's a possible issue for you but I don't have one and my Vive is ok. Maybe you should check as it seems like it's in your pc and your not sure why it keeps appearing. Personally I don't think its anything to do with your VR setup. These boards are hobbyist things. Not connected with VR at all. Maybe unplug it?

Or maybe not?
I found this thread: https://www.reddit.com/r/Vive/comments/ajh6wx/htc_vive_stm32_dfu_mode_problem/

Did the recent firmware update get my Vive stuck in "DFU Mode"? :cozycastondeath:

Sorry don't have this in my setup. I assumed you were unsure what the STM32 was as you asked if I had one. Has the HMD ever worked ok? No one replied to that guy who wrote that reddit post. Not an easy one to answer. Hope you get it sorted. Might be worth contacting that guy on reddit.

[Turbolego]

Originally posted by ymo1965:

Originally posted by Turbolego:

Or maybe not?
I found this thread: https://www.reddit.com/r/Vive/comments/ajh6wx/htc_vive_stm32_dfu_mode_problem/

Did the recent firmware update get my Vive stuck in "DFU Mode"?

Sorry don't have this in my setup. I assumed you were unsure what the STM32 was as you asked if I had one. Has the HMD ever worked ok? No one replied to that guy who wrote that reddit post. Not an easy one to answer. Hope you get it sorted. Might be worth contacting that guy on reddit.

My Vive has worked fine for over 4 years now. Might just be either the firmware update or windows update to version 2004?