قالب وردپرس درنا توس
Home / Technology / Sorry, Windows 10 has another file-delete error that Microsoft missed

Sorry, Windows 10 has another file-delete error that Microsoft missed




<div _ngcontent-c14 = "" innerhtml = "

Apparently, I have not finished killing this dead horse yet, because another file-delete error has detected in Microsoft's Windows 10 Build 1809 update. Microsoft pulled from public circulation because it was wiping entire user documents from existence. New Error focuses on Microsoft's Unzip application and appears to present itself in two different forms.

There are many situations where this can lead to data loss with varying degrees of severity. To edit a Reddit user issue:

"The problem is that the 1809 header overwritten files by extracting from an archive using File Explorer, does not result in an overwritten free dialog, nor replaces any files, it just fails. There are also some reports that it overwrites items, but made it quiet without asking. [19659003] Other users confirm the same problem and there is currently an entry on it on Windows 10 FeedbackHub .

In a pre-Windows 10 Build 1809 world, I may have gloss over this since there is not a lot of noise being generated around this particular issue. Then again, Microsoft completely lost the original, and more serious file-delete error that caused unprecedented decision to pull the update from public distribution.

Microsoft said that the original error only affected "one hundred percent of" its Windows Insiders. Microsoft also claims that it has 15 million Windows Insiders that test early builds and future Windows 10 updates. This means that it potentially affected 1,500 of them. It does not sound too damaging right? Well, we know that Windows 10 has a global installation base of at least 700 million. Had Microsoft expected even more days to pull the original Windows 10 1809 update, which apparently minuscule "one hundred percent of" adds an unacceptable number of users.

In fact, 15K is unacceptable. Any amount of lost data is unacceptable.

Insiders can now report the severity of a problem related to Windows 10 testing. Is it enough? Microsoft

And now there is another data-eating bug that affects some users who received that update. On the bright page WindowsLatest reports that the error could have been addressed in early Windows 19H1 construction (spring 2019), which means that the solution can be sent when the revised Windows 10 October update rolls out. But none of this is confirmed.

Hopefully enough people encourage this to get Microsoft's attention, to guess what? Windows Insiders also captured this . There are scattered reports from 1 to 3 months ago.

To the company's credit, it has recently revised Windows Insiders can provide feedback by giving the severity of a particular mistake. I'm not extremely sure that's enough.

Another way, Windows 10 users are at risk every time Microsoft burns out an update. The story shows this.

RELATED: Here's how Ubuntu updates your PC and why it's better than Windows

Let me get in front of an accusation that some readers may wear . Yes, I've totally won Windows in favor of Linux. So if you plan to call me forever, you would be right. And you know what? It's Microsoft's incorrect Windows updates that put me down that path. In my eyes, I just can not understand how people have set up this month after the month.

People have this assumption that Linux is stupid and complicated and requires endless troubleshooting, but when you really start to consider how many articles – and even entire sites – are dedicated to managing, preventing and generally solving The countless issues with Windows updates, your point of view can slowly change.

Currently, as always, I encourage Windows 10 users to slow down updates of something that's necessary. Exit them if you are on Windows 10 Pro, and follow this guide to streamline them if you are on Windows 10 Home. And under no circumstances use Microsoft's built-in Unzip app. Grab yourself WinRar or 7Zip.

Or just installs Ubuntu .


[n / a]

"

" Apparently, I have not finished killing this dead horse yet, because another file Sharing error has detected Microsoft's Windows 10 Build 1809 update. The same update left Microsoft from public circulation because it deletes the entire user folder from existence. The new error is central to Microsoft's Unzip application and appears to present itself in two different forms.

There are many situations where this can lead to data loss with varying degrees of severity. The user describes the problem:

"The problem is that in 1809, overwriting files by extracting from an archive using File Explorer does not result in an overhead free dialog and also does not replace any files at all; it just fails. There are also some reports that it overwrites items, but made it quiet without asking. "

Other users confirm the same problem and there is currently an entry on it on Windows 10 FeedbackHub.

In a pre-Windows 10 Build 1809 world, I can translate this because there is not much audio generated around this particular issue. Again, Microsoft completely lost the original and more serious file-delete error that caused unprecedented decision to pull the update from public distribution.

Microsoft said that the original error only hit "one hundred percent of its Windows Insiders. "Microsoft also claims that it has 15 million Windows Insiders testing early build and future Windows 10 updates. Well, we know Windows 10 has a global installation base of at least 700 million. Had Microsoft been waiting even more days to pull The oriental ginal Windows 10 1809 update, which apparently minuscule "one hundred percent" adds an unacceptable number of users.

In fact, 15K is unacceptable lt. Any amount of lost data is unacceptable.

Insiders can now report the severity of a problem related to Windows 10 testing. Is it enough? Microsoft

And now there is another data-eating bug that affects some users who received that update. On the bright side, WindowsLatest reports that the error could have been addressed in early Windows 19H1 building (spring 2019), which means that the solution can be sent when the revised update of Windows October 10 rolls out again. But none of this is confirmed.

Hopefully enough people encourage this to get Microsoft's attention, to guess what? Windows Insiders also captured this . There are scattered reports from 1 to 3 months ago.

To the company's credit, the recently revised way Windows Insiders can provide feedback by giving the severity of a particular mistake. I'm not extremely sure that's enough.

Another way, Windows 10 users are at risk every time Microsoft burns out an update. The story shows this.

RELATED: Here's how Ubuntu updates your PC and why it's better than Windows

Let me get in front of an accusation that some readers may wear. Yes, I've totally won Windows in favor of Linux. So if you plan to call me forever, you would be right. And you know what? It's Microsoft's incorrect Windows updates that put me down that path. In my eyes, I just can not understand how people have set up this month after the month.

People have this assumption that Linux is stupid and complicated and requires endless troubleshooting, but when you really start to consider how many articles – and even entire sites – are dedicated to managing, preventing and generally solving The countless issues with Windows updates, your point of view can slowly change.

Currently, as always, I encourage Windows 10 users to slow down updates of something that's necessary. Exit them if you are on Windows 10 Pro and follow this guide to streamline them if you are on Windows 10 Home. And under no circumstances use Microsoft's built-in Unzip app. Grab WinRar or 7Zip.

Or just install Ubuntu.



Source link