Prepare Windows
SirHurt leans on runtime libraries that a fresh Windows install often doesn’t ship, and its files look like a hack tool to every antivirus heuristic scanner. Sort both out before the first launch and you avoid most of the failures people blame on the injector.
Problems you skip here tend to surface later as “the bootstrapper closes instantly” or “a DLL is missing” - both are covered on the Troubleshooting page.
Step 1 - Give SirHurt its own folder
Section titled “Step 1 - Give SirHurt its own folder”Every later step (exclusions, cleaning, reinstalling) gets simpler if SirHurt lives somewhere obvious and predictable.
-
Create a dedicated folder for SirHurt - this is your SirHurt folder, and every later page refers to it by that name. If you extract with 7-Zip or WinRAR, you can normally use the folder the archive creates.
-
Keep it out of OneDrive-synced locations such as Desktop or Documents. Cloud sync can lock or “restore” files while you’re installing, which produces confusing partial installs.
-
Keep it out of
C:\Program Files. That tree is write-protected, so updates and the Cleaner both need elevation just to touch their own files.
Step 2 - Add antivirus exclusions
Section titled “Step 2 - Add antivirus exclusions”This is the single most important step. If your antivirus quarantines SirHurt’s files, nothing downstream will work, and the failure will look random rather than like an antivirus problem.
-
Open your antivirus or Windows Security (Windows Security → Virus & threat protection → Manage settings).
-
Temporarily switch off real-time protection so the next steps aren’t interrupted. Windows may re-enable this on its own after a while; that’s expected.
-
Add a folder exclusion for the SirHurt folder you created in step 1.
-
Add a second folder exclusion for
%LOCALAPPDATA%\Roblox. Paste that path exactly rather than browsing to it, so you don’t exclude the wrong profile. -
If anything was previously removed, open Protection history and restore the quarantined SirHurt files before continuing.
-
Verify the exclusions stuck by opening the exclusions list again and confirming both entries are present.
Step 3 - Repair system files
Section titled “Step 3 - Repair system files”Corrupt or mismatched Windows component files are a common cause of silent bootstrapper crashes. This chain checks the component store and repairs it from a known-good source.
-
Open the Start menu, type
PowerShell, right-click Windows PowerShell and choose Run as administrator. -
Paste the following single line and press Enter. It checks the exit code after every command and prints one green or red summary line at the end:
Terminal window $failed = $false; foreach ($step in @(@{Name='SFC scan';Exe='sfc.exe';Args=@('/scannow')},@{Name='DISM CheckHealth';Exe='dism.exe';Args=@('/Online','/Cleanup-Image','/CheckHealth')},@{Name='DISM ScanHealth';Exe='dism.exe';Args=@('/Online','/Cleanup-Image','/ScanHealth')},@{Name='DISM RestoreHealth';Exe='dism.exe';Args=@('/Online','/Cleanup-Image','/RestoreHealth')})) { Write-Host "==> $($step.Name)" -ForegroundColor Cyan; & $step.Exe @($step.Args); $code = $LASTEXITCODE; if ($code -notin 0, 3010) { Write-Host "FAILED: $($step.Name) exited with code $code" -ForegroundColor Red; $failed = $true; break } }; if ($failed) { Write-Host "ERROR: System repair chain failed." -ForegroundColor Red } else { Write-Host "SUCCESS: System repair chain completed. Reboot before continuing." -ForegroundColor Green } -
Let it finish without closing the window. This can take several minutes; DISM pauses at the same percentage for a long time and that is normal.
-
Check the last line. SUCCESS means the component store is healthy. Exit code
3010also counts as success - it means the repair worked and a reboot is required. If you get ERROR, the line above it names the command that failed, which usually points at a disk or permissions problem worth fixing before you go further. -
Reboot once before installing anything else.
Step 4 - Install the required runtimes
Section titled “Step 4 - Install the required runtimes”SirHurt will not start without these. Install both architectures of the Visual C++ redistributables a 64-bit Windows install is not a substitute for the x86 package.
-
Download and install the x86 Visual C++ Redistributable.
-
Download and install the x64 Visual C++ Redistributable.
-
Download and install the .NET Framework 4.8.1 web installer.
-
Use the installers’ defaults. There’s no need to customise components.
-
Restart your PC. The runtimes register themselves during the reboot, so skipping this leaves the bootstrapper unable to load them.
Step 5 - Verify you’re ready
Section titled “Step 5 - Verify you’re ready”Run through this list before moving on. Each item maps to a failure you would otherwise have to debug later.
-
Your SirHurt folder exists, and you know its full path.
-
Both antivirus exclusions (SirHurt folder and Roblox directory) are listed and confirmed.
-
The repair chain finished and printed SUCCESS.
-
Both VC++ redistributables and the .NET Framework 4.8.1 are installed.
-
You have rebooted since installing the runtimes.
-
You’re on Windows 24H2 or newer.
If every box is ticked, continue to Roblox Settings to configure Roblox itself. If something failed, check Troubleshooting the antivirus and hung bootstrapper sections cover these exact symptoms.
Made by SIX - Report Issues to them.