Skip to main content

Windows systems are crashing because of a bug related to special filenames

If you’re among the holdouts still sticking with Windows Vista, Windows 7 or Windows 8.1, you should be aware of a newly discovered bug that can bluescreen your system if you happen to visit an affected website. The issue is related to the way filenames are constructed and calls to mind a similar problem that affected users in the 1990s.

Windows has long since employed several special filenames that refer to things other than individual files located on disk. The nature of these special filenames dictates that they need to be accessible from any location in the file system and they can cause the operating system to hang if they are not used properly.

Recommended Videos

The special filename at the heart of this bug is $MFT, which is the name given to a particular kind of metadata file used in Microsoft’s proprietary file system, according to Ars Technica.

$MFT is not visible under normal circumstances, the majority of software cannot access it directly, and Windows will block attempts to open the file. However, if there is an attempt to open $MFT as if it were a directory, a Windows driver will enforce a lock on the file that will never be released.

All attempts to access the file system will be blocked as a result, which will cause problems for any active applications. The computer might not necessarily bluescreen, but it will not be good for much until you reboot it.

Including a dodgy filename as an image source on a web page can successfully trigger the bug on a visitor’s computer. Some browsers are unaffected, as they don’t offer the ability to access local system resources in this manner — but apparently, Internet Explorer has no such restrictions and, as such, can be targeted quite easily.

Window 95 and Windows 98 were affected by a similar issue relating to special filenames that referred to hardware devices. Windows 10 is seemingly unaffected by the new iteration of the bug.

Brad Jones
Brad is an English-born writer currently splitting his time between Edinburgh and Pennsylvania. You can find him on Twitter…
This Windows 11 bug is preventing basic system applications from running
A person using a laptop that is running Windows 11.

Another annoying issue is bothering some Windows 11 users. With this new bug, built-in system apps like the Snipping Tool, which is a common method for taking screenshots, refuse to work.

The good news? Microsoft has already confirmed it is working on a fix.

Read more
Download AMD’s new driver now to fix a major Windows 11 bug
AMD Ryzen 5000 with no lid.

A day after Windows 11 launched, AMD posted a notice about two severe bugs that could tank performance as much as 15%. The two issues are resolved now. One fix comes from AMD, while you can obtain the other through Windows Update.

The AMD update is focused on UEFI CPPC2, or in practical terms, AMD's preferred core feature. The Windows 11 bug wouldn't put the most demanding work on the fastest core, leading to decreased performance overall. You can download the chipset driver update now (revision 3.10.08.506) from AMD's website. As a reminder, this update is relevant to all AMD processors that work with Windows 11.

Read more
HiveNightmare is a nasty new Windows bug. Here’s how to protect yourself
Windows 11 on a tablet.

A new bug called ‘HiveNightmare’ reportedly lets anyone with local or remote access to your PC take it over. This is a fairly new and serious flaw in the latest versions of Windows 10, as well as in Windows 11, which is still being tested in the Windows Insiders program.

Using malware, the hacker can gain complete access to your PC without needing an administrative password. The bug originates from an alleged change in the recent versions of Windows 10 and 11 that grants unauthorized users the privilege to access the Security Account Manager (SAM). The SAM is a database that contains both usernames and passwords for local accounts on the operating system.

Read more