Wednesday, 24 October 2018

Windows 10’s October 2018 Update Is Probably Delayed Until November (And Here’s Why)

Microsoft stopped offering Windows 10’s October 2018 Update on October 6, as it was deleting some people’s files. Now, another ugly data loss bug has reared its head, and it won’t be fixed until November.

M. Hamer, a Microsoft forum agent and moderator, explained this issue on October 23:

There is a known issue in the Windows 10 October Update where the consent prompt “Do you want to replace these files” is missing when copying contents from a .ZIP file.

With the Windows 10 October 2018 Update, if you copy or move files from a .ZIP file (without first “extracting” the contents) in to a new destination folder that contains duplicate filenames or is write-protected, you don’t get a“Do you want to replace these files” prompt. It will appear that the files were overwritten, when in fact the copy action for those files is not executed and files have not been overwritten.

That all sounds a little dry and boring, but it’s serious: You could lose data when working with zip files! In fact, he goes on to warn more about this more explicitly:

Important: Do not attempt to Cut and Paste items from a compressed (.zip) folder. This may result in unintentionally deleting items that may not be recoverable.

Microsoft is working on a resolution and estimates a solution will be available in early November for this issue.

After all the bad press, we can’t imagine Microsoft will want to re-release the October 2018 Update with another bug that can potentially lead to data loss. This one doesn’t seem quite as bad as automatically deleting entire folders during the upgrade process, but it’s still not great. And, if Microsoft starts rolling out the update with this bug, it’s sure to bite some people. That means Microsoft has to wait until November.

Please, if you work at Microsoft and you’re reading this: Don’t do it. Wait until November. Fix the data loss bugs first.

Read the remaining 5 paragraphs



from How-To Geek https://ift.tt/2SfDtQb

No comments:

Post a Comment