Didn't work on my system at all.sdjj348&^#`%${%&`+'${`%&NO CARRIER

Funny!

One would think that a patch would have been released straightaway. Evidently fixing this security flaw is less than trivial. Hope they don't break NTFS in some weird way when they do patch it.

Ran this in VM to see, I didn't create the shortcut, just pasted the text into the command line and hit enter - CMD complained the command was invalid, but immediately the file system showed corrupt, need to reboot. On reboot, it tried to fix it, failed, rebooted, tried again, rebooted...

restored to the last checkpoint and did it again, the VM was back in windows in 2-3 minutes after reboot - so it's not always fatal to the system, but it can be.

I tried it inside a Hyper-V VM which as the articles suggest, it resulted in a NTFS error in my Event Log. I rebooted the VM, it did a CHKDSK as it should, tried to reboot, it BSODed, rebooted again, ran another check of the file system, and then the system came back up as normal.

A little scary if you ask me.

What I'm missing is any indication that the indicated hard drive corruption has actually occurred outside a lab, or why someone would have used this command or had a file with it on their computer. Now that it is public, it seems actually more dangerous for the moment, since malware practitioners are probably trying to exploit it. Look forward to a fix soon.

"The use of this technique relies on social engineering"

Or malice.

I am pretty sure malice is simply assumed if someone is using social engineering to destroy someone's data...