Microsoft releases workaround for storage space parity problem in Windows 10, 2004

Some users have reported corruption partitions and damaged files in Storage Spaces in Windows 10 version 2004 after the update. The workaround for the KB4568129 issue is now available. Microsoft suggests users to make storage space as Read-only so as the data does not get affected. The Windows Team has released Windows Troubleshooters for the Parity Storage space issue.

Note: Only the storage with parity has been affected. The mirror and simple Storage Spaces are not affected by the issue.

Storage Space workaround using Troubleshooters

It you have updated your Windows 10, version 2004 and affected by this issue, the company has made available some automated troubleshooters to address the issue and mitigate the problem. Use the below steps to check if the automated troubleshooter has run and applied the mitigation:

  • Open Windows 10 settings
  • Click on Troubleshoot
  • In the Troubleshoot section, click on the View History link
  • Here you will see a critical troubleshooter or recommended troubleshooter with the title and description as describe below, in case the Troubleshooter has attempted to run.

Hardware and devices troubleshooter: Automatically change the system settings to fix a problem on your device – This troubleshooter will prevent issues with the data on your Storage Spaces. After the troubleshooter has run, you will not be able to write to your Storage Spaces.

Storage Space Troubleshooter: Data corruption was detected on your parity storage space. This troubleshooter takes actions to prevent further corruption. It also restores write access if the space was previously marked read-only – This troubleshooter will mitigate the issue for some users and will restore read and write access to parity storage spaces. You need to manually recover the files that already had an issue.

Manual steps for the Workaround

  • When the troubleshooter has not run yet, you should mark them as read-only. Here are the required steps for doing this:
  • Click on Start option and type PowerShell
  • Right click on the top result and select the Run as Administrator option
  • Type Get-VirtualDisk | ? ResiliencySettingName -eq Parity | Get-Disk | Set-Disk -IsReadOnly $true command and click enter

The above steps are the equivalent to the troubleshooter above titled “Hardware and devices troubleshooter.” There is currently no manual equivalent to the troubleshooter titled “Storage space troubleshooter.”

How to recover the files

If you can access to parity storage spaces and it does not appear as RAW in DISk Manager, you can attempt to recover the files using Windows Files Recovery or WinFR. After downloading it from Microsoft Store and open it, follow this instruction:

Run segment mode (/r) with the undeleted files flag (/u) to recover files from your NTFS volumes. By default, this will recover all possible files.  You can add filter flags if you are only interested in certain file formats (such as/n *.docx) and to reduce system file recovery.  Example command to recover all docx files present in the C: drive to the D:\SpacesRecovery folder: winfr.exe C: D:\SpacesRecovery /r /u /n*.docx

Then, go to the D;\SpacesRecovery to see the recovered files

In case, if you have a ReFS volume that shows as RAW in Disk Manager, you need to use refsutil salvage command to recover the data. Two options for salvage commands are described below:

Quick Recovery

  • Open Start and search for Command Prompt
  • Right click on top result and select Run as administrator
  • Type this command “refsutil salvage -QA SOURCE-VOLUME WORKING-DIRECTOR DESTINATION-FOLDER” and then press enter

Full Recovery

This option more data than the previous option. Here are the steps to perform it:

  • Open Start and search for Command Prompt
  • Right click on top result and select Run as administrator
  • Type this command :refsutil salvage -FA SOURCE-VOLUME WORKING-DIRECTOR DESTINATION-FOLDER For example: refsutil salvage -FA E: F:\SalvagedFiles” and then press enter

After this, the files will be recovered in your folder specified.

The company says, they are currently investigating this issue and will provide an update when more information is available