From 5c01a2dc17bb19b404641e424ada54d481d5a50a Mon Sep 17 00:00:00 2001 From: CDRLpart <115928334+CDRLpart@users.noreply.github.com> Date: Tue, 19 May 2026 21:34:53 +0200 Subject: [PATCH] Fix typo in README instructions Corrected the spelling of 'CRTL' to 'CTRL' for clarity. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d90dd45..722ede3 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ How to reproduce : 1. Copy the FsTx folder to "**YourUSBStick:**\System Volume Information\FsTx" as is and make sure to use a filesystem that's compatible with Windows (NTFS is preferable but I think FAT32/exFAT should work as well). Funny thing is, the vulnerability is extremely convenient, you don't even need to plug an external storage device, you can just pull out the disk, copy the files in the EFI partition, put it back and it will still work. That's how bad it is. 2. Plug the USB stick in your target windows computer with bitlocker protection turned on. 3. Reboot to Windows Recovery Environment Agent (you can do that by holding SHIFT and clicking on the restart button using your mouse) -4. Once you click on the restart button, lift your finger off the SHIFT key and hold CRTL and do NOT lift your finger off it. +4. Once you click on the restart button, lift your finger off the SHIFT key and hold CTRL and do NOT lift your finger off it. 5. If you did everything properly, a shell will spawn with unrestricted access to the bitlocker protected volume. shell