geebee

Was this ever answered? Also, would you happen to know if the fileID bug in this thread is present inside a cloud drive when used on top of a drivepool? Does cloud drive meet the NTFS spec of fileID stable until file deleted?

HD Sentinel has something similar, but it's not free. It has multiple surface tests you can perform on a drive, in addition to the standard SMART tests. The equivalent you are asking about would be the write + read test, or reinitialize disk surface (more in-depth). You can configure the data pattern (zero byte, sector count, random data, etc). It has overlap with Stablebit scanner in terms of smart monitoring, etc, but scanner has a much better layout to organize/sort and custom name drives. I've always used sentinel's surface tests to prepare new disks before putting data on them. I basically reinitialize them. https://www.hdsentinel.com/help/en/61_surfacetest.html You can configure a couple of other things on the tests.

It's not an MS problem, it's a user problem. Fast ring, or the new dev, beta and release preview channels are there for developers to iron out compatibility and bugs before it hits mainstream. You are on a developer release channel, on the same channel that Covecube is probably tracking, expecting zero-day stability, that's not going to happen. Then move Drivepool out of the developer channel windows installation.