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-12-11T17:36:17+00:00

    I have battled with this issue several times until finding the final solution.

    There are several instances where brUSBsib.sys may be rearing its ugly head (usually in the context of memory integrity settings

    There is the old driver itself which conflicts with memory integrity. Look in memory integrity settings what the oem number of the driver is and then remove it using an admin command prompt and pnputil /delete-driver oemxx.inf /uninstall /force

    If this does not cure the issue, the registry entry of the driver might still be there. This manifests itself by a driver brUSBslb (slb NOT sib) being mentioned as incompatible in the memory integrity settings.

    Image

    To remove this, open regedit and search for brUSBsib.sys. The corresponding registry key is called brUSBslb. Delete this key and you should be good to go.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-01-20T01:12:56+00:00

    I did the dism cleanup but it showed no errors. I have also manually removed the driver but that's why I posted here. Removing the driver renders my entire computer inoperable. I had to start reformatting my computer from a fresh win10 version because it could not complete the system restore process.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-05-21T02:53:46+00:00

    Driver Store Explorer could not even find , but I could find this BrUsbSIb.sys driver file in C:\Windows\System32\DriverStore\FileRepository\mdmbr006.inf_amd64_9bcf5f1bda0dc96c directory location (file dated July-2011)

    I could not any proper way to remove this driver file, if anyone find any way to remove, please share here, so that Incompatible Drivers can removed from Window 11 and can re-initiate Memory Integrity.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-09-05T02:03:21+00:00

    Looked promising. But it didn't solve it for me. I was able to remove everything shown as Brother with the Driver Store Explorer. I also disconnected the Brother printer and removed it in Windows. Also made sure that BrUsbSib.sys was removed. But after rebooting I still can't turn on Memory Integrity because it states that BrUsbSib.sys is incompatible.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-01-20T01:28:17+00:00

    I am sorry you are having this problem. It is odd this driver would cause a problem with your computer. It is a brother serial driver.

    I would be careful about reinstalling it. Can I help you with a clean copy of Windows 10?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments