Windows "Storage Spaces"- Software Bug /// Incorrect "Physical Drive Warning"

Observations:​

1. Error Triggering: The issue arises when both drives are connected, but disconnecting one resolves the lockup, which indicates a problem within the storage pool rather than the drives themselves.
2. Status Swapping: The fact that the error can appear on either drive depending on their connection order strongly points to a potential issue with the metadata or headers from "Storage Spaces" rather than individual drive failure.
3. Fresh Install Not Helpful: It's interesting (though frustrating) that a fresh installation of Windows did not clear up the issue, reinforcing that it’s tied to the drive's pool configuration.

Your Questions and Suggestions:​

1. Pool Headers: You might indeed be correct about potential corruption or issues with the pool headers. Sometimes, the headers may get out of sync, especially if there are interruptions or errors during drive use.
2. Deleting and Recreating the Pool: Deleting and recreating the pool is a legitimate approach, but here's the crux—you will lose data unless you take steps to back it up first.
3. Removing Drives Safely: You’re right in noting that “Storage Spaces” doesn’t provide an easy method to remove drives without losing data. However, if you have your data backed up elsewhere, you can consider deleting the pool and reformatting the drives.
4. Alternative Solutions:
   • Using Windows PowerShell: You might try using PowerShell commands to export and then possibly re-import the pool, which might avoid the need for formatting.
   • Check for Updates/Bug Fixes: Ensure your Windows is up to date. Microsoft occasionally releases fixes for issues related to "Storage Spaces."
   • Chkdsk and Repair Utilities: Running chkdsk on both drives can sometimes correct underlying file system issues that could affect "Storage Spaces."

Image Synopsis:​

Conclusion:​