AutoRuns V14.3 Unable to disable or delete imcompatible drivers

Dionne Hersh 0 Reputation points
2026-08-24T20:24:08.44+00:00

I am using the AutoRuns V14.3 program to identify and delete or disable incompatible drivers so that I can turn on Memory Integrity. Some of the highlighted drivers cannot be deleted or disabled.

Screenshot attached. Screenshot 2026-08-24 131954.jpg

Sysinternals
Sysinternals

Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.

0 comments No comments

2 answers

Sort by: Newest
  1. Alan S. Jones 1 Reputation point
    2026-08-25T20:03:31.6333333+00:00

    I am having similar issues where I can't delete some items with AutoRuns. I have actually seen this for a while though...

    I get annoyed by he AI responses like above.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. AI answer

    2026-08-24T20:24:23.7733333+00:00

    If Autoruns cannot disable or delete some highlighted drivers, the most likely reason is that the driver is still present in the Windows driver/component store or is otherwise protected from removal through Autoruns alone.

    A practical path is:

    1. Try the supported fix first: update the driver
      • Check Windows Update for a newer driver.
      • If nothing is offered, check the device or driver manufacturer for an updated version.
      • This is the preferred fix for Memory Integrity compatibility issues.
    2. If no updated driver is available, turn off Memory Integrity temporarily
      • Open Windows Security.
      • Go to Device security > Core isolation details.
      • Turn Memory integrity Off.
      • Restart the PC.
      • Warning: on a Secured-core PC, this takes the device out of a Secured-core state.
    3. Check which drivers are actually being blocked
      • Open Event Viewer.
      • Go to: Applications and Service Logs\Microsoft\Windows\CodeIntegrity\Operational
      • Memory integrity compatibility events generally use Event ID 3087.
      • This helps confirm the exact driver name that is preventing enablement.
    4. Use Autoruns to inspect all driver entries
      • Autoruns includes a Driver tab, and autorunsc can also enumerate autorun items.
      • If a driver entry still cannot be removed in Autoruns, that aligns with cases where the file remains elsewhere in Windows rather than as a simple startup entry.
    5. If the driver remains after uninstall attempts, remove it from the driver store
      • Community guidance in similar cases uses:
        • dism /online /get-drivers /format:table to identify third-party drivers
        • pnputil /delete-driver oemXX.inf /uninstall /force to remove the published driver package
      • This is more direct than Autoruns for driver packages.
      • Warning: removing a driver can stop the related hardware or software from working until the correct driver is reinstalled.
    6. If the driver is still needed, leave it installed and keep Memory Integrity off until the vendor provides a compatible version
      • Microsoft guidance for driver-blocked Memory Integrity issues is to update the driver first.
      • If no compatible driver exists, disabling Memory Integrity is the documented workaround.

    Also note:

    • Some incompatible drivers may not be easy to find in normal file locations because they can remain in the component or driver store.
    • The driver name and company name shown in the Memory Integrity notification are the most reliable identifiers to use when matching the blocked driver.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.