It seems there is a second driver needed - when the sensor is switched into DFU mode.
Under windows 10 - the device is not recognised correctly when it is in the mode.
Even more problematic is the UWP Driver ... Intel RealSense D400 Series UWP Driver v126.96.36.199
which continually keeps putting the sensor into DFU mode to attempt to do a firmware update
... to 5.9.0.x when the device is already at 188.8.131.52 ...
Eventually managed to disable the RS400 service to at least allow the device to keep running on windows 10.
But right now its a complete mess - this really needs to be fixed ... not a professional look at all
I have had no further problems since updating my d435 using Win8.1 and the update tool which is labeled as a Win10 download:) ... just to repeat the tool works fine for 8.1, but this isn't indicated anywhere on the download page.
There must be something about Win10 that is giving the engineers fits. In the Viewer 3d mode, in Win8.1, with the D435, you can cycle the source of the image being reconstructed... ir1, ir2, color, really slick and very useful. In Win10 no such luck. I'm guessing there is a flag somewhere that didn't get set and can't be scripted.
using the DFU tool - the device does not update - it puts the sensor into DFU mode - but windows fails to connect to a valid driver and the device remains in a locked state until you disconnect and reconnect it to the computer.
using the UWP Driver ... Intel RealSense D400 Series UWP Driver v184.108.40.206 - the problems are different.
It installs a RS400 service which attempts to UPDATE the firmware every time you connect the device --
Problem is - firstly the firmware on the sensor is NEWER than the firmware it wants to install
- secondly it also tries to put the sensor in to DFU mode every time - which fails - LEAVING the sensor in an unusable state.
The only current workaround is the disable toe RS400 service in the windows SERVICES panel
Thanks so much for your feedback about the firmware and for your workaround.
The UWP driver is a general-purpose driver for UWP compatibility and is not specially written for the RealSense cameras. So use of UWP with the firmware tool is not a guarantee that the firmware update process will work better with Windows.
This message was posted on behalf of Intel Corporation
Please follow the instructions below:
- Open Device Manager
- Expand Imaging Devices
- Right click on each entry for Intel RealSense 430 with RGB Module and...
- Select "Uninstall this device."
- In the Uninstall Device dialog box, check the box for "Delete the driver software for this device" (this option will not be available for the second device) and click Uninstall.
- Unplug and re-plug in the camera.
- Verify that the uninstallation worked...
- Check that the entries for the D435 in Device Manager are now under Cameras
- Right click on each device, select Properties, Manufacturer should be listed as Microsoft.
Thanks --- this does at least remove the UWD driver it seems ... but it still does not seem to resolve the original issue that it is not possible to update to the latest firmware on windows 10.
Intel (TM) Firmware Update:
 Intel(R) RealSense(TM) 435 with RGB Module Depth (FW Version: 220.127.116.11)
Enter camera number to update: (any out of bounds index to go back to main menu)1
Enter path and filename (e.g. c:\Documents\newFirmware.bin: )Signed_Image_UVC_5_9_11_0.bin
Updating firmware to Signed_Image_UVC_5_9_11_0.bin
No DFU device was connected
Failed to burn firmware
Press any key to continue . . .
And Windows device manager still shows:
WinUsb Device - with an error.
And assistance would be greatly appreciated
Have tried that - its not stuck in Upgrade mode.
I can access the device in the viewer and it works fine.
It shows up as a device that is able to be upgraded.
BUT when I run the upgrade in the DFU - it fails.
When the upgrade starts - the DFU software seems to try to put the d435 into and upgrade mode - BUT windows then reports that
The last device you plugged in failed - and the sensor is now suck until i disconnect and reconnect it ...
The previous firmware upgrade worked fine.
But since the last windows update it seems like there is a driver issue of some sort.
Would appreciate any assistance in getting this device upgraded to latest firmware