Windows 10 2004: Microsoft published a Workaround for Parity Storage Spaces issue

[German]Windows 10 May 2020 Update (Version 2004) has some issues with parity storage spaces that prevents an upgrade. Now Microsoft has confirmed this issues and published a workaround.


In my recent blog post Windows 10 2004: Storage Spaces issues I mentioned a number of issues within Windows Storage Spaces.

Issues with Parity Storage Spaces

The support article KB4568129 (Issue with some Parity Storage Spaces after updating to Windows 10, version 2004 and Windows Server, version 2004) describes an issue, that may occur during upgrading to Windows 10, version 2004.

When users try to update to Windows 10, version 2004, the update install  may be interrupted during  compatibility check and you may receive the message: "This PC cannot be updated to Windows 10. Your PC is not yet supported by this version of Windows 10. No action is required. Windows Update will automatically offer this version of Windows 10 when the problem is resolved.

screenshot of safeguard hold dialog
(Source: Microsoft)

Devices that use parity storage spaces may experience problems using or accessing their storage spaces after you upgrade to Windows 10 version 2004 (the May 2020 update) and Windows Server version 2004.  When some configurations are used, partitions for parity storage spaces in Disk Manager may appear as RAW. Microsoft has therefore set an update lockout on Windows 10 version 2004.


Microsoft  suggests a workaround

Microsoft has now published the support article Workaround and recovery steps for issue with some Parity Storage Spaces after updating to Windows 10, version 2004 and Windows Server, version 2004  on the issue described in support article KB4568129. This applies to Windows 10 version 2004, Windows Server version 2004, and all editions of OneDriveOneDrive for Business. Simple storage spaces and mirror storage spaces are not affected by this issue.

The first advice from Microsoft is to run the "Hardware and Device Troubleshooting" or "Mirror Storage Spaces Troubleshooting" troubleshooting. The next suggestion is to use a PowerShell command to set a VirtualDisk to read only. To do this, open Windows PowerShell by choosing Run as administrator and typing the following command:

VirtualDisk | ? ResiliencySettingName -eq Parity | Get-Disk | Set-Disk -IsReadOnly $true

Storage spaces should now be set to read-only, i.e. you can no longer write to them.  Your device will still be usable, and any volume that is not considered RAW should be readable. In the KB article, Microsoft gives further advice if a Parity Storage Spaces drive is not seen as RAW in Disk Management.

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Windows and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *