Win10 (updated with the latest version) does the same thing to my system from time to time.
I have two SSD's:
A fast Samsung NVMe drive (PCIe 4 compatible) to boot from
A slow Crucial 2TB NVMe storage drive running off an adapter plugged into the miniPCIe slot and running at SATA3 speeds (because the board only has one M.2 socket).
This seems to be an NVMe related problem as I don't recall it happening with a SATA SSD or mechanical drive?
The system itself is an AMD Ryzen 7 1700x with 16GB of memory and a fast graphics card. The motherboard is from Asus and uses a B450 (PCIe V3) chipset.
I assumed MS would eventually fix what appears to be a bug... but it seems to continue occurring? Thus worth reporting?
The bug doesn't seem to damage anything and scanning a drive from time to time shouldn't hurt it? It is a bit time consuming and inconvenient when it happens... as even with a fast drive it still takes a few minutes to finish the scan?
I'm about to upgrade the board to PCIe V4 (X570 chipset) to allow both drives to run at full speed (2x M.2 sockets running at full speed)... but I doubt that will have any impact on the problem?
I've always wondered if the system was still scanning the storage drive (a much larger drive) when this happens... but there is no disk activity... so I think it's unlikely. Also I've left the system alone for a while to see if it resets itself eventually... but it shows no signs of doing so.
The system seems to suffer no permanent damage from this problem?
The computer is being shut down correctly prior to the scan being initiated.
The computer power goes through a double conversion UPS which should mean it's very well protected from spikes and other power gremlins (the cause of many unexplained errors). The house power is also filtered further at the mains.... so the power is unusually clean.
:-)