A Windows Security notification that a driver cannot load can describe a compatibility boundary enforced by Memory Integrity. The next step is to identify the blocked driver and its purpose, not immediately lower protection to make the notification disappear.

Record the driver name and company shown in the notification. Microsoft identifies those as the reliable information available about the driver. Preserve the wording accurately, including any filename, while keeping unrelated personal information out of a shared screenshot.

Connect the driver to the function you need

List what changed recently: a peripheral connection, application installation or driver update. Identify the function that now fails, if any. A notification at startup and a later unrelated app error should not be joined into one diagnosis without evidence.

Microsoft recommends looking for an updated compatible driver through Windows Update or the driver manufacturer. Use the exact PC or peripheral model and Windows release when selecting a supported package. Avoid driver-download sites that merely repeat the filename.

Ask the supplier which product owns the driver if that remains unclear. This is especially useful when the visible company name differs from the branding on the device or application. Do not delete a similarly named file from a system directory as an identification experiment.

Keep the protection decision visible

On Windows 11, inspect Windows Security, Device security, Core isolation details to read the Memory integrity state. Record it before an agreed driver change so later testing can distinguish improved compatibility from protection being switched off.

Microsoft warns that disabling Memory Integrity takes a Secured-core PC out of that security state. Ignoring the blocked driver can also leave its supported functionality unavailable. Those are different consequences that deserve an explicit decision by the computer’s owner or administrator.

If no compatible update exists, ask the supplier about its support plan and consider an alternative supported workflow. Do not treat an indefinite protection downgrade as a routine step that needs no record.

After a supported update, complete any required restart, revisit the security state and test the affected function. A useful result preserves both the intended capability and an understood protection configuration, with unresolved limitations documented.

Sources: Microsoft driver load block.