Microsoft shares Windows 10 2004 workaround for Storage Spaces issue

[silversurfer]

Microsoft has provided workarounds to help customers partially mitigate the impact of an issue affecting some devices with Parity Storage Spaces configurations after applying the May 2020 Update.
 
Storage Spaces is a Windows and Windows Server data redundancy technology that protects users' data from drive failures by storing copies on multiple drives just as RAID (redundant array of independent disks), but implemented in software.

Parity Storage Spaces can be used on systems with at least three drives and they work like RAID5 volumes.
 
On June 19, the company applied a compatibility hold on Windows 10, version 2004 and Windows Server, version 2004 devices using Parity Storage Spaces (computers with Simple Storage Spaces and Mirror Storage Spaces configurations are not affected).
 
Microsoft recommends customers to avoid "running the chkdsk command on any device affected by this issue" and says that reverting to a previous OS version will not resolve this known issue.

To mitigate the effect of this known issue impacting their Parity Storage Spaces configurations in some scenarios after applying the May 2020 Update, affected customers can use manual steps or troubleshooters.

The manual workaround allows users to still access their data by marking their Storage Spaces as read-only to continue using them.

This requires them to go through the steps detailed in the following procedure:

1. Select Start and type: powershell
   
2. Right-click or long-press on Windows PowerShell and select Run as administrator.
   
3. If prompted by a User Access Control dialog for Windows Powershell, select yes.
   
4. Within the PowerShell dialog, type the following command and press enter:
   Get-VirtualDisk | ? ResiliencySettingName -eq Parity | Get-Disk | Set-Disk -IsReadOnly $true
   
5. Your Storage Spaces should now be set to read-only, meaning you will not be able to write to them. Your device will still be usable, and any volume not seen as RAW should be readable.
   

Read more: https://www.bleepingcomputer.com/news/mi...ces-issue/