Some additional important info I've just discovered:
When connecting the SR300 to the USB port that works, 3 imaging devices are shown in the device manager: Depth, RGB and Virtual driver.
When connecting the SR300 to the USB port that doesn't work, only 2 imaging devices are shown in the device manager: Depth and RGB.
Below is a snapshot of my device manager when the SR300 is connected to the working USB port, with the virtual driver is marked in the red rectangle, and a snapshot of the device manager when the SR300 is connected to the faulty USB port (you can clearly see that the virtual driver is missing).
Seems like the virtual driver fails to start for the faulty USB port.
After trying many things, I have finally found a way that fixes the problem:
In "Connected Device Settings", I uninstalled the SR300.
Then I disconnected and reconnected it to the USB port.
Since I uninstalled the SR300, Windows is reinstalling it.
After that, the SR300 is working again.
Having said that, my solution is just a bypass.
It does not explain, why the SR300 stopped working on that specific USB port in the first place.
This solution also doesn't guarantee that this problem will not happen again.
Therefore, I would appreciate if someone from Intel can look into this issue and advise.
As I mentioned at the beginning of this post, I have another NUC with the same problem.
I will apply this solution on that NUC as well, as soon as this NUC will be available.
Once I'll do that, I will update if it fixed the problem on the second NUC too.
Thank you for joining the Intel communities.
For system requirements the Intel® Realsense SR300 camera requires a 6th generation processor as you can see here:
At this point for better support please POST your issue to the developers group, you can POST it at the following link:
Thank you for your reply.
I am aware that one of the SR300 requirements, but it doesn't seems like a problem that is caused by using a 5th generation processor instead of 6th.
Can you say for sure that using 5th generation processor is the root cause of this problem?
Did you see this problem happen with SR300 on non-6th generation processors before?
I've posted my issue in the developers group as you suggested (with the same topic), so we can continue the discussion there.
In order to get the proper support for you Intel® Realsense SR300 camera I suggest you to post this issue at the following link: