Your sensor is plugged into an incompatible USB port?? (after win10 update)

[KevinLongtime]

So my computer restarted on windows 10 with the latest update and now it seems to want to say the usb 3.0 port I've been using for the past months and a half for my sensor is all of a sudden incompatible. The Rift headset itself reports no problems on either 3.0 port only the sensor does.

Even switching the USB's around it's not the specific USB port, but rather whichever 3.0 port the sensor is plugged into that's the "incompatible one"

Anyone else having this?
Edit: Others are having the same issue today:
https://www.reddit.com/r/oculus/comments/5589h5/your_sensor_is_plugged_into_an_incompatible_usb/

• Asus P6X58D Premium Mobo (w/ two USB 3.0 ports on the back and a ton of USB 2.0 ports)
• i7 920
• GTX 970
• 12gb Corsair Dominator ram 1600mhz
• Windows 10 Version 1607 for x64-based Systems (KB3194496)
• Renesas USB 3.0 eXtensible Host Controller - 0.96 (Microsoft) http://oi68.tinypic.com/2rc0brt.jpg

Log Files in next post below:

Update: The interesting thing about this problem is that I can start up the OculusWorldDemo from the SDK and it will play fine. Can even exit out with the home button back to oculus home inside of VR. Yet it will tell me while INSIDE of VR that my sensor is on an incompatible USB 3.0 port while plugged into said incompatible USB 3.0 port inside of VR. 

Hell, I can start up any VR game outside of Oculus Home. It's only the Oculus Home games telling me "You have a pending hardware issue preventing you from entering VR"

Update #2:  MuntzMental appeared to have found the cause. Oculus is blacklisting our equipment:
https://www.reddit.com/r/oculus/comments/5589h5/your_sensor_is_plugged_into_an_incompatible_usb/d8af...

[Thijssss]

That explains my problems .. HMD works fine USB3.0 but the sensor would refuse to work being unable to start any content. Using USB2 resolved the issue .. but I did now order a new USB3 card (the amazon one). Oh well, I needed another port anyway for the second sensor soon.

[elboffor]

well boys and girls, My support ticket is closed as they have now fixed the problem.
all it took was a preorder of a £200 pair of controllers and BOOM! 15 minutes later they got back to me and said it was resolved.

for anyone who is wondering, all i had to do was:

• sign out of the rift software (not just close it)
• restart the pc
• sign back in

If this is a personal fix for just my account then i might start pimping out my log in details to fix it for you too 😄

[Kirshaw]

elboffor said:

well boys and girls, My support ticket is closed as they have now fixed the problem.
all it took was a preorder of a £200 pair of controllers and BOOM! 15 minutes later they got back to me and said it was resolved.

for anyone who is wondering, all i had to do was:

• sign out of the rift software (not just close it)
• restart the pc
• sign back in

If this is a personal fix for just my account then i might start pimping out my log in details to fix it for you too 😄

Have you tested already? Do they remove the adaptors from the black list?

[Anonymous]

thank you Oculus and Elbofor problem is now resolved

[OzDruiD]

My compatability.JSON file was indeed updated when I logged in\out - it  now has no NEC items... still plenty of others thou .. appears to be what it was before hand (the blacklist section)
- the VIdMAP section still lists the NEC Entries thou?

- I can't be sure as I didn't take a copy before these changes were made.

"UsbBlackList": [
    {
      "Vendor": "VIA Labs",
      "PID": "Any",
      "OS": "Any"
    },
    {
      "Vendor": "ETron",
      "PID": "Any",
      "OS": "Any"
    },
    {
      "Vendor": "Renesas",
      "PID": "Any",
      "OS": "Any"
    },
    {
      "Vendor": "ASMedia",
      "PID": "1042",
      "OS": "Any"
    },
    {
      "Vendor": "Texas Instruments",
      "PID": "8241",
      "OS": "Any"
    },
    {
      "Vendor": "AMD",
      "PID": "7814",
      "OS": "Any"
    }
  ],

[beaulima9933]

My sensor is "incompatible" since Win10 last update.
Fresco 3.0 card.

Updated 3.0 drivers. Nothing
Tried the JSON file. Nothing.
Signed out - restard - in Oculus. Nothing.
Before backrolling to previous Win10 update, I tried one last thing.
I uninstalled all Oculus software. Restarted. Re-installed Oculus.

Now everything is fine. Just sayin'. I don't think the problem is from latest Win10 update, but from Oculus software. See you in VR!

[Thijssss]

Ohh that's good to hear! I'll give it a try tonight. I'll be receiving the new USB3 card (amazone one they recommended) this friday. I need the extra ports for Touch anyway.

[nasenhupe]

I plugged the sensor to USB 3.0 today and it works as usual! Yay! Did not have to logout of my account. Just started the PC and the Oculus software and it worked.

[cybereality]

The NEC blacklist was removed. Sorry for the inconvenience.

[Bagnet]

Any chance of removing Etron? The only way it works is if i use that socket. I play all night with no issues. On the ports home accepts it disconnects all the time. I have the Json file edited and blocked so its all working for now.. I get no issues from it though. no clue why it would be blacklisted?