Inaccessible boot device after latest insider update this morning (build 21364)

You shouldn't be reoffered this driver now.

-Eddie

I can confirm that I am no longer offered this driver.

However, I cannot see how it took this long to remove. It was an issue for Insiders first, but it STILL was pushed out to the public branch? Isn't the entire point of the Insider program for people to test stuff and you guys fix it before it goes public? This is an extremely serious issue, some people may even resort to a full windows re-install because of this update. I (thankfully) had a restore point, but it was from a week ago, and a lot of my settings and stuff was all borked because of the restore. I'm just happy my computer works, but this is not the kind of stuff you'd expect from a multi-trillion dollar company that is KNOWN for shoving windows updates down our throats. This is exactly the kind of behavior that validates those who refuse to install updates because of various issues. This legit BSODed computers. Microsoft, try to NOT be the company you are notorious for being.

Is Microsoft going to replace my broken hardware? That's exactly what you guys have done. Thanks guys, PC has been running like a dream ever since this one update. Can't even get power to fix anything now. Top notch stuff.

Same issue here, but now mitigated.

System Specs:

MB: Gigabyte AORUS X570 Master

CPU: AMD 5950X (PBO Enabled, CO Tuned To Prime Stable)

RAM: G.Skill 4x16GB DDR4-4000 16-18-18-39 1.4V (Running @ DDR4-3733 15-15-15-36 1.35V, 1866 FCLK, 1.15 VSOC)

GPU: EVGA RTX 3090 FTW3 ULTRA

Boot Drive: WD_BLACK SN850 1TB NVMe M.2

Edition: Windows 10 Pro

Version: 20H2

OS Build: 1904.964

Feature Set: 120.2212.2020.0

Steps:

Installed AMD SCSIAdapter 9.3.0221 driver update. 

BSOD inaccessible boot device on reboot.

Auto-reboot after BSOD caused the MB to freak out, fall over several times, clear CMOS (good thing I keep my tunings written down), and auto boot into BIOS recovery mode (which I didn't even know was a thing). 

Left BIOS settings on defaults.

Used Windows install USB to apply restore point.

Attempted reinstall of driver update.

Replicated behavior. BSOD, MB failures, Auto cleared CMOS, rebooted to BIOS recovery mode.

Used Windows install USB to run startup repair.

Boot to Windows successful. AMD SCSIAdapter 9.3.0221 shows as successfully installed. 

Re-applied BIOS settings and tunings and rebooted several times without incident. 

Currently re-running Prime95 to confirm stability.

Comments:

I'm not sure what startup repair did as there are no logs of it in event viewer. However, this seemed to come scary close to actually damaging my hardware. Things have to get pretty screwy for the MB to do a CMOS clear all on its own, let alone that BIOS recovery mode.

This was gross negligence on Microsoft's part. The issues with this update were well documented in the dev version and should never have been pushed to the public.

I totally understand the risk here when using the insider build. I am a software engineer myself for 20 years. I know how it is. I have never used Feedback Hub before because I cannot boot into the system when it's broken, I am not sure if it needs to collect any data from the system while it's in the broken state. 

You are correct, the more data they can get, better for a resolve. Not much one can do if you cannot get into system when broken. As long as they are aware, it helps. This would be ideal for a dual-boot scenario where one could retrieve the logs from the faulty drive or partition. Not a fan of dual-boot myself.

Regards,

Eddie, is there a bug tracking for the Advanced Micro Devices, Inc. - SCSIAdapter - 9.3.0.221 driver? I think maybe it's using SCSI translation for NVME and SATA. That's why I am affected. I cannot update now with that issue. Thank you for your help.

The issue is being investigated. I can't say for sure if there is an issue with that particular 3rd party driver, but is just something I noticed in common with the reports. One possible thing to try (after making sure you have a good backup/restore point). would be to roll back to a previous version of that driver and seeing if you can install the latest Windows build (21370). Completely up to you and your comfort level.

-Eddie