m17 R2, BIOS installer blocked, vulnerable driver amifldrv64.sys

Question

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.

FMax__ · Accepted Answer

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!

DaRkHeArTz · Accepted Answer

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.

JamSaw · Answer

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!

moha56 · Answer

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.

Matt_HOUTX · Answer

Can we get a driver that is not blocked by Microsoft's vulnerability features?

moha56 · Answer

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.

Pelican2231 · Answer

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?

FMax__ · Answer

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.

moha56 · Answer

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.

Alienware Aurora R12 System BIOS | Driver Details | Dell US

Lalie · Answer

( Windows 11 Version 22H2 BIOS 1.1.26 )

Hello

I want to update the BIOS following the procedure of FMax which I thank for its information.

When I copy the BIOS update file downloaded from the DELL website ( version 1.1.29 ) to my FAT32 formatted USB stick it appears the message "Are you sure you want to copy this file without its properties? The XPS8930 1.1.29 file has properties that cannot be copied to the new location. File description: Afudell Application. Company: AMI. File version: 1.0.5.0. Creation date: 05.04.2023. Size: 6.31 MB. Yes Ignore Cancel »

For the BIOS update can I use this copy without these properties?

( I checked the permissions, everything is OK )

Thank you in advance for your answers.

Shippo7 · Answer

Vulnerable Driver Blocklist can be turned off from Windows Security app

https://support.microsoft.com/en-us/windows/core-isolation-e30ed737-17d8-42f3-a2a9-87521df09b78

Then Dell BIOS updates are able to be installed on Windows 11 22H2

MxMarLo · Answer

Thank you! This fix worked on an AW Aurora R6 model.  yes, the Winx 22H2 build blocks it, if you have something earlier then it wont.

user_890d7d · Answer

@DaRkHeArTz​ This might be old but bro you are a life saver.  Thanks alot

Alienware

Was this post helpful?