Intel Chipset Device Software Version 10.1.19222.8341 WHQL

It is possible that the passage of new chipsets modifies the hierarchy of the peripherals because as said Fernando, the drivers intel chipsets does not bring drivers but only information to recognize the new chipsets intel like yours, the Raptor lake.
It is possible that the latest pack poses a problem on the recognition of chipsets and therefore inconsistencies 

I had the same issue with a Gigabyte Z790 D DDR4 - there is definitely an issue with the NVMe driver (Standard NVM Express Controller) in these packages which causes the inaccessible boot device issue (in my case it was unrecoverable and I had to do multiple clean installs until I pinned down the problem!).

If I installed the entire Chipset driver package (via setup.exe) every time I got inaccessible boot device (Windows 11 clean install was fine, until I then installed the chipset driver package). When installing only any "missing" devices using the chipset package inf files they work fine, so I'm on a hybrid of Microsoft Out of the Box and Intel chipset drivers when not present OOB. I had to go one-by-one installing specific devices from their inf files to find out what was causing the inaccessible boot device, very annoying!

Those here saying it can't possibly be the chipset driver package are, I'm afraid, wrong, it most definitely is the chipset driver package (specifically the NVMe controller) causing the problem.

Thank you russ884 for your feedback,
is this the last pack that poses a problem? because it will impact in this case just the Raptor lake chipsets? 

 

 

Hi, I tried Version 10.1.19222.8341 WHQL and Version 10.1.19284.8351 WHQL (which is supposed to be for Raptor Lake), both showed the same problems - I've stopped installing new INF drivers now as I can't risk the consequences!

Hopefully either Microsoft or Intel fixes the problem soon. 

Intel collects bugs (i226, I225 Rev 1.x, ...) that does not reassure me