Solved!
Go to SolutionClosed
m17 R2, BIOS installer blocked, vulnerable driver amifldrv64.sys
I wanted to install a new BIOS update from October 27th, which is classified as critical and which is supposed to fix Common Vulnerabilities and Exposures (CVE).
I noticed that on current, up-to-date Windows 22H2 systems in the default configuration, the Bios update installers from Dell/Alienware no longer work.
After starting the BIOS update installer, a pop-up message "Driver Version Fail!" and about 1000 pop-up instances of the Windows Compatibility Assistant "Windows Compatibility Assistant has detected amifldrv64.sys as a vulnerable driver and prevented it from loading..." crippled my machines. Same on two non-hardware identical m17 R2 and one XPS.
Microsoft recommended driver block rules: "With the Windows 11 2022 update, the vulnerable driver blocklist is enabled by default for all devices...".
The BIOS update installers use a driver called amifldrv64.sys, which is detected and blocked by the Windows Compatibility Assistant as an unwanted vulnerable driver.
Turning off new Windows security features (e.g. Core Isolation Memory) had no effect on my machines (m17 R2 and XPS) - amifldrv64.sys was always blocked.
With the following workaround the BIOS update worked without problems on all machines (should also work for other Dell/Alienware machine types):
- Take a USB memory stick (better rather old and with little storage capacity). I used a five years old 8GB USB 2.0 stick formatted with FAT32 (non-bootable).
- Copy your "BIOS_update_whatever_name.exe" as the only file on the stick (and leave it inserted).
- Shutdown the computer completely (restart does not work!).
- Give your computer a few seconds and restart it. During the restart press F12 repeatedly until the F12 menu appears.
- Select the BIOS Flash Update option. On the next screen, navigate through with the Tab key, select the "BIOS_update_whatever_name.exe" file with the Enter key and then select "Start flash update" again with the Enter key.
- Hands off the computer, keyboard and mouse. Wait and breathe until you see the Windows login screen again.
6460
0
Posted November 21st, 2022 03:00
Hi JamSaw
I am glad the post was useful for you.
Thanks for your positive feedback and the Kudo!Thanks also to Kuzq8 and 67shelbynut for your Kudos!
0
0
Posted February 22nd, 2026 03:03
6915
0
Posted November 10th, 2022 08:00
Had this same problem and it was maddening, I could not find any solutions anywhere. In my case it was an Alienware Aurora R12 desktop rather than laptops but it was the exactly same thing. Your solution was perfect and helped get rid of my headaches. Thank you so much!
5572
0
Posted December 6th, 2022 09:00
Just as an added comment and solution. My R12 was in the same predicament. My solution will work only if you are also dual booting a version of Windows 10 on the same hardware platform. DL and run the BIOS update from Windows 10. Works perfectly. The rogue (expired) driver amifldrv.sys is not involved.
4483
2
Posted December 14th, 2022 06:00
Can we get a driver that is not blocked by Microsoft's vulnerability features?
4398
0
Posted December 15th, 2022 07:00
I received and applied the latest BIOS to my Alienware R12 on Tuesday, Dec. 12, 2022. Rev went from 1.1.17 to 1.1.18. This BIOS release was specifically aimed at those not being able to update BIOS (driver error) after doing earlier Windows 11 Cumulatiives. I suggest you manually check the Dell Support site to see if you have an appropriate BIOS update for your system.
4401
0
Posted December 15th, 2022 07:00
I updated my Area51M to Windows 11 about three years ago. I am also getting error messages when I run the BIOS update:
1.23.0, 1.23.0
13 December 2022
Does this discussion apply to me also?
4309
0
Posted December 16th, 2022 09:00
Status Update
New BIOS updates to fix security vulnerabilities like CVE-2022-40262 and CVE-2022-33894 have been published.
The update description still says "...can be used to install from any Windows or MS DOS environment". There is no information about the incompatibility with Windows 11 22H2 provided.
Therefore, I tested the new BIOS update Alienware_m15_R2_m17_R2_1.19.0.EXE from December 13th.The installer still does not run under Windows 11 22H2.
The installer's driver is still the same and therefore remains blocked under Windows 11 22H2.
However, only the first error message of the installer "Driver Version Fail!" still appears, then the installer aborts. Nothing bad happens.Currently it remains with the workaraound via F12 and USB memory stick.
4285
0
Posted December 16th, 2022 13:00
I'm adding the Dell BIOS link mentioned in my post. It works, it's fine. My rig is an R12. It seems odd I should have a fix and others do not. Anyway, just for reference this is what I I got. Read over the fix section.
DaRkHeArTz
1 Rookie
•
1 Message
2283
1
Posted January 28th, 2023 21:00
After disabling Memory Integrity, Local Security Authority Protection & Vulnerable Driver Blocklist in Windows Security under Core Isolation tab on the left side (PC Icon), Head over to Settings>windows update>Advanced>Recovery and click advanced start-up, after reboot, click through the options to get to advanced startup, click reboot & when menu appears tap 7 for 'disable driver signing enforcement'.
Upon login you should be able to use AFUWINGUIx64.EXE for the GUI or AFUWINx64.EXE in cmd prompt without issue. Make sure to re-enable Windows Security options if you wish. Restarting enables Driver signing enforcement.