Critical NTFS bug in Windows 10 can corrupt HDD/SSD filesystem
Click here to post a comment for Critical NTFS bug in Windows 10 can corrupt HDD/SSD filesystem on our message forum
jststojc
Sorry im a bit confused. Does it corrupt the filesystem or actually the drive? Because the title suggests it can actually make hardware faults, whilst the text would rather suggest it only makes the filesystem corrupt.
Hilbert Hagedoorn
Administrator
I'll clear that text up a little, the file system e.g. volume will get corrupted. Likely it can be resolved after checking/fixing, and after a format, the HDD/SSD should be alive again.
cool_recep
*NTFS
Kaarme
Luckily that's something few people could do by accident.
anticupidon
So, the internet will be flooded with messages:
"Wanna speed your Windows 10 with this small command?" or " Microsoft hates this trick, use it to make your Windows 10 more private, faster, etc"
And gullible people will do it. Guess that means more work for tech repair people.
Microsoft is really a good company, gives us techies a lot of work. 😕
Thanks, Microsoft!
/heavy sarcasm ended
TheDeeGee
caldas
Time to buy a NAS
mbk1969
How could I live without that command for all those years since 90s?...
Airbud
Mufflore
Ouch!
I wonder if this traverses back to previous OS versions, they specifically mention 10 only.
Mufflore
Ghosty
Astyanax
David3k
HOLY CRAP, this actually explains a big issue I've been having for a while on my program on any of my computers; the program indexes only file and folder STATES on various marked locations over time at two minute intervals on NTFS filesystems.
A few weeks ago I added NTFS attributes on the list of metadata it probes for and records that information. It caused no immediate problems so I had a hard time tracking this down when I started getting issues week ago, since I've made a few more versions since then with other features and bugfixes.
I just updated the program to now exclude the $i30 attribute (NTFS bitmaps are already excluded) and hopefully I won't be seeing random NTFS errors crop up anymore.
Thanks for picking up on this, Hilbert, you've just solved a massive ongoing headache for me.
Twenty years, and you're still helping me out. : )
PS: I think I'm just going to exclude most NTFS attribute flags by default and only query the compressed and encrypted flags
alanm
"The vulnerability was discovered around the Windows 10 April 2018 update and has not been resolved to this day. according to a spokesperson for Microsoft, a solution is being worked on as soon as possible."
mbk1969
schmidtbag
https://i.pinimg.com/236x/52/9b/d0/529bd0d900c6e501602f6931ef32e39c--family-guy-told-you.jpg
How do you even find something like this? It seems so oddly specific.
Ghosty
mbk1969
Reddoguk
That is funny, "The vulnerability was discovered around the Windows 10 April 2018 update and has not been resolved to this day".
-a solution is being worked on as soon as possible. like really soon or another 3 years?