Windows 10: fixed the NTFS bug, but only for a few

Windows 10: fixed the NTFS bug, but only for a few

Windows 10

Microsoft fixed the bug that caused Windows 10 NTFS file system corruption. Unfortunately, the Redmond company included the fix only in build 21322 distributed in the Dev channel reserved for members of the Insider program. It is not known when it will be released to all users.

NTFS bug: fix only for a few

The bug causes corruption of the structure of the NTFS file system if the C command is typed: \: $ i30: $ bitmap. Windows 10 displays the error message "The file or directory is damaged or unreadable" and prompts the user to restart the computer to check and repair the file system with the Check Disk utility.

Microsoft reported that the disk is not actually damaged and that Check Disk fixes the problem. In reality, several tests confirm that the tool does not correct anything. Indeed in some cases, the computer no longer restarts after a second Check Disk.

The Redmond company did not distribute the fix with the cumulative update of February, probably because it does not consider it a security problem . The bug was currently fixed in build 21322, so only for Insider program members. Alternatively, users can install an unofficial patch that blocks the execution of commands containing the string: $ i30:.

File system corruption can also be caused by typing the dangerous command in the address bar of the browser. For this reason, Mozilla has added a filter starting with Firefox 85.0.1. In fact, the release notes state that the fix "prevents access to special NTFS paths that could cause file system corruption".

Source: Bleeping Computer

Microsoft fixes nasty Windows 10 bug – but you’re going to have to wait

A recently-found bug in Windows 10 has just been fixed by Microsoft, but at the moment it’s only available to people who signed up to the Windows Insider program.

The bug itself is particularly nasty, so it’s good that Microsoft hasn’t wasted any time fixing it. When accessing a certain location either using File Explorer or the command prompt, a hard drive could become corrupted – causing serious problems for users.

Microsoft had stated that, although people were seeing an error message saying that “The file of directory is corrupted and unreadable” when accessing the specific file or folder, the drive was in fact not corrupted, and running the chkdsk tool would fix the issue. 

However, BleepingComputer reports that in its tests the drive did become corrupted, and Windows 10 was unable to boot. Nasty stuff.

The bug was severe enough that while people waited for Microsoft to fix it, some companies implemented their own fixes – Mozilla, for example, blocked Firefox from accessing the folder that causes the corruption.

Now, at least, it appears that Microsoft has found a fix. With Windows 10 Insider build 21322, if you try to access the folder (C:\$i30:$bitmap if you must know – but don’t try to access this), Windows 10 will no longer say the folder is corrupted, but will instead say that the directory name is invalid.

While it’s unlikely that people will come across this bug accidentally due to the obscure folder location, the fact that it can cause serious problems – and could be exploited by malicious users – means we’re glad Microsoft has found a fix so quickly.

However, unless you’re part of the Windows Insider program – which gives you early access to upcoming Windows 10 versions to help with testing – then you may not get this fix any time soon.

It doesn’t look like it will appear in the upcoming Windows 10 21H1 update, but hopefully Microsoft will release the fix as a separate patch soon. Until then, make sure you don’t try accessing the folder.

Today's best Windows 10 deals