Hi,
We’re running a long-term public installation using an Orbbec Femto Bolt and are investigating an intermittent failure that causes the sensor to disappear from Windows after several hours or days of operation.
Environment
- Orbbec Femto Bolt
- Firmware: 1.1.3
- Windows 11 Pro 25H2 (Build 26200.8246)
- Nuitrack 0.38.4
- Unity application
- Sensor powered through its dedicated external power supply
The installation runs daily in a museum environment.
Failure Symptoms
When the issue occurs:
- Body tracking stops working
- Nuitrack can no longer access the sensor
- Unity continues running normally
- The last received camera frame remains visible (appears frozen)
Device State During Failure
During the failure we captured the following state from Windows:
The Femto Bolt devices disappear and become phantom devices:
- Orbbec Femto Bolt RGB Camera
- Orbbec Femto Bolt Depth Camera
- USB Composite Device
These report:
- Status: Unknown
- Present: False
- CM_PROB_PHANTOM
At the same time Windows reports:
- Unknown USB Device (Device Descriptor Request Failed)
- VID_0000
- PID_0002
- CM_PROB_FAILED_POST_START
- Present: True
Example:
USB\VID_0000&PID_0002
The normal Femto Bolt VID_2BC5 / PID_066B interfaces are no longer active.
Recovery Attempts
The following do not recover the device:
- Restart Unity
- Restart Nuitrack
- Sensor power cycle
- Windows reboot
- Disable / Enable PnP device
- Remove device and rescan
- pnputil /scan-devices
After these actions the Femto Bolt devices remain phantom devices and the VID_0000 descriptor-failure device remains present.
What Does Recover It
The only confirmed recovery so far is:
- Complete shutdown of the installation
- Removal of AC power overnight
- Cold startup the following day
After this, the Femto Bolt immediately reappears and functions normally.
Additional Context
The installation operated reliably before the following Windows updates were installed on April 27, 2026:
- KB5088467
- KB5083769
- KB5082417
The failures were first observed after these updates were applied.
We have not established a direct causal relationship, but the timing appears significant enough to mention.
Current Investigation
We are currently looking into:
- Firmware stability
- USB host controller compatibility
- Windows USB power-management behaviour
- Interaction with Nuitrack timestamp settings
- Long-duration runtime stability
Questions
- Has anyone seen a Femto Bolt enter a VID_0000 / PID_0002 descriptor-failure state after extended runtime?
- Are there known firmware issues related to long-running installations?
- Are there newer firmware versions than 1.1.3 that address USB stability?
- Is there a recommended way to force a full USB re-enumeration of the device without physically removing power?
Any suggestions would be greatly appreciated.
Thanks.