New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

(Windows 7) Oculus Setup does not detect the sensor, but Device Manager does. Tried everything. :c

Oswin_Oswin_ Posts: 4
NerveGear
<i>I purchased an Oculus that arrived today. As the owner of and developer for a DK1 (cannot remember my original login info for the life of me, or I'd use my old account) , I was very excited to try a new one out. ...unfortunately, several hours later, I still haven't gotten to try it. ;~;</i><br><br>Whenever I get to the setup menu, everything is detected except the sensor.<br><p><img alt="" src="https://us.v-cdn.net/6024342/uploads/editor/ii/bj5die87kvfz.png" title="Image: https://us.v-cdn.net/6024342/uploads/editor/ii/bj5die87kvfz.png"><br></p><p>I can see the sensor registered as a rift sensor in the device manager, as shown below.<br><br><img alt="" src="https://us.v-cdn.net/6024342/uploads/editor/3x/aqp67ddzl487.png" title="Image: https://us.v-cdn.net/6024342/uploads/editor/3x/aqp67ddzl487.png"><br></p><p>I have tried all of the following things to get past this.<br>&gt;Nuking all signs of a previous Oculus Runtime install, deleting every file, wiping the space where they were to 0s, hiring CIA operatives to change legal documents to wipe the record of there ever being an oculus runtime on my computer from history.</p><p>&gt; Changing from a USB 3.0 to a USB 2.0 port.</p><p>&gt; Reinstalling the Oculus software.</p><p><u>&gt; Updating my Intel USB 3.0 drivers from 3.0.x.x to 4.0.x.x.</u></p><p>&gt; Using the X-Box extension cable on the sensor, and plugging it into a USB 2.0 port.</p><p>&gt; Using the X-Box extension cable on the sensor, and plugging it into a USB 3.0 port.<br></p><p>&gt; Reading every single thread even remotely related to the issue only to find one person who had the same issue, fixed it, and then didn't tell anyone how. (In other words, the worst kind of person on the planet. )</p><p>&gt; Reaching page 6 of the Google search results with every possible permutation of "Oculus", "Sensor", "Not working", "Not detected", "Won't detect", etc. Page 6 is called "Desperation.</p><p>&gt; Every possible combination of the above things, repeatedly, for hours.</p><p><br><b>Possibly related</b>: My computer runs Windows 7 Service Pack 1, and I cannot, no matter how many times I try, install the Windows Update KB3303929, which is required by Oculus Rift. Like above, I have tried every possible thing on the google search results page to get the notoriously difficult update to install.&nbsp;<br>MANY people cannot install that update and never have, myself included.</p><p><u>As a result, I had to run the installer with /bypassHotfixCheck. </u><br>I do not know what this particular hotfix is for, or why Oculus depends on it, so I don't know what the consequences of not having it are.&nbsp;</p><p>Please don't ask me to reinstall Windows -- It's just not an option. If you can't take that on faith, I will happily email you a copy of my calendar. <br>If you've got any other ways of getting that update to install, please tell me.<br>I would also like to know what the consequences of not having the update actually are.</p><p>Attached is my oculus setup log, my oculus service log, and everything else in the folder that I could think of that might be useful.</p><p>Note: One of the service logs and the oculus setup may suggest an outdated USB hub driver. As mentioned above, I fixed that, obviously to no avail.&nbsp;<br><br>Can anyone advise me on how to fix this?&nbsp;<br><br></p><p><br></p>

Comments

  • Oswin_Oswin_ Posts: 4
    NerveGear
    edited October 2016
    Oh god. What? Why? WHY? Am I cursed?
    Have I done something wrong? Is this a haunting? 
    Do machines crumble in my sight? Am I a goddess?

    Trying again:

    I purchased an Oculus that arrived today. As the owner of and developer for a DK1 (cannot remember my original login info for the life of me, or I'd use my old account) , I was very excited to try a new one out. ...unfortunately, several hours later, I still haven't gotten to try it. ;~;

    Whenever I get to the setup menu, everything is detected except the sensor.



    I can see the sensor registered as a rift sensor in the device manager, as shown below.



    I have tried all of the following things to get past this.

    >Nuking all signs of a previous Oculus Runtime install, deleting every file, wiping the space where they were to 0s, hiring CIA operatives to change legal documents to wipe the record of there ever being an oculus runtime on my computer from history.

    >Changing from a USB 3.0 to a USB 2.0 port.

    >Reinstalling the Oculus software.

    >Updating my Intel USB 3.0 drivers from 3.0.x.x to 4.0.x.x.

    >Using the X-Box extension cable on the sensor, and plugging it into a USB 2.0 port.

    >Using the X-Box extension cable on the sensor, and plugging it into a USB 3.0 port.

    >Reading every single thread even remotely related to the issue only to find one person who had the same issue, fixed it, and then didn't tell anyone how. (In other words, the worst kind of person on the planet.

    Reaching page 6 of the Google search results with every possible permutation of "Oculus", "Sensor", "Not working", "Not detected", "Won't detect", etc. Page 6 is called "Desperation.

    >Every possible combination of the above things, repeatedly, for hours.

    Possibly related:
    My computer runs Windows 7 Service Pack 1, and I cannot, no matter how many times I try, install the Windows Update KB3303929, which is required by Oculus Rift. Like above, I have tried every possible thing on the google search results page to get the notoriously difficult update to install.
    MANY people cannot install that update and never have, myself included.

    As a result, I had to run the installer with /bypassHotfixCheck.

    I do not know what this particular hotfix is for, or why Oculus depends on it, so I don't know what the consequences of not having it are.

    Please don't ask me to reinstall Windows -- It's just not an option. If you can't take that on faith, I will happily email you a copy of my calendar.

    If you've got any other ways of getting that update to install, please tell me.
    I would also like to know what the consequences of not having the update actually are.
    Attached is my oculus setup log, my oculus service log, and my giant (abridged) service zip file.

    Note: One of the service logs and the oculus setup may suggest an outdated USB hub driver. As mentioned above, I fixed that, obviously to no avail.

    Can anyone advise me on how to fix this?


  • Cookiez111Cookiez111 Posts: 7
    NerveGear
    edited October 2016
    I don't think I can help much but here is some info: 
    I'm running W7 SP1 and I checked that I have KB3303929 successfully installed but I didn't even know it was required.
    Also, my sensor device manager properties is as shown here:

    There might be an issue with the digital signature and the sensor is not properly detected from the look of your screene.
    I remember we needed to accept some driver digital signature box during the install or something like that but on how to fix this...I'm not sure..
  • zbosonzboson Posts: 994 Poster of the Week
    Have you tried installing Windows10?
  • Oswin_Oswin_ Posts: 4
    NerveGear
    zboson said:
    Have you tried installing Windows10?
    No. While I feel that Windows 10 is a huge improvement on Windows 7, and perhaps the only improvement on a Windows OS since Windows XP, I cannot use it because Windows 10 is notorious for poor sound quality and I am a composer.
    Also, I have to jump through hoops to make sure all of the privacy settings are ticked off so I don't get sued over NDA's -- I had to omit my unity editor logs from the Oculus diagnostic zip, not because I think Oculus would ever do anything with it, but because I am working on a company's unity-rendered physics simulator and they would go apeshit if they thought anyone could see as much as the file structure.

    I don't think I can help much but here is some info: 
    I'm running W7 SP1 and I checked that I have KB3303929 successfully installed but I didn't even know it was required.
    Also, my sensor device manager properties is as shown here:

    There might be an issue with the digital signature and the sensor is not properly detected from the look of your screene.
    I remember we needed to accept some driver digital signature box during the install or something like that but on how to fix this...I'm not sure..

    I accepted the digital signature box, but I think you're on to something here. Indeed, mine shows Error 52, and has a warning light by it, but yours does not.

    I tried running commands as suggested online, and editing group policies (the digitial signature policy is all but absent on my PC), but I cannot get Windows 7 to accept this driver. 

    Perhaps it is refusing to run the driver over this?

    Does anyone know a workaround? Perhaps a way of proving that it's signed, or a way of circumventing it?
  • Oswin_Oswin_ Posts: 4
    NerveGear
    edited October 2016
    Confirmed! 

    Restarting Windows 7 in the disable signature checking mode (F8 on boot), the Rift Sensor is detected perfectly fine in the setup.

    Unfortunately, this is not a workaround -- having Windows in this mode is very insecure and requires me to enter F8 on boot.

    Does anyone know what might cause the Oculus rift sensor driver to not pass the signature test? 
  • Comic_Book_GuyComic_Book_Guy Posts: 1,077 Poster of the Week
    Windows 7 is your issue. 
  • prezjtprezjt Posts: 4
    NerveGear
    I feel your pain.  I reinstalled W7 Pro 2 times with zero resolutions.  Upgraded to 8.1 and 10 and still no resolutions.  Because I had troubleshooted and put in so much time with W7 I reverted back to my original W7 image.

    For me, my device manager had less than a handful of unknown devices and I couldn't move forward with the Oculus Setup until I had resolved all the drivers first.

    But I got it working...  used all the Mobo / Graphics drivers used from the CD(s).   As well as updated Mobo Bios firmware.  Installed newer drivers: AMedia USB 3.1, XBox ACC (https://www.reddit.com/r/Windows10/comments/3qgeoz/xbox_acc_driver_is_unavailable_cant_get_the_xbox/cwf98x7/)

    MOBO: Asus H170 Gaming Pro
    Corei5
    Asus 1070 Graphics Card


Sign In or Register to comment.