3 ms·
Windows 10 Bug That Can Corrupt Hard Drives
- Someone 6y agoFTA: An example command that corrupts a drive is shown below cd c:\:$i30:$bitmap So, ‘cd’ can trigger writes to a file system? This also is a very scary bug as it allows a user level command to corrupt a disk.
- tinus_hn 6y agoIf you remember the con\con bug this isn’t that surprising.
- enzo1982 6y agoMore discussion in this other thread which I didn't find when submitting this. [0] It appears that the file system is not actually corrupted. The bug is just triggering a warning popup and a consistency check at the next boot. [1] [0] https://news.ycombinator.com/item?id=25787717 https://news.ycombinator.com/item?id=25787717 [1] https://news.ycombinator.com/item?id=25788171 https://news.ycombinator.com/item?id=25788171
- Someone 6y agoThanks. Especially that second link seems very much more plausible in its analysis “This is probably a simple check assertion somewhere which is seeing unexpected data passing through a call” If you write a file system every bug can destroy years of data, silently, so “better be safe then sorry” should be a poster hanging on every wall, so even a simple directory traversal, upon seeing a “this normally shouldn’t happen” event, should raise a few flags.