Nasty Windows 10 update bug is corrupting files: What to do now

It seems Microsoft’s latest Windows 10 May 2020 update (Windows 10 version 2004) is causing some files to become corrupted inside the Storage Spaces feature.

The most commonly reported concern is that some users may have trouble connecting to and accessing their Storage Spaces (via Windows Latest). Additionally, some Windows 10 laptop owners have experienced their files completely corrupted. Microsoft warns it plans to prevent any potentially impacted users from downloading the Windows 10 2004 update until it understands a strategy to this issue.

Storage Spaces is a data service intended to protect your storage from drive malfunction, which is quite ironic considering it has become facing corruption issues itself. It’s mainly intended as a way to combine multiple drives and turn them right into a digital hard drive. The service typically stores two copies of the drives, so it’s meant to be an additional safe method to make sure you never lose files.

Microsoft admitted this issue is prominent inside a status report yesterday. The company notes, “devices using Storage Spaces may have issues using or accessing their Storage Spaces after updating to Windows 10, version 2004 (the May 2020 Update) and Windows Server, version 2004. When using some configurations, partition for Storage Spaces might show as RAW in Disk Manager.” It is going onto claim that there’s “currently no workaround for this issue.”

How to proceed now

Microsoft said it’s “currently investigating the issue,” so it might not be long until Windows 10 2004 receives a fix. However, until then, the organization provides a method that should prevent any more issues from occurring on Storage Spaces.

The technique to thwart this issue are available at the bottom of Microsoft’s update article. Here are all the steps:

Select Start and type: powershell
Right-click or long-press on Windows PowerShell and select Run as administrator
If prompted by a User Access Control dialog for Windows Powershell, select yes.
Within the PowerShell dialog, type the followingcertainly be set to read-only, meaning you will not be able to write for them. Your device will still be usable, and any volume not seen as RAW should be readable.”