Windows 10: StorageWMI 4, New-VirtualDisk powershell failure

Getting this error on a Windows Server 2016 VM disconnected from the Internet:

:)

 

Windows 10 Storage Spaces Mirrored VirtualDisk crashed after single HDD failure

I have suffered yet another fatal Storage Spaces crash after 1 of my 8 HDDs failed. I have a mirrored VirtualDisk which is 1TB and it become detached, lost communication with the failed PhysicalDisk HDD. I have 3 other mirrored VirtualDisks which are still
working fine. I cannot connect the unhealthy VirtualDisk and cannot repair the VirtualDisk. Windows 10 SS GUI will not automatically fix this issue, and Powershell commands have not worked. The only difference between the failed VirtualDisk and those that
are still running is that the failed VirtualDisk was evidently at almost 100% full, whereas the other VirtualDisks were about 60%. The PhysicalDisk that failed is Lost Communication. Evidently, SS tried to remove data off the HDD which started at about 60%
usage and was able to move data off to about 11% usage before the drive totally died.

I have added 2 additional HDDs so I now have 13 TB used out of 30 TB pool. I don't understand how a mirrored VirtualDisk in a pool of 8 HDDs can be taken offline and crash from a single HDD failure. In theory, should there not be a second, complete copy
of every file in the mirrored VirtualDisk?

If anyone has any idea of how to work around this failed HDD and get my VirtualDisk back online, at least long enough to move the files, I would be very thankful. Again, the failed PhysicalDisk is dead, not just unhealthy. The VirtualDisk is detached, unhealthy,
but I cannot get it back online.

 

Can't connect the VirtualDisk on new server

When the old server was crashed, I connect all the disks of the StoragePool to the new server (Windows server 2019).

The StoragePool and all of VirtualDisk can be recognized and no errors found in physical disk.

However, the two of eleven VirtualDisk can't be connected while the others can be connect properly.

There was no feedback when running Repair-VirtualDisk cmdlet.

 

PowerShell instead of Commandline in Creators Update

Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

Edit: Not that it matters...I use both regularly. *Toast :toast: