![]() ![]() But if you have a virtual machine, you can find the command in Bleeping Computer's story. We're not going to tell you what the command is because we don't want you trying this at home. ![]() "I'll leave it to the people with the source code," i.e., Microsoft. "I have no idea why it corrupts stuff and it would be a lot of work to find out," told Bleeping Computer. The only reason this flaw may not have been discovered before is because the active command might not normally be paired with the specified implementation. None of the elements of the command are anything special or uncommon, and it'd be familiar to many Windows users who often get into the command-line interface. It's not clear why this specific command borks hard drives. The flaw affects all builds of Windows 10 from version 1803 onward, told Bleeping Computer, which Dormann confirmed. You could also be safe if you're still running Windows 10 version 1709, released in October 2017, or earlier. ![]() Doing so would be a huge pain in the neck, as you'd have to first back up and then essentially rebuild your system. To avoid attacks using this flaw, you could change your PC's hard drives to the FAT32 file format, the same file format used by USB flash drives, SD cards and other kinds of removable storage. You'd likely need third-party software to fix that. ![]() But in other cases the disk's master file table (MFT), an index of all the files on a drive, would be corrupted along with the files. The virtual machine in the video was unable to restore the drive, even after several reboots.īleeping Computer said that in some cases the chkdsk (Check Disk) utility was able to repair the drive. Bleeping Computer (opens in new tab) replicated the flaw and even posted a video of it rendering the C, or main, drive unreadable on a virtual PC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |