How to Fix brusbseb.sys BSOD in Windows 10 & 11

Fix brusbseb.sys blue screen errors permanently. Learn how to delete this legacy Brother USB driver and restore Windows 11 Memory Integrity safely.

If you’ve ever stared at a blue screen of death (BSOD) blaming brusbseb.sys, or found yourself unable to turn on Windows 11’s Memory Integrity due to an "incompatible driver," you’re not alone. This isn’t a rare glitch—it’s a known conflict between an older Brother printer USB driver and modern Windows security features. I’ve helped users diagnose this exact issue dozens of times, and the good news is that you rarely need a full system reset.

The file brusbseb.sys is part of Brother’s USB printer software. While it used to work fine, Windows 10 and 11 now block it because it lacks the updated signatures required for Core Isolation. This typically manifests as a System Thread Exception brusbseb.sys crash loop or a security warning preventing memory integrity from enabling. In this guide, I’ll walk you through everything from simple quick fixes to deep manual removal, so you can fix brusbseb.sys errors once and for all.

A multi-screen workstation showcasing coding on monitors and a laptop.

What Is brusbseb.sys And Why It Causes System Thread Exception

Understanding the File's Origin

At its core, brusbseb.sys is a driver file installed by Brother printer software. It serves as the communication bridge between your PC and a Brother printer connected via USB. You’ll typically find this file in the system drivers folder, such as C:\Windows\System32\drivers.

The problem arises because this driver is often legacy code. Brother hasn’t always prioritized updating these specific kernel-level drivers for the latest Windows security architectures. When Windows 10 or 11 attempts to load this driver alongside its newer security protocols, a mismatch occurs. Think of it like trying to plug a two-prong adapter into a three-prong socket—the physical connection exists, but the system rejects it because it’s not up to modern safety standards.

Common Error Codes and BSOD Variants

When brusbseb.sys causes trouble, it usually does so in one of two ways: a sudden crash or a security block. Below is a breakdown of what you might see on your screen.

Error TypeDescriptionLikely Cause
SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDA blue screen crash where the system thread fails to handle an exception.The driver is corrupted or incompatible with the current OS version.
Memory Integrity WarningWindows Security blocks the driver from loading to protect the system.The driver is unsigned or not certified for Windows 11 Core Isolation.
Code 39 Device ErrorDevice Manager shows the printer/USB controller has failed.The driver file is missing or corrupted upon boot.
bsusbseb.sys not foundApplication fails to start because the DLL/sys is gone.Previous uninstallation left remnants, or the file was manually deleted incorrectly.
Understanding these codes helps you decide whether you’re dealing with a simple corruption issue or a deeper security conflict. If you’re seeing crash loops, we need to repair the file. If you’re seeing security warnings, we need to remove the file.
Cyberpunk-themed setup with laptops, keyboards, wires, and retro tech items in a dim room.

Method 1: Quick Fixes for brusbseb.sys in Windows 10 and 11

Before diving into the registry, always try the low-risk troubleshooting steps. These won’t work every time, but they can resolve issues caused by temporary glitches or loose connections.

Restart and Basic Troubleshooting

It sounds obvious, but many BSOD events are triggered by a simple USB handshake failure. If your Brother printer is connected and the error persists, try this:

  1. Unplug the USB cable connecting your printer to the PC.
  2. Restart your computer.
  3. Once back in Windows, check if the system is stable.

If the crashes stop, the issue may be a loose connection or a power state conflict. Re-plug the printer only after you’ve confirmed stability. I’ve seen this solve the "crash on boot" scenario where the driver tries to initialize before the USB stack is fully ready.

Running System File Checker (SFC)

If the driver file is corrupted, Windows can sometimes repair itself. The System File Checker (SFC) tool scans protected system files and replaces incorrect versions.

  1. Type cmd in your Start menu search.
  2. Right-click Command Prompt and select Run as administrator.
  3. Type the following command and press Enter: sfc /scannow

This process can take 10–15 minutes. If SFC finds and repairs corrupted files associated with the driver, reboot your PC and test again. It’s a non-destructive step that resolves many "phantom" driver errors.

Updating Drivers via Device Manager

Sometimes, the issue isn’t the Brother driver itself, but the USB controller driver that hosts it.

  1. Right-click the Start button and select Device Manager.
  2. Expand the Universal Serial Bus controllers section.
  3. Look for any device with a yellow warning icon or any entry related to "Brother" or "USB Printing Support."
  4. Right-click the device and choose Update driver > Search automatically for drivers.

If updating doesn’t help, try Roll Back Driver if the option is available. This reverts the driver to a previous version that might have been stable before a Windows Update broke it.

Method 2: Deep Clean - How to Delete brusbseb.sys Permanently

If the quick fixes didn’t work, the driver is likely persisting in your system because standard uninstallation leaves behind "stub" files. This is the most common reason users return to forums asking how to delete brusbseb.sys completely.

Uninstalling Brother Software via Control Panel

Start with the official removal process.

  1. Go to Settings > Apps > Installed Apps (or Control Panel > Programs and Features).
  2. Locate any software with "Brother" in the name (e.g., Brother Printer, Brother iPrint&Scan).
  3. Click Uninstall and follow the prompts.
  4. Restart your computer.

Here’s the catch: many users report that even after this, the brusbseb.sys error returns upon reboot. This is because the driver remains registered in the Windows Driver Store, hidden from the standard app list.

Using pnputil to Remove Stub Driver Files

To truly remove the file, we need to delete it from the driver store using the Command Prompt. This is the definitive way to update brusbseb.sys context by removing it entirely.

  1. Open Command Prompt as Administrator.
  2. First, list all installed drivers to find the Brother entry: dism /online /get-drivers /format:table (Alternatively, you can use pnputil /enum-drivers)
  3. Look for a driver where the "Published Name" is something like oemXX.inf and the "Provider Name" is Brother. Note the oemXX.inf name (the number varies by system).
  4. Delete the driver using the following command (replace oemXX.inf with your identified file): pnputil /delete-driver oemXX.inf /uninstall /force

The /uninstall flag removes the associated software, and /force ensures it doesn’t get re-installed immediately. After running this, reboot your PC. The blue screen error should be gone.

Registry Cleanup (Advanced)

In rare cases, residual registry keys can cause the driver to reload automatically. Only attempt this if you are comfortable editing the registry.

  1. Press Win + R, type regedit, and hit Enter.
  2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
  3. Look for a folder named BrUsbSer or similar Brother-related entries.
  4. Right-click and Delete the key.

Warning: Incorrect registry edits can damage your Windows installation. Always create a system restore point or export the key before deleting anything. I recommend skipping this step unless the pnputil method fails, as it is rarely necessary for most users.

Method 3: Addressing Core Isolation and Memory Integrity Issues

For Windows 11 users, the issue often isn’t a crash, but a security warning. You try to turn on Memory Integrity and get an error saying an incompatible driver, brusbseb.sys, is blocking it.

Why Windows 11 Blocks the Driver

Windows 11 introduced Core Isolation and Memory Integrity as mandatory security features. These features use virtualization to ensure that only trusted, digitally signed drivers can run in the kernel space. Older Brother drivers like brusbseb.sys were created when these security standards didn’t exist. They are often unsigned or signed with certificates that Windows 11 no longer trusts.

As a result, Windows simply refuses to load the driver when Memory Integrity is active. It’s not that the driver is malicious; it’s just technically "unsafe" by modern standards.

Temporary Workaround: Disabling Memory Integrity

If you cannot remove the driver and need to use your printer immediately, you can disable Memory Integrity.

  1. Go to Settings > Privacy & security > Windows Security.
  2. Click Open Windows Security > Device security.
  3. Under Core isolation details, click Core isolation details.
  4. Toggle Memory integrity to Off.

Safety Implications: Disabling Memory Integrity lowers your system’s defense against kernel-level malware. While it allows your older Brother printer to function, it leaves you more vulnerable to sophisticated attacks. I only recommend this as a short-term bridge while you set up a new printer driver.

Restoring Security After Fix

Once you have successfully removed the driver using the methods in Section 2, you should re-enable Memory Integrity to restore your system’s security posture.

  1. Toggle Memory integrity back to On.
  2. Restart your computer.
  3. If the prompt about the incompatible driver no longer appears, the fix was successful.

If the error persists after removal, it indicates that another Brother driver (perhaps for a scanner or fax feature) is still present. Repeat the pnputil deletion process to hunt down the remaining oem*.inf file.

Prevention: Managing brusbseb.sys USB Driver Conflicts

To avoid this issue in the future, proactive management of your drivers is key.

Keeping Drivers Updated via Windows Update

Windows Update often pushes compatible driver versions. Regularly check for updates by going to Settings > Windows Update > Advanced options > Optional updates. Here, you may find newer printer drivers provided by Microsoft or Brother.

Additionally, visit the official Brother support site and download the latest full driver package for your specific model. Newer packages often include updated USB drivers that are compatible with Windows 10/11 security features.

When to Consider BIOS Updates

In some cases, the conflict between USB drivers and the OS is exacerbated by outdated motherboard firmware. A BIOS update can improve USB controller compatibility and resolve persistent driver conflicts.

However, BIOS updates carry risk. Ensure your laptop is plugged in and your PC is stable before proceeding. Check your computer manufacturer’s website (Dell, HP, Lenovo, etc.) for BIOS updates, but only install them if they specifically mention USB or stability improvements. For most users, keeping Windows and printer drivers updated is sufficient to prevent brusbseb.sys errors.

FAQ

Is brusbseb.sys a virus or safe? brusbseb.sys is a legitimate driver file from Brother Industries, not malware. However, malware can sometimes masquerade as system files. To verify authenticity, check the file location. It should be in C:\Windows\System32\drivers. If you find it elsewhere, run a scan with Windows Defender or Malwarebytes.

How do I delete brusbseb.sys completely? The most effective method is using pnputil. Open Command Prompt as admin, run dism /online /get-drivers to find the Brother driver’s oemXX.inf name, and then execute pnputil /delete-driver oemXX.inf /uninstall /force. This removes the stubborn stub files that standard uninstallation misses.

Why does my computer crash with brusbseb.sys? Crashes usually occur because the driver is incompatible with the current version of Windows, leading to a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error. The driver attempts to execute code that Windows no longer permits, causing the system thread to fail and the blue screen to trigger.

Can I update brusbseb.sys driver automatically? Windows Update may offer a generic USB printer driver, but it often does not update the specific Brother kernel driver. For the best results, manually check Brother’s official support website for the latest driver package tailored to your printer model.

Conclusion

Dealing with a brusbseb.sys error can be frustrating, but it is almost always solvable without a full Windows reinstall. The key takeaway is that this is rarely a virus—it’s a compatibility conflict between legacy hardware software and modern Windows security.

I recommend starting with Method 1 (SFC and basic troubleshooting) to rule out simple corruption. If the issue persists, move to Method 2 and use pnputil to perform a deep clean of the driver store. This is the step most users miss, and it’s usually the one that fixes the problem. Finally, ensure you re-enable Memory Integrity after removal to keep your Windows 11 system secure.

If you’re still stuck, please share your specific error code and Windows version in the comments below. We can help you identify the exact oem file you need to remove. For more guides on Windows security and driver management, check out our related articles on Core Isolation and system troubleshooting.

← Back to Home