Realtek Camera Driver Compatibility Issue – Latitude 7400

We reviewed multiple threads across Dell Community and haven’t found any confirmed fix for VID_0BDA&PID_585B on Latitude 7400. Most users report similar issues after upgrading to Windows 11 24H2, and Dell’s official drivers don’t list this PID. Has anyone successfully restored camera functionality without modifying INF files or disabling usbvideo.sys manually?

Hi

The internet reports........

The USB device with hardware ID USB\VID_0BDA&PID_585B&REV_8710&MI_00 is manufactured by Realtek.

Part numbers such as 093THN or HK46K.

So tracking down the correct driver may be tricky....

This driver is not compatible.  This driver is not applicable for XXXXXXX with Windows 11.

You can search for a similar driver for this device or check to see if this driver is compatible with another device.

Windows 11 includes native drivers for integrated webcams. 

Unfortunately it seems that you have progressed as far as you can, and there are no better drivers or solutions than already tried.

@anne_droid​ 

Thanks for your reply. To clarify, I’ve detected two camera devices on this system:

1. Integrated Realtek USB Camera

• Hardware ID: USB\VID_0BDA&PID_585B&REV_8710&MI_00

• This is the built-in camera module in the Latitude 7400.

• Windows assigns usbvideo.sys, which fails to initialize the device.

• Dell’s official driver does not list this PID, and newer Realtek drivers (e.g., 10.0.22000.20362) also don’t support it natively.

2. Secondary Camera Device

• Hardware ID: USB\VID_32E6&PID_9221&MI_00\6&1f91bb17&0&0000

• Possibly an external USB camera or an IR module.

• I attempted manual installation using oem87.inf, but the device isn’t recognized without INF modification.

If you or anyone else has successfully restored camera functionality on a Latitude 7400 with this Realtek module under Windows 11 24H2 — ideally without modifying INF files or using DevCon — I’d greatly appreciate your input.

When Windows assigns the generic usbvideo.sys driver to the camera, it installs a system-provided UVC driver with a fixed timestamp: Driver Date: 06/21/2006 Driver Version: 10.0.xxxxx.xxxx This is intentional — Microsoft uses the original Windows Vista RTM date to ensure their driver ranks lower than OEM drivers when both match the same hardware ID. However, in this case, the Realtek module is not matched by any OEM driver, so usbvideo.sys remains active and fails to initialize the camera properly.

Driver enumeration results:

Using pnputil /enum-devices /connected, I confirmed the following:

1. Realtek USB Camera

   • Hardware ID: USB\VID_0BDA&PID_585B&REV_8710&MI_00

   • Driver: usbvideo.inf (Microsoft UVC)

   • Version: 10.0.22621.1

   • Date: 06/21/2006

   • Status: Loaded but camera not functional

2. Secondary Camera

   • Hardware ID: USB\VID_32E6&PID_9221&MI_00

   • Driver: oem87.inf (manually installed)

   • Status: Device present but not working correctly

The Microsoft UVC driver (usbvideo.sys) is dated June 21, 2006 by design, to rank below OEM drivers. However, since no OEM driver matches PID_585B, the system defaults to usbvideo.sys, which fails to initialize the camera.

I’ve blocked usbvideo.sys via registry and prevented driver updates via Windows Update, but no Dell or Realtek driver binds to the device natively. Manual INF editing works temporarily but breaks under Windows Update or signature enforcement.

@Kelemvor 

Use Snappy Driver Installer - let the tool find the correct driver for your cam.
All my cams are up and running now.
HTH

Peter

@petermuss​  Snappy Driver Installer cant find any update or downgrade drive for my both integrated camera