A security researcher has revealed details of a strange bug that could result in an NTFS hard drive becoming corrupt in Windows 10, as well as the unsupported Windows XP. What makes the bug so serious and unusual is that it can be triggered without the user having to open a file.
It seems that is being misreported.
It's been the case for quite some time that Windows automatically runs a scan whenever that message is generated; whether the message is legitimately generated or not. (Might be a Task Scheduler item that has an event defined as a trigger.) They seem to be under the assumption that the appearance of the message is validation that corruption has actually occurred. I opened a user privileged command prompt and typed "cd c:\:$i30:$bitmap". The corruption message appeared. I manually restarted the system, watched ChkDsk run, it rebooted into Windows as normal. Ran EventVwr.MSC, searched for "chkdsk" and confirmed that Windows has found no problems with the file system. Tried writing to the NTFS metadata file and of course access is denied; no such message about corruption or other was generated.
Unrelated, we've seen a number of odd occurrences with NTFS bug checks lately on 1809 systems with healthy HDDs.
Today is the first patch day of the year 2021. Microsoft released security updates and non-security updates for the company's Windows operating system and other company products such as Microsoft Office. In […]