fbpx

Windows 10 version 2004 slams right into a Storage Areas brick wall

It’s prematurily . for the villagers to haul out their rusty pitchforks and oft-hoisted torches, nonetheless it appears like another data-consuming is had by another Windows version upgrade bug. The bug infects Storage space Spaces, Microsoft’s method of implementing RAID-like information redundancy through the use of standard hard disks.

Yesterday, Microsoft posted Information Base article 4568129, which says partly:

Devices using Storage space Spaces could have issues using or even accessing their Storage Areas after updating to Home windows 10, version 2004 (the Might 2020 Update) and Home windows Server, edition 2004.  When working with some configurations, partition for Storage space Spaces might present asNatural in Disk Manager.

Within a couple of hours, Microsoft clamped down on distribution of the Win10 version 2004 upgrade for some affected PCs, showing the information:

This PC can’t upgrade to Windows 10. YOUR PERSONAL COMPUTER isn’t supported yet with this version of Home windows 10. No activity is needed. Home windows Update will offer you this version of home windows 10 once the concern provides been resolved automatically.

the block appears about Win10 1809 Presumably, 1903 and 1909 machines running Storage Spaces.

Attribute it in order to the “artificial” section of Microsoft’s vaunted rollout AI.

The scary part will come in the announcement later, which says:

Important

We usually do not recommend jogging the chkdsk order on any device suffering from this issue.

Of course, any experienced Windows consumer who encounters a faltering disk will wind up chkdsk suddenly.exe. Checkdisk ‘s been around since the full times of DOS. And we&rsquo now;re being told never to use it. There is no description why, it’s not recommended just.

understand what little offers appeared online To, you need to recognize that Storage Spaces, an attribute introduced in Win7, works with four degrees of protection. When you create a SPACE FOR STORAGE, you tell Home windows what degree of backup security (“resiliency”) you need. A Parity Storage space Space setup, which shields you from full destruction of an individual drive, requires at the very least three hard disks. With a Parity set up, among your drives can grind to dirt, and you’ll have full, uninterrupted accessibility to all your data.

The information I’ve seen (thx, skippy on Reddit) indicate corruption in Home windows PCs with the Parity version of Storage Spaces. JohnHagan, publishing on a different Reddit thread, describes it in this manner:

I experienced a Storage Areas Parity storage space comprising 4 WD Crimson 6TB NAS hard disks, formatted as NTFS, on the Windows 10 Professional workstation, for quite some time. After upgrading to Home windows 10 Version 2004, each day or two within, The contents were noticed by me of some files were corrupt. A CHKDSK led to finding a large number of problems, such as for example “Attribute list access with type code 80 in file 5E711 is corrupt” and “Document record segment 67C08 can be an orphan”. When CHKDSK finished, the file program was consistent again, but hundreds of documents had incorrect articles, despite their additional attributes getting correct (quality and change dates).

I restored the corrupt data files manually from backup, for another week and continued on. Then, a Cumulative Upgrade for Edition 2004 was set up and the workstation had been rebooted. Soon after the reboot almost, I once again noticed corrupt files. This right period, CHKDSK (operate in read-only mode) detected a huge selection of problems. I haven’t attempted to correct it with CHKDSK, as I’m afraid I’ll corrupt it further.

Based upon the few articles I’ve noticed, the bug only turns up on machines working the Parity variant associated with Storage Spaces.

In my knowledge, Storage Areas isn’t typical – and Parity Storage space Spaces aren’t typical from all. But that’s very little solace to someone who’s trusting Microsoft to aid its feature.

Microsoft has had a variety of problems with difficult SSD and drive administration in Win10 edition 2004 – Mayank Parmar on Windows Most recent lists issues with creating Storage Spaces. He furthermore shows that the Travel Optimizer defrag device doesn’t keep an eye on dates and therefore prompts frequently one to run it too. Günter Born, quoting Karl Wester-Ebbinghaus, reports that old issues with freeing data haunt Storage Spaces still; and that Microsoft provides known around these bugs for a long period.

I haven’t seen any reviews of Win10 2004 upgraders permanently losing information yet. But given the released warning about making use of chkdsk, it appears like another data-feeding on is had by us upgrade bug about our hands.

The last time a fresh version of Win10 started chewing up information inexplicably, with version 1809, Microsoft pushed the upgrade for four times before yanking it. Version 1809 went in to the shop for four a few months, with the “oops, final final” edition shipping in March 2019.

Given the most likely severity of the nagging issue, Microsoft should right now yank version 2004, and wish that more folks don’t lose their information. It isn’t enough to cover up behind an upgrade prevent.

Microsoft shouldn’t have shipped Earn10 edition 2004. Delaying the deliver date may be the first product in my own list of Five steps Microsoft should take AT THIS TIME to greatly help us through the pandemic, published 8 weeks ago. You can find no feature upgrades worth the term – edition 2004 re-arranges the chairs on the deck primarily. In the “tick-tock” brand new Win10 scheme of version upgrades every half a year, that one doesn’t tick. It thuds.

After fives months of testing the ultimate version of Win10 version 2004, we understand this.

Have the beef with 2004? Sign up for us on AskWoody.com.

%d bloggers like this: