A company outside Microsoft launches before it an open source patch for a bug that allows you to damage your hard drive in Windows 10



On January 9, the existence of a hitherto unknown vulnerability in Windows 10 was disseminated on the networks, and so strange that can be exploited not just by entering a short command, but even even if the user is limited to viewing the folder where the shortcut is located the same.



Here is an example of what happens when we enter the command in question:




Thus, each time we try to access that path, the system mistakenly detects the directory as damaged or corrupted, forcing the system to reboot to "repair drive errors." Normally, after that, the Windows CHKDSK utility fixes the problem ... although some equipment has been rendered useless after that.




Before the delay in solving the problem by Microsoft (and the lack of an established date for it), an external company has decided to develop and distribute a patch for the NTFS driver that solves this annoying bug in Windows 10.







How to use chkdsk in Windows to fix errors on your disk





OSR is a software development company specialized in components and drivers for Windows. Its programmers, motivated precisely by having lost one of their Windows 10 PCs while investigating this bug, decided to create the patch ... and upload it to GitHub as open source.



How to install it



We only have to download the last available compressed file (there are two versions: 32-bit or 64-bit), extract its content in a new folder and, when we have the latter open, press CTRL + Shift + right click, and select the option 'Open PowerShell window here'.



Once the terminal is open, we must enter the following commands to install it:



RUNDLL32.EXE SETUPAPI.DLL,InstallHinfSection DefaultInstall 132 .i30flt.inf



wevtutil im i30flt.man



fltmc load i30flt



If something goes wrong and we need to uninstall, just type the following:



RUNDLL32.EXE SETUPAPI.DLL,InstallHinfSection DefaultUninstall 132 .i30flt.inf



But this patch is just that: a patch (its creators even qualify it as a mere 'mitigation filter'), and that is why OSR insists that this vulnerability You will only have a definitive solution through an official Windows update.



Via | MakeUseOf