Share via

brusbsib.sys incompatible driver preventing memory integrity from functioning

Anonymous
2023-01-19T00:52:12+00:00

So I have read multiple resources on brusbsib.sys and cannot find an accurate solution to solve the problem. I have tried to remove the driver manually by using pnputil command in PowerShell and I end up with many errors upon reboot: sound isn't configured, event manager will not run, system restore program will not run, and other vital errors. I had to boot into repair mode and restore my computer settings to make it usable and semi-secure again.

I have tried updating brusbsib.sys as well and that function does not seem to work either because upon reboot it still shows as incompatible.

I am at my wits end here. I don't want to have to factory reset my computer and avoid downtime but that seems like my best and only option at this point. What else can I do if I can't update it/repair it/remove it?

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

34 answers

Sort by: Most helpful
  1. Anonymous
    2023-04-08T00:12:15+00:00

    I echo your problem and frustration, but I finally found a solution that hopefully will help you, too.

    Go to: GitHub - lostindark/DriverStoreExplorer: Driver Store Explorer [RAPR]

    Read about DRIVER STORE EXPLORER and then scroll down to download the RAPR.exe file: https://github.com/lostindark/DriverStoreExplorer/releases/latest

    It allowed me to scan my C:\Windows\System32\DriverStore folder to identify all the Brother related files and get rid of most of them. Then I rebooted my PC and successfully turned-on Core Isolation. I rebooted again to confirm Windows Security was all OK, and then reloaded my Brother applications and drivers for trouble-free operation of my Brother printers and scanner.

    I'm no computer expert so don't ask me how it works. Good luck to you!

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-01-19T02:03:03+00:00

    Hi Nick,

    My name is Cindy. I am sorry you are having this problem. I know it is really frustrating. I will do my best to help you with this problem.

    Please note: This is a user-to-user community forum. We are users just like you who help others. We are not employees of Microsoft, nor do we have access to your account information.

    Windows has a feature that allows users to scan for corruptions in Windows system files and restore corrupted files. I have enclosed the directions below. You can cut and paste the code.

    1. Type cdm in the search box. Do not hit enter.
    2. select Run as Administrator then hit enter.
    3. Then type without the quotes. "DISM.exe /Online /Cleanup-image /Restorehealth" and hit enter.

    On the same page run these two scans below.

    sfc /scannow

    DISM /Online /Cleanup-Image /StartComponentCleanup

    Please let me know if you continue to have a problem.

    Best Wishes,

    Cindy

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-01-17T15:40:32+00:00

    The above reply helped, but I also had to do 1 more thing.

    The process went as follows:

    1. in CMD (admin) write: "pnputil /enum-drivers >c:\enumdrivers1.txt"
    2. open the "enumdrivers1.txt" file from C:\
    3. Search for "Brother"

    -> I found this:

    Published Name: oem5.inf

    Original Name: brpri07b.inf

    Provider Name: Brother

    Class Name: Printer

    Class GUID: {4d36e979-e325-11ce-bfc1-08002be10318}

    Driver Version: 07/21/2009 1.1.0.0

    Signer Name: Microsoft Windows Hardware Compatibility Publisher

    1. take the "oem5.inf" (it may be different on your PC) and use it in a command in CMD:
    2. "pnputil /delete-driver oem5.inf /uninstall /force"
    3. "pnputil /delete-driver oem5.inf /force"

    That fixed it. What I added was the step 6, because without the "/force" it could not be deleted. But it may be that the step 5 would have been enough, but after using step 6, it finally gave the information that the driver has been succesfully deleted. Thanks for Jacobacci.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-10-17T23:34:05+00:00

    I spent many hours on this also. I figured out the hard way and posted in a similar thread elsewhere.

    I sent it to Brother and they will not update / fix the uninstall driver app or update the driver itself.

    Their instructions….

    “Our engineers provided the following procedure to remove the driver components related to the issue. Removing these

    will cause PC Fax Receive and Remote Setup to be unavailable, but printing and scanning will not be affected.

    There is not currently a plan to update drivers for these older models.

    This is the procedure to remove the driver files:

    open command prompt, terminal or powershell as administrator,

    type:

    pnputil /enum-drivers >c:\enumdrivers1.txt

    This sends the data to a text file which can be searched. The file will be saved to the c:\ drive

    Search this file for brpoc12a.inf then write down the name of the oem***.inf files that are associated with them

    (something like oem249.inf, but the numerals will be different on each computer).

    Back to command prompt, type:

    pnputil /delete-driver oem***.inf

    (where the *** should be replaced with the numerals found in the previous steps)

    It may also help to remove the following registry key if present:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BrUsbSer

    Restart the computer, then enable Memory Integrity

    At your side,

    Mike

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-02-13T03:32:34+00:00

    I'm running the latest Win11 and ran into the issue, then I'm trying to fix it through reset/restore the system, unfortunately the issue is still around.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments