Driver Cannot Load On This Device – BtwUsb.sys | Fixes

You plug in a headset, USB Bluetooth dongle, or other gear and Windows suddenly throws up a box saying a driver cannot load on this device with BtwUsb.sys in the details. The device might still work, or it might stop responding, and Windows Security may start nagging you about Core isolation or Memory integrity.

This error ties back to stricter driver checks in Windows 10 and Windows 11. The system blocks older kernel drivers that do not meet current security rules, and the Broadcom Bluetooth USB driver behind BtwUsb.sys is a regular offender on some setups. The good news is that you can usually clear the warning with a mix of driver cleanup and a few Windows settings tweaks, without breaking Bluetooth for good.

This guide walks through what the message actually means, how BtwUsb.sys fits in, and several safe ways to stop the driver cannot load on this device – btwusb.sys pop-up from coming back.

What “Driver Cannot Load On This Device – BtwUsb.sys” Actually Means

When you see this alert, Windows is telling you that a specific driver failed a security check and will not be loaded into the kernel. Program Compatibility Assistant or Windows Security usually shows the short text A driver cannot load on this device, and the details point at BtwUsb.sys along with a note that a security setting is preventing the driver from loading.

BtwUsb.sys belongs to a Broadcom Bluetooth USB stack that ships with some OEM packages and VR headset drivers. On modern Windows builds, that stack relies on older driver behavior that conflicts with features such as Core isolation and Memory integrity, so the operating system blocks it to protect the kernel.

Under the hood, Windows checks drivers for things like valid digital signatures, support for virtualization-based security, and known compatibility flags. When a driver fails these checks, you get messages such as “A driver can’t load on this device” and the driver never starts, even though the hardware may still appear in Device Manager or work through another driver layer.

So the “Driver Cannot Load On This Device – BtwUsb.sys” alert does not mean your PC is broken beyond repair. It means a specific Bluetooth-related driver does not meet current security rules and needs either an update, a replacement, or to be removed if you no longer rely on it.

Quick Checks Before You Change Driver Settings

Before you start removing drivers or turning off security features, run a short set of checks. This keeps you from chasing the wrong cause and helps you pick the least disruptive fix for your setup.

1. Note When The Warning Appears — Watch whether the pop-up shows at boot, only when you launch SteamVR, or when you plug in a specific USB device. This tells you which hardware is tied to BtwUsb.sys.
2. Check Device Manager Status — Open Device Manager, expand Bluetooth and Universal Serial Bus controllers, and see whether any device shows a yellow warning mark next to it.
3. Run Windows Update — Open Settings > Windows Update and grab pending updates, including optional driver updates. Sometimes Microsoft ships a newer Bluetooth stack that replaces the one using BtwUsb.sys.
4. Open Windows Security — Go to Settings > Privacy & security > Windows Security > Device security and review the Core isolation and Memory integrity section for notes about incompatible drivers.
5. Confirm You Use The Linked Device — If the warning only appears when you plug in an old VR link box or legacy dongle you never use, you can often remove that driver package entirely instead of weakening security.

If these checks show that everything else on Bluetooth works well and only one accessory triggers the error, you can target the fix at BtwUsb.sys instead of reinstalling every driver on the system.

Driver Cannot Load On This Device – BtwUsb.sys Fixes For Windows 11 And 10

Once you know BtwUsb.sys is the culprit, you can follow a set of fixes in order. Start with updates and cleanup, then move toward deeper changes only if the warning refuses to go away.

Update Or Replace The Broadcom Bluetooth Stack

Many systems ship with a vendor-tuned Broadcom Bluetooth package. When that package is old, BtwUsb.sys may not satisfy current driver requirements. Replacing it with a newer release or a Microsoft Bluetooth driver often clears the error.

1. Get OEM Driver Packages — Visit your laptop, motherboard, or headset vendor site, search by exact model, and download the latest Bluetooth or VR support package made for your version of Windows.
2. Install Over The Existing Driver — Run the installer and let it update the stack; reboot when prompted so Windows reloads the new driver set.
3. Try The Microsoft Bluetooth Driver — In Device Manager, right-click the Broadcom Bluetooth USB device, choose Update driver, then Search automatically so Windows can pick a compatible in-box driver.
4. Reboot And Check For The Warning — After the restart, open Windows Security and confirm that the driver cannot load on this device – btwusb.sys alert no longer appears.

If your vendor has retired the Bluetooth stack tied to BtwUsb.sys and offers no newer package, the next step is to remove that stack and let Windows use a different one.

Remove Old Headset Or Dongle Drivers

On many systems, BtwUsb.sys arrives with VR headset software or a bundled USB Bluetooth dongle. When you stop using that gear, the driver can hang around and keep triggering security alerts even though you never rely on it anymore.

1. Uninstall Related Software — Open Settings > Apps > Installed apps and remove packages tied to your old VR headset, Bluetooth suite, or connection utility.
2. Delete The Device In Device Manager — In Device Manager, right-click the Bluetooth USB device that shows Broadcom or your headset name, choose Uninstall device, and tick the option to delete the driver software if Windows offers it.
3. Unplug The Hardware — Disconnect the VR link box or USB dongle that depended on BtwUsb.sys, then restart the PC so Windows can refresh its driver list.
4. Recheck Windows Security — After reboot, open Device security and confirm that the incompatible driver list no longer shows the BtwUsb.sys entry.

If you still use the hardware that shipped with BtwUsb.sys and no newer driver is available, you must decide whether to accept lower security or keep the device off the system.

Temporarily Turn Off Memory Integrity

Memory integrity uses virtualization-based security to shield the Windows kernel from malicious drivers. That layer blocks BtwUsb.sys on many builds, which is why you see the warning when you try to enable it. Turning Memory integrity off allows the driver to load again, but it also lowers protection, so treat this as a last resort or a short-term workaround.

1. Open Device Security — Go to Settings > Privacy & security > Windows Security, then choose Device security and open the Core isolation details link.
2. Toggle Memory Integrity Off — In the Core isolation panel, switch the Memory integrity slider off and restart when Windows asks.
3. Test Your Bluetooth Device — After the reboot, check whether your headset or Bluetooth device now works as expected without new warnings.
4. Plan A Safer Long-Term Setup — Look for updated drivers, a replacement device, or a generic Bluetooth adapter that does not rely on BtwUsb.sys so that you can turn Memory integrity back on later.

Leaving Memory integrity off for months just to keep one legacy device alive is rarely a good trade. In many cases, switching to newer hardware or a different driver stack gives you both working Bluetooth and a safer kernel.

Roll Back Or Reinstall Recent Updates

Some users only see the message after a major Windows feature update or a big driver bundle. In those cases, rolling back a specific driver or, in rare cases, the Windows build can remove the mismatch that triggered the BtwUsb.sys block.

1. Roll Back A Driver — In Device Manager, open the properties for the Bluetooth USB device, switch to the Driver tab, and use Roll Back Driver if the button is active.
2. Remove A Problem Update — In Settings > Windows Update > Update history, uninstall the last update that lined up with the start of the warning and reboot.
3. Use System Restore If Available — Launch System Restore, pick a restore point from before the first BtwUsb.sys alert, and let Windows revert system files and drivers.

Rollbacks work best when you can tie the first “A driver can’t load on this device” message to a specific update. If the problem has lingered for months, driver cleanup and replacement tend to give more stable results.

BtwUsb.sys And Windows Memory Integrity Security

BtwUsb.sys trouble often shows up next to Memory integrity warnings. That is not an accident. Memory integrity relies on virtualization-based security to keep kernel code in a protected region, so any driver that does not meet strict signing and compatibility rules gets blocked from loading.

Broadcom’s older Bluetooth USB stack was written before these rules hardened. On new Windows builds, that stack falls into the incompatible bucket, especially when bundled with certain VR headsets and OEM images. The system chooses safety over compatibility and stops BtwUsb.sys from running, which then breaks the link between your Bluetooth hardware and some headset tools.

Here is a quick overview of common ways to deal with BtwUsb.sys and how each one affects Memory integrity and overall security:

If you are unsure which route fits your situation, start at the top of this table and work downward. Most setups can avoid disabling Memory integrity by either updating the Bluetooth stack or retiring the hardware that depends on BtwUsb.sys.

How To Check Whether You Still Need The BtwUsb.sys Driver

In many homes and offices, this driver sticks around long after the hardware that needed it has been boxed up or replaced. Keeping a stray kernel driver in place only to trigger alerts is not helpful, so it is worth checking whether you really still rely on it.

Common sources for BtwUsb.sys include:

• VR headset link boxes — Some older VR kits install Broadcom Bluetooth support to manage controllers and base stations over USB.
• Bundled USB Bluetooth dongles — Adapter kits that shipped with their own driver disc or installer often bring BtwUsb.sys along.
• Legacy OEM Bluetooth suites — Older laptop images sometimes deploy Broadcom stacks instead of the lighter Microsoft Bluetooth drivers.

If none of those apply anymore, there is a fair chance you can remove the related software and let Windows fall back to simpler drivers. Before you do that, check which Bluetooth devices you truly care about today and confirm they use a driver you can replace.

1. List Active Bluetooth Devices — Open Settings > Bluetooth & devices and note which mice, keyboards, headsets, and controllers are currently paired and in use.
2. Match Devices To Drivers — In Device Manager, expand Bluetooth and view the properties for active devices to see whether they point to BtwUsb.sys or a different driver file.
3. Test With Hardware Unplugged — Disconnect any suspect dongle or link box, reboot, and check whether your day-to-day Bluetooth gear still works.
4. Remove Only What You Do Not Need — Uninstall software and drivers tied to retired hardware first, then confirm there are no new problems before going further.

By trimming unused drivers, you cut down on extra attack surface and reduce the odds that the driver cannot load on this device – btwusb.sys message will return after future Windows updates.

Preventing “Driver Cannot Load On This Device – BtwUsb.sys” From Coming Back

Once you have cleaned up or replaced the BtwUsb.sys stack, a few habits can keep the warning from showing up again with the next round of updates or hardware changes.

• Favor Vendor Updates Over Random Packs — Get Bluetooth and VR drivers from your device maker or Windows Update instead of assorted driver pack tools.
• Keep Windows Security Features On — Use Memory integrity and other Core isolation features by default, and only disable them when you have a clear short-term reason.
• Retire Old Hardware Promptly — When you box up a headset or dongle for good, uninstall its software and drivers so they stop loading in the background.
• Review Incompatible Drivers After Big Updates — After major Windows upgrades, peek at Device security to see whether any driver, including BtwUsb.sys, has moved into the incompatible list.
• Document What You Changed — Jot down which driver packages you updated or removed so it is easy to retrace your steps if a future update reintroduces the alert.

Handled with a bit of care, the “Driver Cannot Load On This Device – BtwUsb.sys” message becomes a one-time clean-up job rather than a constant nuisance. Update or remove the old Broadcom stack, keep Windows security features on when you can, and your system can stay stable without nagging driver pop-ups.

Send us your feedbackTell us what you thought about this post

⚠Please use a real email you check. If it's fake or mistyped, your message won't reach us and we can't reply — wrong addresses are rejected automatically.

Name *Email *

Your comment *

Quick check — what is …? *

Send feedback