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. Recovered remotely from 20,000 miles away without physical access, proprietary firmware files, or manufacturer support.
Camera firmware crashed during update and entered DFU bootloader mode - waiting for firmware upload but unable to function as a camera.
Get-PnpDevice | Where {$_.FriendlyName -like "*cam*"} |
Select Status, Class, FriendlyName, InstanceIdReturned Class: USB instead of Class: Camera - confirmed not recognized as camera.
# Navigate to dfu-util cd "Downloads\dfu-util-0.11-binaries\win64" # Verify working .\dfu-util.exe --version # List devices in DFU mode .\dfu-util.exe -l # Send exit command (primary method) .\dfu-util.exe -d 1bcf:0b1d -e # Alternate: exit with leave command .\dfu-util.exe -d 1bcf:0b1d -s :leave
Expected: Device disappears from Device Manager for a few seconds, then reappears as "Integrated Camera" under Cameras section.
# Reset Windows Camera app Get-AppxPackage Microsoft.WindowsCamera | Reset-AppxPackage # Force hardware rescan pnputil /scan-devices
DFU is a standardized USB protocol. When a device enters DFU mode, its bootloader runs instead of normal firmware. The bootloader can:
In this case, the firmware was intact - just stuck in bootloader mode after Windows update interrupted normal boot. The -e flag tells the bootloader "stop waiting for firmware, boot what you already have."
No firmware files needed. No proprietary tools. Just a standard USB DFU command.
Key takeaways:
Need expert remote IT support? We solve complex hardware and firmware problems remotely.
Contact Us