قالب وردپرس درنا توس
Home / Technology / Windows 10 1809 may have another error while deleting the file

Windows 10 1809 may have another error while deleting the file



This site can earn affiliate commissions through the links on this page. Terms of Use

Earlier this month, Microsoft made the October Update for Windows 10 (Build 1809) after discovering that a small number of users Updated to a fatal error and deleted the contents of the folder Pictures, Videos and sometimes Documents. How Microsoft describes this error:

Before reissuing the October 2018 update, our technical research has revealed that a very small number of users lost files during the October 2018 update. This occurred when the Known Folder Redirection (KFR) feature was previously enabled, but files remain in the original "old" folder and have not been moved to the new, redirected location. KFR is the process of redirecting the familiar Windows folders including desktop, documents, images, screenshots, videos, camera rolls, etc. from the default folder c: users username to a new folder.

In other words, if you've created a new folder on a new drive to save space, and your device does not have the Documents folder in the default C: location, but in the D: location The operating system may delete all data in your "old" folder while keeping the new one intact. This is a big problem if you did not move all of your data from the old document folder to the new one and instead treated the old directory as an archive while all new data was stored in a different location.

The new Build 1809, which has not been released to the public yet, solves this problem. Unfortunately, it may have introduced new ones. Ghacks has resolved a number of complaints that may indicate a problem with Microsoft's Unzip application, including reports that it automatically replaces all files in a directory with the same name as the unzipped files without asking them to overwrite them should be. and reports that the unzip may fail because files with the same name already exist in the directory.

There are reports of both types of behavior – files without prompting to overwrite and implicitly popping file names without updating – it is difficult to know if these are two different versions of the same error, two different errors, or something completely different , It just seems to affect the unzip capability introduced in File Explorer, not the functionality of third-party applications – if you're using a utility like WinZip, WinRAR or 7zip, you should not have any problems.

 FileExplorer-Unzip

We had doubts about Microsoft's update method on its operating system, since it fired a lot of its QA team and got around to the idea that programmers test their own work and the Rest would be moved to Windows Insider reorganized. But there is evidence that Windows insiders knew and reported this issue, and Microsoft did not track it, obviously not recognizing the severity of the problem. The key problem here is that Windows insider builds are explicitly not as daily Recommended drivers, which means that most test persons do not test in a real production environment. They test on VMs or on secondary systems. I certainly would not install a Windows Insider build on my own daily machine.


Source link