There's a new Windows 10 bug that can corrupt a hard drive just if you look at an icon...! Microsoft tells me it's working on a fix, but you don't even need to open a file to trigger this. Details here: https://t.co/2G3lQIPmqf pic.twitter.com/Plp3qUErhY

— Tom Warren (@tomwarren) January 15, 2021

Microsoft to fix Windows 10 bug that can corrupt a hard drive just by looking at an icon https://t.co/bWpxI6pcsI pic.twitter.com/uOrRkiy3qj

— The Verge (@verge) January 15, 2021

#Cybersecurity #ALERT #Microsoft to fix #Windows 10 bug that can corrupt a hard drive just by looking at an icon.#CNN #CNNelection #CNNtonight#100DaysOfCode #100DaysOfHacking#100DaysofLearninghttps://t.co/v76P5Dficl

via @GoogleNews

— Simon (he) (@Simon99731093) January 15, 2021

Microsoft to fix Windows 10 bug that can corrupt a hard drive just by looking at an icon

全然話題になってないんですけど、
アイコンを見るだけでパソコンが破壊される、まるで人間にとってのNTRみたいなWindowsのバグです https://t.co/tWoC9yY4aQ

— 緋村罵倒祭 (@Muskuarede) January 15, 2021

Nice find by @jonasLyk :
cd <specialdir>

Result: NTFS corruption
Other vectors:
- Open an ISO, VHD, or VHDX
- Extract a ZIP file
- Open an HTML file without a MoTW
- Probably more... pic.twitter.com/LY18Lo3J3m

— Will Dormann (@wdormann) January 9, 2021

Why? Almost 2 years ago I reported to them NTFS filesystems that can cause windows to BSOD when they're mounted. e.g. by double-clicking a VHD or VHDX file.
That's still not fixed.https://t.co/4H8jgqmqJk

— Will Dormann (@wdormann) January 9, 2021

This problem seems to be introduced around the time of Windows 10 1803. Prior versions of Windows do not appear to be affected.
I'll give Microsoft a shot at addressing this before disclosing what the value of <specialdir> is.
Though I question how such things get prioritized...

— Will Dormann (@wdormann) January 9, 2021