1 2 3 Previous Next 91 Replies Latest reply on May 22, 2018 1:21 PM by Zuperman

    How to get SR300 working on Windows 10 Build 1703 - Including SDK Apps such as Segmentation (Updated 5/17/2017)


      Hello everyone!


      Just as a reference, I am a Microsoft Engineer working off the books because I was directly affected by this issue since updating to Windows 10 Creators Update.  Please note that this post does not reflect any of the opinions or views of this company and is completely of my own.  The reason why I actually ended up working on this was because I am a Video Game Streamer on my leisure time when I am not working.  I have confirmed this is a Intel Driver Issue for your reference.

      With these steps I was able to get FULL functionality from my Razer Stargazer Webcam(SR300) after performing this fix/workaround.  The reason why you can only use the imaging sensor is because the Virtual Driver is not actually installed.  This should work in theory for Insider Builds as the same principle applies.


      If you have the following item that is circled, this fix does not apply to you.  But you should not have to do this if you aren't on the latest build of Windows 10.


      Please ensure you are running the latest build of Windows 10.  Windows 10 Version 1703 to be exact.  Here is my OS Build for your reference.  This is not a Insider Build.  Results may vary if you are on a Insider Build.

      EDIT (5/17/2017):  I have tested this with the latest build, 15063.296


      Step 1:  Go to the Settings App and Ensure All Updates are Completed

      EDIT: Once Completed, Open a Run Box (Windows Key + R) and type the following command:


      In the Windows that appears, click "Device Installation Settings"

      Then Select, "No, your device may not work as expected."

      Side Note: Once Intel releases an actual fix, you can turn this back on at a later date.


      Step 2: Open up the Device Manager.  You can either access this by accessing a Run Prompt and typing "devmgmt.msc" in the field and click "ok" or right-click/windows key + "X"

      to access it.  Keep in mind that you do need Administrative Privileges.


      Right-click and delete the highlighted drivers.  Keep in mind, my machine is working, so I do have a SR300 Virtual Driver.


      When prompted, ensure you delete the driver software for the devices.  Check the box and say "Ok".


      Step 3: Restart the Device


      Step 4: Being Plug and Play enabled, wait for a notification in the Action Center or a toast notification to restart to complete a driver installation for a Intel RealSense device.


      Step 5: Restart the device


      Step 6: Download the following link: http://download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/wushowhide.diagcab


      This is a troubleshooter to hide/block updates that can cause issues with Windows.  Run the tool and high any Intel Realsense Drivers that are newer than



      Step 7: If already installed, remove DCM.  Then Install DCM(Right-Click and Run as administrator.) Ensure you have the latest version of DCM installed.  Firmware Update your camera if you can(It is not required.)


      Step 8: Open up device manager and ensure all Imaging devices are underneath the Imaging Device Class.  You should see the following:




      Open up the Properties on the Depth Sensor Driver.  Verify that it says the following:

      Edit (5/17/2017:) If the driver is older than this, that is fine as well.  If the driver is from 2006(which is should be if you properly deleted your drivers), please do the following:

      Click on "Update Driver"

      Click on "Browse my computer for driver software"

      Click on "Let me pick from a list of available drivers on my computer"

      Un-Check "Show Compatible Hardware"


      Select "Intel" as the Manufacturer.

      Select "Intel (R) Realsense(TM) Camera SR300 Driver and next


      Restart the device afterward.


      Step 9:  Verify that Windows Hello works, Open Camera App, and even an app of your choice that may use the SDK.

      In the picture above, I have verified that User Segmentation/Dynamic Background removal is working.


      Step 10:  Wait for a actual driver update that corrects this issue.  This should be enough to get you guys by if you did happen to be an early adopter like me.




      Hopefully this works out for you guys!  Message me if you need any help!


      This post has been updated on 5/17/2017 based on a driver update that broke workaround on 5/8/2017

        1 2 3 Previous Next