Skip to main content
New Participant
November 26, 2020
Question

Rift S owners who had the Displayport issue and FIXED it: How?

Picked up a Rift S recently and it refuses to work because of the well-known displayport issue. I've already submitted a ticket, but I thought I'd try to gather info from the community as to which fixes worked and which didn't.

The specific issue I'm talking about is where after connecting the Rift S, both connections will seem OK for a few seconds, but then the Displayport disconnects and you're left with one of these status screens in the Oculus app:

There's plenty of speculation as to the cause of this issue and no official word from Oculus as far as my research goes, the most likely culprits seem to be a power delivery issue where the headset is drawing too much power for the USB port to keep up (which, for some reason, causes an issue with the DP connection rather than the USB one), a bad cable, or a software/firmware issue caused by the 2019 update that brought Facebook integration to the Oculus app (this is, again, pure speculation, but there are a few articles that suggest these issues became more prevalent when that update dropped)

The behavior is the same for every "plug-in procedure" as Oculus describes it: Connect the USB3 cable, wait 10 seconds (the LED between the lenses goes from off, to amber, to white, and stays there- nothing from the displays themselves), connect Displayport. 

Here's everything I've tried so far, collected from forums and other sources:
  • Rebooting
  • Reinstalling Oculus app
  • Disabling power-management USB suspend options
  • Disabling USB suspend on USB devices through Device Manager
  • Updating video drivers
  • Reinstalling video drivers
  • Reinstalling video drivers using DDU and Safe Mode to fully wipe the previous driver
  • Running C:\Program Files\Oculus\Support\oculus-drivers\oculus-driver.exe , which starts silently and doesn't pop up any kind of status window, which seems like a bad way to design software but whatever
  • Connecting the headset through every available USB 3.0 and USB 3.1 port on my computer, using the proper "plug-in procedure" each time
  • Connecting a single monitor through HDMI rather than Displayport or DVI
  • Disconnecting all other non-essential USB devices
  • Checking the seating of the connectors on both the computer side and headset side
  • Checking the integrity of the cable, connectors, and headset, for kinks/frays/etc
  • Unplugging audio devices from the headset

Here's what I've seen online, but haven't been able to try yet:
  • Using a dedicated, powered PCI-E USB 3.0 card, specifically the Inateck KT4001 as (apparently) recommended by oculus support 
  • Using the above card but with different drivers (the ones that come with it, the ones Windows installs automatically, whatever "Fresco" drivers are, etc)
  • Using a powered USB 3.0 hub
  • Replacing the cable
  • Replacing the GPU
  • Replacing the entire headset
  • Replacing the entire computer

The fixes I haven't been able to try seem hit-or-miss, though the PCI-E card seems to have worked for some.

So here's my question to you, Rift S user who's fixed this issue: What did you do? What has worked out for you? If your headset worked and then suddenly didn't, do you remember around what time it happened or what you did around that time?

If your answer is "I stopped using a cable extender" or "I stopped using a mini-DP to DP converter" or whatever else, that answer doesn't apply to this issue. This issue is specific to the Rift S in its intended setup, with no dongles or adapters involved.

Once again i've already submitted a ticket and am working through the issue personally, this isn't me asking for solutions, it's me asking for experiences from people who had this issue and got it fixed.
This topic has been closed for replies.

57 replies

New Participant
September 10, 2021

I checked back on this thread like I've been doing for weeks now trying to get the headset to work. I also have a 1WEGCH5OR20422 cable, and unending pseudo-DisplayPort problems. Just recently got a powered USB hub (Sabrent 4 port model) and still have fake DisplayPort problems and a fake 'On' white light inside the headset which just hides the fact that when you look inside the display is off.

 

As an added piece of information, sometimes when I would start the headset and get it to work by sheer random chance (months ago) I would see snow starting to form in the goggles. The snow would continually get worse and worse until the screen shuts off unless I put my hand up on the headset-side part of the cable and push or pull a little bit. Usually pushing up on the cable, which makes the snow vanish. Strangely, letting go of the cable then would not make the snow immediately come back, and everything would be crystal clear for a while. Only getting the cable twisted in strange ways would make the snow come back and you could usually just fiddle with it again to push the snow back. This is one case for the WEGCH5 cables having a high failure rate. I think mine is just beyond ever showing any snow anymore.

 

Sometimes I could get it to work by screwing with the Oculus software. Restarts, re-installs, punching the "Device Setup" button, turning beta on and off. On a few occasions, the "Headset audio does not work" error would be really good because it would mean the displayport problem would never happen that attempt. I usually give VR about 5-10 tries whenever I remember it, and it's not been behaving lately. Will hit support soon.

Participant
September 11, 2021

Best to see if you can order a new cable for it. I did get similar symptoms, with the snow effect you experienced, when mine was RMA replaced the first time. I got 2 weeks temperamental use out of it before it stated going snowy then packed in completely, then I got another failed RMA replacement, before finally getting a third.  Even that failed but that was when I  had a brainfart and got hold of a powered USB hub. That fixed it in my case but doesn't seem to work for everyone.  Given there's a trend on the WEGCH5 cables failing I would suggest trying to get another cable online. 

Stu5mmy
New Participant
September 18, 2021

Hello everyone, I've been checking this forum for over a month trying to troubleshoot my VR with no success up until now. Spoiler alert, what fixed my issue was replacing the cable, since the SN had the H5 on my cable as someone pointed out previously, however, I don't think this is necessarily the case for everyone who's trying fix the issue since it depends on the circumstance you're on. I tried fixing the displayport issue with a USB powered hub and it obviously didn't work, but I did notice something reading this forum and other sources about this solution that no one has made a mention of and I'll explain it below.

USB powered hub solution: This usually ONLY works for people who've had their headset for the first time and doesn't work right off the bad. The theory is that the motherboard is potentially not drawing enough power to the headset since it seems to be a little picky in that sense. It could also apply to people who've only had a few days playing with it, but it could be less likely since your motherboard did the job in drawing enough power for the first days or at least that is my theory.

Replacing the cable: This is the most expensive paid solution to fixing the displayport issue, however, this can be the definite solution for people who've played on their Rift s for months, which in my case I lasted around 10 months without any issues until the last days with it. It showed different symptoms throughout that last month, like black screens, the VR video losing connection and reconnecting again and lastly some weird white dots showing on my VR.

 

The way I replaced my cable wasn't through Oculus since they don't ship in my country so I bought a third party cable from Aliexpress whose brand is LONGON, costed me around 80 bucks, had solid reviews and it's been working perfectly fine ever since I've gotten the cable. In conclusion, this should help other people choose the right solution according to their circumstance, although this is just my theory and is probably not 100% accurate.

Hope this helps you out guys! 🙂

PS: For anyone who's had one of their controllers dead or reconnecting constantly right after fixing the display port issue try leaving the battery out for a whole day since it resets whatever the hell makes the controller work. This seems to happen to the controllers when they are left for a long time without being used apparently.

Up and Coming
September 24, 2021

You dont have to wait ten seconds. It works immediately.

Up and Coming
September 24, 2021

Another problem is I get a "display port not detected" error. A USB hub wont fix that.

Participant
October 27, 2021

Yep, I have the same issue as you and others here.  In fact, I think bout a few weeks into using mine which I purchased bout a year ago, I had to reseat my cables after every boot.  Most of the time it would work fine after 1 reseat. 

 

I initially opened a support ticket but gave up on all the troubleshooting steps.  Lazy ... maybe, but it worked fine when I reseated.  

 

About a week ago the error was constant.  Reseating gave the same error.  I purchased a $20 USB hub, but it didn't help.

 

So, I re-opened my support ticket and proceeded to follow through with the potential fixes and send all the logs.  Today they said they'd send me a replacement unit!

 

Hopefully, it's more stable than the 1st one.

 

Thanks so much for posting this for us!

Participant
November 2, 2021

Got my refurbished headset today.  So far working just fine, even with the adapted audio headset plugged into it.

Participant
October 27, 2021

This is a complete stretch with no facts to back it up....... Rift S users are having what appears to be some sort of power deliivery issues as of end of 2020/beginning of 2021, Quest 2 users have been having similar issues, where the link cable does not charge during use, only supplies data (even though its supposed to do both). I wonder if the issues are related? Something to do with latest versions of Oculus app/device firmware versions etc. Like many of the Rift S users, plugging your device into a powered USB hub/wall charger, is a similar solution to many of the Quest 2 users as well (use the link cable to charge via wall brick, and Air Link (wifi) to connect to pc........ Arsenio Hall might have said "This is one of those things that make you go Hmmmmm?"

 

Participant
October 28, 2021

It might possibly be, but based on my experience and what I saw I would wager a similar but not exactly the same guess. At the end of the day I think it really comes down to exactly what all of us are thinking and what the more obvious solution is - the proprietary cable system on the rift S was notoriously faulty, and has known design flaws that will cause it to fail over time (maybe due to the demand of the way it was designed as a single cable?)

 

While I have no evidence to back this up either, only what I personally experienced, the entire reason that they pivoted so quickly away from this was because they know they are all going to fail long term anyway.

 

Notice the HP Reverb recently? They released a new "upgraded cable" after launch which is claiming to fix the issues for a lot of users? In the realm of fun coincidences, do you want to know the exact other device that I tried hooking up to my very same PC and also did not work? Yep, an HP Reverb I borrowed from a friend using an older gen 1 reverb cable. Do you want to know what device I tested and works absolutely perfectly fine in the same usb port? Yep, an Oculus Quest 2 using a link cable.

 

So while it's pure speculation of course, I think it's actually really clear exactly what happened here. Oculus released the Rift S, they realized much later that in the EXACT SAME fashion that the HP Reverb cables have flaws, theirs do to, and they will likely fail for many users. And you know exactly what they've done instead? Yep, they dropped the product and ran. It makes sense purely from an anti-consumer business perspective, but they are here to make money and I really would not be surprised.

I think that the whole "Quest 2" not charging thing is more so indirectly related, it's something that they knew would be a limitation potentially, but not so much a cable failure.

New Participant
January 8, 2022

It's not the cable, or atleast on my case and a lot of what i've seen online. It's an AMD problem with the USB power delivery that is cutting off for a milisecond or something like that and its making the headset reset. I got another gaming PC in my home and its an Intel PC, not a single problem there. On the AMD pc it fails a lot, connecting the headset to the usb-c port on my graphics card also made the problem go away but it wasnt perfect either (image jittering and audio cutting). In the end i 99% solved it with a powered usb hub, that's it (an internal pcie usb card would also work i guess). In 3 months it only failed with the "display port not connected" once.

 

Ryzen 3600 with Asus Tuf gaming B550 motherboard (latest bios).

New Participant
December 3, 2021

My headset got the dreaded Display Port Error about 3 months ago. After 28 days I kid you not, Oculus Support basically said there is nothing we can do for you, buy a Quest 2. Jealous to see some people here getting offered refurbished headsets but whatever. I got a Quest 2, hope it will work and be just as good as my Rift-S playing PC VR!

December 5, 2021

Try this:

 

I had the same problem, not used my Rift S for 2 weeks and now constantly disconnecting > Firmware update > missing display port > and this again and again. (nothing chanched at my PC, but maybe a windows update)

 

Now i found a way it works:

-You need "MSI Util V3" (ask google)

-disconnect Rift S

-in Oculus App also remove the headset

-open MSI Util (as admin) and deselect/unmark "MSI" on your USB Controller, then press APPLY on up/right and restart PC.

-open Oculus app and connect your headset normally

 

....mine is now working again without disconnect.

 

p.s. with a separate USB card the problems are little bit different, it also helps to disable the MSI mode, but not 100% (in my case), with mainboard USB ports it´s a 100% fix.......if they have enough power for wakeup the headset at a cold boot (usb port power issue), but that´s another problem.

Participant
March 25, 2022

sadly I fixed my issue by sending it back for repairs, nothing I did which was listed in your forum post (besides replacing) fixed it for me

New Participant
June 1, 2022

I HAVE FIXED THIS ISSUE!

 

If you're getting this in 2022, reinstalling drivers, firmware, etc, you're wasting your time. 

 

The cable is broken.

 

Conveniently, my friend and I built the exact same PC, both have a rift S, mine broke, his didn't.

 

I tried my headset on his PC with his cable and that was the only way I could get it to work.

 

I spoke to Oculus support on live chat, told them all of this, and they sent me a new cable within the week - for free.

 

Get the box you got the Oculus in, prepare to be on live chat for a little while and they'll send you a new cable.

Up and Coming
November 10, 2022

Since day one of buying this headset in Oct 2020, daily, I get:

1. Screen display flashes/freezes for a blink, then goes black

2. I check Oculus app and it says only: USB disconnect

3. I must first unplug and re-plug the USB into my PC

4. Then, I get a message saying: Display adapter disconnect

5. Un-plug/re-plug the display adapter (straight from Rift S cord into back of PC video card slot, no adapters used)

6. Status goes back to green

7. I re-enter VR

 

This repeats about every 20-60 minutes every single time I use the headset. (Many times while using Microsoft Flight Sim when I am 20 seconds from landing on the runway)

 

I have posted and posted and have given up. Oculus is not able to resolve this issue.


Worse yet, every time Oculus updates this, I now do not know whether I should be using the beta version, or not.

This whole thing has been one of the most frustrating experiences I have ever had with any product I have ever bought in my entire 53 years. And I bought the Quest 2 and that sucks trying to get it to work right with MSFS2020. It hurts your head. Oculus screwed up not using the head design from the Rift on the Q2. The Rift headset is one of the most comfortable headsets I have owned (several). The Q2 feels like cheap junk. And the performance I am getting with all three of my flight sims is a major pain to work with, when I do manage to get the Q2 working right.

 

I'll try a cable. It is about the only thing I havent tried yet. Kinda sucks I have to now spend an additional what, $125 for one??? Thanks, Oculus.

 

(Intel i9-10600x, RTX2080 Super, Win 10)

Participant
April 30, 2023

I felt your pain mate, for I too, had the same problem. I figured at the time the headset was demanding more power than the USB bridge on the motherboard was able to provide.  I prove that correct when I bought a powered USB 3.0 hub and connected the headset there.  It was never the video card needing replaced or updated, just intermittent loss of USB. 

It's no longer an issue since I upgraded my rig last year and the new mobo can handle it, but I am grateful, for the additional functionality a cheap little hub brought. 

New Participant
April 30, 2023

Okay so just an update cause I just had this issue and figured it out on my own. The problem is you need to update your computer's graphics card. Just look up the name if your graphics card on your computer, go to the website and update the latest version. I also searched my HP Support Assistant program on my computer to update the BIOS for good measure.