Bcm92035dgrom Driver Windows 10 May 2026

Before downloading any driver, check your Hardware ID to make sure the BCM92035DGROM driver matches.

Steps:

Look for something like:

USB\VID_0A5C&PID_2009

If you see PID_2009 or PID_200A, you have the correct Broadcom chip.

Once the driver is correctly installed, Device Manager will show:

Test connectivity:

Here is the core issue: Broadcom officially ended support for the BCM2035 series chipsets after Windows 7. Microsoft did not include native inbox drivers for this legacy chipset in Windows 10. Consequently, after a Windows 10 update or fresh installation:

But don’t throw away that hardware yet. Although official support is gone, community-tested drivers do exist and function correctly on 64-bit and 32-bit versions of Windows 10 (up to version 22H2).

Windows 10 dropped native support for many older Bluetooth chipsets, especially Broadcom's BCM2035-based modules. The BCM92035DGROM uses a generic USB Bluetooth radio often rebranded by Dell, HP, or Asus. Bcm92035dgrom Driver Windows 10

Common problems after installing Windows 10:

The BCM92035DGROM is, effectively, a zombie. It is hardware that refuses to die but has been abandoned by its creators. Manufactured by Broadcom—a giant in the semiconductor industry—the chipset was ubiquitous in the early 2010s. It offered reliable Bluetooth connectivity in an era when the standard was still solidifying.

The problem arises because Broadcom, like many hardware manufacturers, operates on a model of planned progression. When Windows 10 arrived, bringing with it a new driver architecture and a strict enforcement of driver signing and security, the BCM92035DGROM was left behind. There was no financial incentive for Broadcom to write new drivers for a chip they no longer sold. The official stance was simple: buy a new laptop or buy a USB Bluetooth dongle. Before downloading any driver, check your Hardware ID

However, users are rarely so willing to discard functional hardware. This set the stage for a bizarre game of digital cat-and-mouse between the operating system and the hardware.

Fix: