Back when the driver was released on the Windows Insider program, users reported it was causing boot issues. After investigating what was causing it, a Microsoft representative stated the driver was only supposed for selected systems running Windows 10 2004 and 20H2 versions. However, it ended up landing on incompatible systems because it was using an “extremely generic hardware ID,” placing it in “the wrong place.”
Those who reported crashes after installing the update were surprised with the BSOD error code “INACCESSIBLE_BOOT_DEVICE,” which then results in a system restart loop.
