Lenovo ThinkBook Camera Stuck in DFU Mode After Update
Incident Summary
Integrated camera on Lenovo ThinkBook 16 G6 ABP became unresponsive after Windows update, appearing as "WinUsb Device" in Device Manager. Camera firmware stuck in DFU (Device Firmware Update) bootloader mode. Successfully recovered remotely from 20,000 miles away without physical access, proprietary firmware files, or manufacturer support.
> Problem Identification
After a Windows 11 24H2 update, the integrated camera stopped working. Instead of appearing under "Cameras" in Device Manager, it showed up under "Universal Serial Bus devices" as "WinUsb Device".
> Device Manager Indicators
- •Device listed under "Universal Serial Bus devices" not "Cameras"
- •Shows as "WinUsb Device" instead of camera name
- •Hardware ID: USB\VID_1BCF&PID_0B1D
- •Driver: Generic USB driver, not camera-specific
This indicated the camera firmware crashed during the update and entered DFU bootloader mode—waiting for firmware upload but unable to function as a camera.
> Initial Diagnostics
First step: confirm the device state using PowerShell to query PnP devices.
This returned the device with Class: USB instead of Class: Camera, confirming it wasn't recognized as a camera.
> DFU Mode Technical Indicators
- •USB Class: 0xFE (Application Specific)
- •SubClass: 0x01 (Device Firmware Update)
- •Protocol: 0x02
- •Compatible ID: References USB Class_FE
> Required Tools
dfu-util (Primary Tool)
- →Source: SourceForge dfu-util project
- →Version: 0.11 (pre-compiled Windows binaries)
- →File size: ~500KB
- →Format: .tar.xz (requires 7-Zip to extract)
- →Executable location: win64 subfolder
USBDeview (Optional Diagnostic)
Provides detailed USB device enumeration. Helps confirm device status and USB class identification.
> Recovery Procedure
After downloading and extracting dfu-util, navigate to the directory and run the following commands.
Step 1: Navigate to dfu-util directory
Step 2: Verify dfu-util is working
Should return version information if the utility is working correctly.
Step 3: List devices in DFU mode
Should detect the camera with VID:PID 1bcf:0b1d if it's in DFU mode.
Step 4: Send exit command (Primary method)
This tells the bootloader to exit DFU mode and boot into normal camera firmware.
Step 4 (Alternate): Exit with leave command
Alternative syntax that achieves the same result.
Expected behavior: The device will disappear from Device Manager for a few seconds, then reappear as "Integrated Camera" under the Cameras section. The Windows Camera app should now detect and work with the camera.
> Troubleshooting: If dfu-util Can't Detect Device
In some cases, dfu-util may not detect the device even though it's in DFU mode. This is usually a driver issue. Solution: use Zadig to reassign the USB driver.
> Zadig Driver Reassignment Procedure
- 1.Download and run Zadig (zadig.akeo.ie)
- 2.Enable "Options → List All Devices"
- 3.Locate the SunplusIT camera device in the dropdown
- 4.Select libusbK or libusb-win32 as the target driver
- 5.Click "Replace Driver" and wait for completion
- 6.Retry
dfu-util.exe -lto confirm detection - 7.Run the exit command once dfu-util detects the device
> Post-Recovery Verification
After successful recovery, verify the camera is working and properly recognized.
Reset Windows Camera app
Force hardware rescan
Nuclear option: Remove and re-detect device
Only use if camera still isn't detected. This removes the device and forces Windows to rediscover it.
> Why This Works
DFU (Device Firmware Update) mode is a standardized USB protocol defined in the USB specification. When a device enters DFU mode, its bootloader is running instead of the normal firmware. The bootloader has a simple command set that includes:
- •Upload new firmware
- •Download current firmware
- •Exit bootloader and boot into existing firmware
In this case, the camera's firmware was intact—it just got stuck in bootloader mode after the Windows update interrupted the normal boot process. The -e flag in dfu-util sends the "exit/detach" command, telling the bootloader "stop waiting for firmware, boot what you already have."
No firmware files needed. No proprietary tools. No manufacturer support. Just a standard USB DFU command that works on any DFU-compliant device.
> Outcome
Camera functionality fully restored without physical access, firmware files, or manufacturer support. Performed entirely via remote desktop session from 20,000 miles away. Total resolution time: under 10 minutes. Zero hardware downtime.
Verified Compatibility:
- →Lenovo ThinkBook 16 G6 ABP (AMD Ryzen 7 7730U)
- →SunplusIT integrated camera (VID 1BCF, PID 0B1D)
- →Windows 11 24H2 build
Key Takeaways:
- →Understanding standard protocols (USB DFU) enables vendor-independent solutions
- →"Firmware stuck in bootloader" doesn't always mean firmware corruption
- →Remote hardware troubleshooting is viable with correct tooling and USB-level access
- →Open-source utilities (dfu-util) can outperform proprietary manufacturer tools
> Tools Referenced
dfu-util
Device Firmware Update utility for USB devices. Cross-platform (Windows/Linux/macOS).
dfu-util.sourceforge.net →Zadig
USB driver installation tool for Windows. Enables driver reassignment for USB devices.
zadig.akeo.ie →USBDeview
Advanced USB device viewer showing detailed hardware information and USB descriptors.
7-Zip
File archiver required to extract .tar.xz files containing dfu-util binaries.
Need Expert Remote IT Support?
We solve complex hardware and firmware problems remotely. From camera bootloaders to network infrastructure, we handle the issues other MSPs escalate.
CONTACT_US