Microsoft pulls AMD driver that causes INACCESSIBLE BOOT DEVICE BSOD

[German]Users of systems with AMD Ryzen processors may run into a problem when Windows Update replaces Windows' own NVMe SSD driver with an AMD driver. Subsequently, Windows 10 can no longer boot and throws an INACCESSIBLE BOOT DEVICE blue screen. The issue has been resolved by pulling this AMD driver.

I came across this issue a couple of hours ago, after I read this arcitce from Germen news magazine heise. The magazine has outlined a blue print to build a AMD pc, but readers complaining about issues that suddenly occur after an update. The system was based an an AMD cpu with Gigabyte Aorus X570 ultra board. After installing Windows 10, the computer suddenly stopped booting after a Windows update and threw an INACCESSIBLE BOOT DEVICE blue screen.

An analysis of the process in the c't lab revealed that Windows Update suddenly replaced the standard Windows NVMe driver needed for the Gigabyte X570 board with an NVMe SSD with AMD's own SATA RAID drivers. Heise writes that Windows no longer finds the path for the system SSD after a reboot. In addition heise writes:

The heise editors could not find out why the Windows update mistakenly replaced the NVMe driver. In addition, the defective driver update also reset the BIOS in our system.

Generally, the whole thing seems to be an exotic combination, because the driver was not replaced on a Gigabyte board with a B550 chipset, on the other hand. No AMD driver was replaced via Windows Update on the Asus Pro WS X570-ACE either.

After writing my German blog post, I came across an article later written by Bleeping Computer, citing the links [1, 2, 3, 4] at reddit, where the issue is also decribed.

Fixing that bug

The heise editorial team describes a simple repair approach in this article: Let the faulty system rebooted three times to start the automatic repair function of Windows 10. In the Windows PE environment, the system can be reset to the last recovery point. Since the driver is automatically installed again immediately, don't let the system restarted. Instead, you have to go back to the previous driver version in the Device Manager – which is described in detail in the heise article. Otherwise, I had described in the blog post Windows 10: Block/manage Updates with WuMgr (2021) an approach to also reliably hide a driver update.

Driver is pulled now

Currently the problem is fixed, as the reddit.com thread here, where someone writes.

Microsoft has removed this from Windows Update, you will no longer be offered this until a fixed version is released.

Anyone affected by this problem?  Is it fixed?