[DRIVERS] Intel Chipset/MEI/VMD (6xx/7xx/8xx)

[MoKiChU]

Hi everyone,

- Intel Chipset Drivers :

Package : 10.1.19913.8607 WHQL [09/07/2024]

Download : Link

Install/Update Process :

Launch "CHIPSET_Intel_vxx.x.xxxxx.xxxx.exe"

- Intel MEI Drivers (Drivers Only) :

Drivers : 2433.6.3.0 WHQL [15/08/2024]

DAL SoftwareComponent Driver : 1.46.2024.221 WHQL [31/03/2024]
ICLS SoftwareComponent Driver : 1.74.210.0 WHQL [01/08/2024]
WMI SoftwareComponent Driver : 2428.6.4.0 WHQL [10/07/2024]

Download : Link

Install/Update Process :

Launch "Install.cmd" by right-click Run as admin > Automatic restart when install is done

- Intel VMD Drivers (Drivers Only) :

Drivers : 20.1.0.1015 WHQL [22/07/2024]
Download : Link

Install/Update Process :

- Press Windows key + X > Device Manager > Right-click on your Intel VMD device > Update driver > Browse my computer for driver software
- Browse... > Select the extracted drivers folder (VMD_Intel_v...) > Next

OS requirements : Windows 10 64 bit or more recent.
Hardware requirements : Motherboards with Intel 6xx/7xx/8xx series chipsets.

TIPS :

If you want to manage the drivers (remove old/unused drivers for example) that you have in your Windows DriverStore
Use Driver Store Explorer (Right click on "Rapr.exe" > Run as administrator).

If you want better interrupts delivery latency
Enable MSI (Message Signaled-based Interrupts) mode on all your supported devices (see the column "supported modes") with
MSI Mode Utility (Right click on "MSI_Mode_Utility_v3.exe" > Run as administrator).

[skorell]

MaKo82 wrote:
Where can I get the previous Chipset drivers? I'm putting together a new build today and plan on installing the MEI drivers before the BIOS. Will that be enough until the updated chipset drivers are released?

Edit- I've downloaded v10.1.19222.8341 I assume this version is ok?

Yes,

v10.1.19222.8341 is the previous version and works fine.

[Brutus7284]

Had also installed the Intel Chipset Driver V10.1.19284.8351 For Windows 10/11 64-bit from Asus, could no longer get into Windows. Had to do a system restore

[Juice2643]

SAME, Tried to update my z690 hero 13900k to Intel Chipset Driver V10.1.19284.8351, it gave boot device unavailable. Only way for me to recover was fresh install Windows 11.

How is something like this even posted on the site?

[nbelancic_]

Installed the new chipset driver for my Z790-E and now windows 11 won't boot anymore.

DON'T INSTALL !!!! Error was bluescreen with inaccessible boot device

Had to do a system restore to get back into windows 11!!!!

[Simk1n]

Juice2643 wrote:
SAME, Tried to update my z690 hero 13900k to Intel Chipset Driver V10.1.19284.8351, it gave boot device unavailable. Only way for me to recover was fresh install Windows 11.

How is something like this even posted on the site?

Does it not say Alder Lake for that version in the first post?

READ first.

[skorell]

Simk1n wrote:
Does it not say Alder Lake for that version in the first post?

READ first.

I think he is referring to the ASUS support website. There is no mention of this issue in the download section for this new version.

https://rog.asus.com/motherboards/rog-maximus/rog-maximus-z790-hero-model/helpdesk_download/

[Silent_Scone]

Juice2643 wrote:
SAME, Tried to update my z690 hero 13900k to Intel Chipset Driver V10.1.19284.8351, it gave boot device unavailable. Only way for me to recover was fresh install Windows 11.

How is something like this even posted on the site?

There is a validation process in place, however as ASUS does not write the Intel Chipset drivers, certain conditions can sometimes slip through. This is why users often will come to threads such as this, as newer Intel revisions take a while longer to hit the ASUS support pages.

They're aware there's an issue and are working on a solution.

[RogueSix]

I was affected by this as well and downloaded the chipset drivers from the support site of my ASUS ROG STRIX Z790-E GAMING WIFI mainboard. It was a nightmare to fix in my case as Win 11 could for some reason not identify any system restore points even though system restore is enabled on my boot drive.

The problem was exacerbated by the BitLocker encryption of my boot SSD (Samsung SSD 990 Pro). I could (almost) enter the 48-digit recovery key by heart after all of the troubleshooting and attempts to fix the "inaccessible boot device" issue.

I tried just about all of the tips and tricks you can find online when googling "inaccessible boot device" including a couple of rescue/recovery tools but nothing got rid of the error.

I was about to throw in the towel and clean install when I found one article which described how to manually uninstall *.inf driver packages from the command prompt. That was the ticket to success! I manually uninstalled all of the Intel chipset driver packages (easy to identify by the 07/18/1968 date) and was able to boot into my system as if nothing had ever happened in the first place.

The only thing I had to do to get rid of a couple yellow exclamation marks in device manager was to reinstall the old chipset version (with the "8341" at the end which is the safe to use version).
Phew. It took me a good five-ish hours to get my Windows 11 back because of all the reboots, recovery key entries (I also googled how to manually get rid of BL encryption via command prompt and decrypted my drive to save a little time at one point), creating bootable USB rescue/recovery media with various tools and lots and lots of command prompt fiddling...

I'm glad to see that ASUS has pulled the faulty chipset drivers in the meantime but if anyone is affected by this because they downloaded the "8351" broken version: If rolling back via system restore does not work then do not waste your time with the many solutions that are suggested for an "inaccessible boot device" on the web. Go straight to the method where you enter commands to uninstall the chipset driver packages (called oemXX.inf) from the command prompt.
The faulty chipset drivers do not ruin your boot setup or something on your drive as I first wrongly assumed. Everything is fine on that end. The blocker are the actual chipset files which you need to uninstall manually to get back into Windows.

[dryden_ben]

quick note for all the other noobs out there.

you won't see "run as administrator" until you extract the zip file.

[bobaz]

This worked for me, thanks MrAgapiGC