Memory integrity cannot be turned on due to ftdibus.sys

Anonymous
2022-08-31T07:14:23+00:00

Windows security recommended that I take an action this morning. It highlighted that memory integrity is off. I went to settings and tried to activate memory integrity. It did not work due to an incompatible driver. The incompatibel driver is ftdibus.sys FTDI oem363.inf. 2.12.0.0.

Based on an internet search it could be a driver related to my wacom intuos tablet (which I rarely use). But I am not even sure.

I do not know what steps to take to update this driver?

I went under device manager, but it seems that all drivers are uptodate.

My windows 11 system is uptodate. I have also done the updated based on HP support assistant.

==========

Solved. See solutions on pages 2& 3 (my own posts)

Windows for home | Windows 11 | 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
Answer accepted by question author
Anonymous
2022-09-02T16:26:59+00:00

I sent an email to the FTDI support in the UK, pointing to this thread. I will let you know if I receive a reply.

I have received the reply from FTDI support. They were quick! They sent some instructions.

I followed them and it worked fine for my issue.

Was this answer helpful?

80+ people found this answer helpful.
0 comments

43 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-09-01T17:00:16+00:00

    I just did some research because I have never seen this before and realized by enabling Intel security virtualization in the Bios, the settings showed up for the memory. Mine immediately showed 3 drivers with one being a windows system file and the other two being Bluetooth drivers for a VR Headset.

    Since I am unable to delete the system file and unchecking the Bluetooth drivers in Autoruns, the same indication shows up in the Memory section. So, I am just going to disable the Virtualization in the Bios so my system will go back to normal. ;)

    Was this answer helpful?

    0 comments
  2. Sumit 44,436 Reputation points Volunteer Moderator
    2022-09-01T02:33:35+00:00

    Again due to ftdibus.sys.

    But this time the published name has changed: oem30.inf (import date: today).

    I will go to bed now. Hopefully tomorrow is more sucessful.

    How about this command:

    pnputil -d oem30.inf

    Ensure you run the same in an elevated command prompt.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-31T15:48:54+00:00

    I really wouldn't want to delete the driver. It came from Microsoft during an update last April. The driver may be important. This error just started happening today - so something has changed (though I haven't made any major changes to my system). I was hoping that someone could provide insight into what the ftdibus driver does, which might in turn help me figure out what changed that caused this security issue.

    In my case the driver date is 8/26/2014. oem263.inf

    Was this answer helpful?

    0 comments
  4. Sumit 44,436 Reputation points Volunteer Moderator
    2022-08-31T12:07:22+00:00

    Disable that in that case(uncheck).

    People have reported that deleting did not have any adverse effect.

    Was this answer helpful?

    0 comments