Driver Cannot Load On This Device – amifldrv64.sys | Fix

What Driver Cannot Load On This Device – amifldrv64.sys Means

When you see a pop-up saying that a driver cannot load on this device and the name amifldrv64.sys appears, Windows is blocking a low-level driver used by a BIOS update tool. The system thinks this driver could be risky, so it stops it before it runs.

The file amifldrv64.sys comes from American Megatrends, the company behind many PC firmware tools. Vendors bundle it inside their Windows BIOS flash utilities. During the update, that utility needs a special driver to talk to the firmware at a deep level, so it drops amifldrv64.sys into a temporary folder and tries to load it.

On recent builds of Windows 10 and Windows 11, Microsoft keeps a list of low-level drivers that attackers have abused in the past. That list is called the Microsoft vulnerable driver blocklist. amifldrv64.sys sits on that list, so Windows Defender Application Control and features such as memory integrity stop it and show a “driver cannot load on this device” warning.

If you launched an official BIOS update from your motherboard or laptop maker and saw this message, the cause is usually this blocklist rather than a broken PC. The task is to judge whether you should finish the BIOS update at all and, if yes, how to do it in a safe way.

What Is amifldrv64.sys In Plain Terms

In simple terms, amifldrv64.sys is a helper driver that gives a Windows program raw access to your firmware. That power is the whole point during a BIOS update, yet it is also the reason Microsoft treats the driver with caution. Attackers like drivers that can write directly to firmware or the Windows kernel, and this one falls into that category.

Because of that, Windows now treats amifldrv64.sys as a risky component. If the file appears on a system where you did not just run an official BIOS utility, you should treat it as suspicious and run a full malware scan with a trusted antivirus tool.

Driver Cannot Load On This Device amifldrv64.sys Error Causes

The same message can appear in a few slightly different situations. The wording on screen may vary, yet the core cause stays close to the same theme: Windows does not like this driver and blocks it before it can run.

• Microsoft Vulnerable Driver Blocklist — Newer Windows releases ship with a list of drivers that attackers have abused. amifldrv64.sys is on that list, so the system blocks it by design.
• Memory Integrity (HVCI) — When memory integrity is active under Device security > Core isolation, Windows enforces stricter rules on drivers. The amifldrv64.sys driver often fails these checks and triggers the warning.
• Old BIOS Update Packages — Some vendors still ship older BIOS flash tools that depend on this driver instead of a newer, signed alternative. Those tools run fine on older Windows builds but clash with current security features.
• Third-Party Or Repacked Tools — If the BIOS flasher came from a random download mirror, a forum link, or a YouTube description instead of the vendor website, the file can be altered or come with extra baggage that security tools do not trust.
• Corrupt Temporary Files — Damaged files under C:\Windows\Temp can cause the driver to fail signature checks, which again leads to the “driver cannot load on this device” warning.

In short, the driver cannot load message around amifldrv64.sys usually means Windows is doing its job. The challenge is to decide whether a BIOS update is worth the risk and, if so, how to handle it with as few changes to protection features as possible.

Safety Checks Before You Change Anything

Before you try to “fix” the warning, pause for a moment and do a few basic checks. Rushing straight to disabling protections can leave the system open to real threats.

• Confirm The Source — Check that the BIOS update came from your laptop or motherboard vendor’s official download page for your exact model, not from a third-party site.
• Check Whether You Truly Need The BIOS Update — Read the release notes. If the update only adds minor tweaks and your machine runs fine, you might decide to skip it rather than bypass security rules.
• Back Up Important Files — Any BIOS flash carries some risk. Copy key documents and photos to cloud storage or an external drive before you continue.
• Note The Exact Message — Take a quick screenshot or write down the full text such as “A driver can’t load on this device” along with amifldrv64.sys. This helps if you later contact the device maker.

During these checks you might already decide that the safer option is to leave the block in place and wait for your vendor to release a newer BIOS package that does not rely on amifldrv64.sys. That outcome is often the best one.

Fix The Driver Cannot Load On This Device – amifldrv64.sys Warning

If you trust the source, still want the BIOS update, and accept the added risk, you can work through the fixes below. The goal is to finish the update while keeping security features disabled for as short a time as possible.

1. Install The Newest BIOS Package — Visit the official website for your PC or motherboard, enter your exact model, and download the newest BIOS file offered for Windows 10 or Windows 11. Vendors sometimes replace old flash tools with newer ones that no longer use amifldrv64.sys.
2. Use A Bootable BIOS Flash Tool — Many vendors offer a BIOS update that runs from a bootable USB stick or directly from the firmware setup screen. This method does not rely on Windows or on the amifldrv64.sys driver, so the “driver cannot load on this device – amifldrv64.sys” problem never appears.
3. Run The BIOS Tool As Administrator — Right-click the BIOS update executable, choose Run as administrator, and try again. This does not bypass the blocklist, yet it prevents simple permission issues from getting in the way and helps you see the exact security prompt.
4. Temporarily Turn Off Memory Integrity — If you still see the message and Windows lists amifldrv64.sys as an incompatible driver under memory integrity, you can turn this feature off for the update:
   • Open Windows Security — Open Settings, go to Privacy & security, then click Windows Security and open the app.
   • Go To Core Isolation Details — Select Device security, then pick Core isolation details.
   • Toggle Memory Integrity Off — Turn the memory integrity switch off and restart the PC when asked.
   • Run The BIOS Update — After the restart, run the official BIOS tool again while the machine stays offline.
   • Turn Memory Integrity Back On — Once the update finishes and the system boots normally, go back to the same screen and enable memory integrity again.
5. Use A Different Windows PC To Create A BIOS USB — If your main machine refuses to run the tool because of the blocklist, you can download the BIOS package on another trusted PC and use that one to create a bootable USB flash drive. Then boot the target machine from that USB and run the update without loading Windows.
6. Remove Old Copies Of The Driver — Open File Explorer, browse to C:\Windows\Temp, and remove old BIOS update folders linked to past runs of the tool. Do not touch other system folders. Then download a fresh BIOS package and try again.
7. Scan For Malware If You Did Not Expect The Driver — If amifldrv64.sys appeared out of nowhere, you are not running a BIOS update, and the file lives in an odd path, run a full virus scan with an up-to-date security suite. In that case, the warning is a useful sign that something unwanted tried to gain low-level access.

During step four, you are reducing protection on purpose. Keep the PC offline, run only the official BIOS tool, then restore memory integrity and any blocklist options as soon as the flash completes. That way the driver cannot load on this device – amifldrv64.sys warning stays gone while your day-to-day protection stays close to its previous level.

Common amifldrv64.sys Scenarios And Safe Responses

The message and timing of the error give useful hints about what to do next. The table below groups the most common situations you might see.

By matching your exact symptom to one of these cases, you can usually pick a path that finishes the firmware task without leaving the machine less safe than before.

When To Accept The Block And Ask For Help

Sometimes the best fix for a driver cannot load on this device – amifldrv64.sys warning is to leave the protection in place and refuse to run the old driver at all. That choice makes sense in a few common cases.

• The BIOS Update Solves A Minor Issue — If the notes mention small tuning changes or tiny tweaks that do not affect your daily use, you can stay on the current BIOS and avoid any risk from weakening security rules.
• Your PC Already Runs Stable — For a stable gaming rig or office laptop with no crashes, skipping a blocked Windows-based flash tool is often wiser than fighting the blocklist.
• The Tool Came From A Dubious Source — If the download did not come directly from the vendor, delete it right away. A blocked low-level driver from an unknown origin is not worth the gamble.
• You Are Unsure About Security Toggles — If features such as memory integrity, Smart App Control, or driver blocklist settings feel confusing, leave them alone and avoid changes that you do not fully understand.

If you still need the BIOS update in those cases, reach out to your device maker through their official contact channel and ask whether a newer BIOS method is available for systems where the old amifldrv64.sys driver no longer runs. Many vendors already provide UEFI-level flash tools, bootable USB images, or updated Windows utilities that no longer trigger the driver cannot load on this device – amifldrv64.sys warning.

Send us your feedbackTell us what you thought about this post

⚠Please use a real email you check. If it's fake or mistyped, your message won't reach us and we can't reply — wrong addresses are rejected automatically.

Name *Email *

Your comment *

Quick check — what is …? *

Send feedback