D435 13:35:57 [Error] acquire_power failed: "The system cannot find the path specified."

[DevInOrbit]

Windows 11
Latest RealSense SDK and Viewer (13:30:14 [Info] - librealsense version: 2.56.5)
D435 with recently updated FW (same issue before FW update) 5.17.0.10
Ensured permission is granted in Windows 11 for camera access by all apps.
Started Viewer with admin mode|
USB 3.1 ports on Asus ROG Strix laptop
Tried 3 cables including high amperage model
No UXW driver is installed, using default driver and it shows up properly in device manager with no errors

When plugging in camera it is not recognized the the following error is rendered in the logs:

13:35:57 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\uvc-sensor.cpp:428 - acquire_power failed: MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070003: "The system cannot find the path specified."

Of note: Sometimes rs-fw-update -l returns the expected camera details, and sometimes it returns this:

Connected devices:
21/10 13:40:43,309 ERROR [25628] (uvc-sensor.cpp:428) acquire_power failed: MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070003: "The system cannot find the path specified."
21/10 13:40:43,352 ERROR [25628] (rs.cpp:256) [rs2_create_device( info_list:0000026DD8B69BB0, index:0 ) UNKNOWN] MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070003: "The system cannot find the path specified."
21/10 13:40:43,363 ERROR [25628] (rs.cpp:256) [rs2_delete_device( device:nullptr ) UNKNOWN] null pointer passed for argument "device"
21/10 13:40:43,372 WARNING [25628] (rs.cpp:392) null pointer passed for argument "device"
RealSense error calling rs2_create_device(info_list:0000026DD8B69BB0, index:0):
MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070003: "The system cannot find the path specified."

Or this:

There are no connected devices

This happens with no changes to the camera, simply running the command repeatedly.

[MartyG-RealSense]

Hi @DevInOrbit Do you experience the same problem if you visit the link below, go to the 'Assets' file list at the bottom of the page and then download and run the standalone version of the Viewer by clicking on intel.RealSense.Viewer.exe

https://github.com/IntelRealSense/librealsense/releases/tag/v2.56.5

The downloaded file should be run, and not the Viewer launch shortcut on the Windows desktop.

[DevInOrbit]

When trying per above the same issue presents, here is the console output when I run the fw cli:

C:\Users\bert\Desktop\realsense d435\fw\d400_series_production_fw_5_17_0_10>rs-fw-update -l

There are no connected devices

C:\Users\bert\Desktop\realsense d435\fw\d400_series_production_fw_5_17_0_10>rs-fw-update -l

Connected devices:

1. [USB] Intel RealSense D435 s/n 934222072162, update serial number: 935723023935, firmware version: 5.17.0.10

C:\Users\bert\Desktop\realsense d435\fw\d400_series_production_fw_5_17_0_10>rs-fw-update -l

Connected devices:
22/10 09:01:59,483 ERROR [16552] (uvc-sensor.cpp:428) acquire_power failed: MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070003: "The system cannot find the path specified."
22/10 09:01:59,519 ERROR [16552] (rs.cpp:256) [rs2_create_device( info_list:00000226ED1F6AF0, index:0 ) UNKNOWN] MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070003: "The system cannot find the path specified."
22/10 09:01:59,533 ERROR [16552] (rs.cpp:256) [rs2_delete_device( device:nullptr ) UNKNOWN] null pointer passed for argument "device"
22/10 09:01:59,540 WARNING [16552] (rs.cpp:392) null pointer passed for argument "device"
RealSense error calling rs2_create_device(info_list:00000226ED1F6AF0, index:0):
MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070003: "The system cannot find the path specified."

[MartyG-RealSense]

As the camera details can be accessed sometimes but not others, it sounds as though the issue may be with the USB ports on the laptop having problems with the camera. Ports are managed by a 'USB controller' component chosen by the computer manufacturer, and some brands of controller work better with RealSense cameras than others.

A way of testing whether it is a port related problem would be to obtain a mains electricity powered USB3 hub device and attaching the camera to the hub instead of the laptop ports. Hubs have their own USB controller separate from the one on the computer, and the ports of a powered hub have greater stability than built-in computer ports as they are drawing power from the mains plug socket rather than the computer's power supply,

Another USB diagnostic technique is to listen for the Windows USB connect / disconnect sound effect. When a USB device is successfully detected, Windows should make a 'boom-BOOM' sound effect when connected, and make a lower-key 'boom-boom' sound when a disconnection occurs. If you hear the boom-BOOM connect sound and soon after hear the boom-boom disconnect sound, it would strongly indicate a stability issue with the USB port in regard to handling your RealSense camera.