How to Delete ScriptHookV2: A Complete Removal Guide for GTA Modders
ScriptHookV2 is a modding framework used in Grand Theft Auto V that allows custom scripts to run inside the game engine. While it's a popular tool for extending gameplay, there are plenty of reasons you might want to remove it — getting rid of unused mods, preparing to play GTA Online safely, or troubleshooting a game that won't launch. Deleting it correctly matters more than most players realize.
What Is ScriptHookV2 and Why Does Removal Require Care?
ScriptHookV2 (sometimes referred to as Script Hook V 2 or Alexander Blade's Script Hook V) is a runtime library that bridges custom .asi scripts with GTA V's game code. It works by injecting into the game process at launch, which means it leaves behind more than just one file.
The framework typically includes:
ScriptHookV.dll— the core injection librarydinput8.dll— often used as a loader hookNativeTrainer.asi— a bundled trainer script- Any additional
.asiplugins you installed alongside it
Because ScriptHookV2 hooks into DirectInput and the game's native function table, a partial removal can leave orphaned .dll files that still trigger on launch. That's why "just deleting one file" often doesn't fully solve the problem.
Step-by-Step: How to Fully Delete ScriptHookV2
1. Navigate to Your GTA V Root Directory
Open File Explorer and go to where GTA V is installed. Common locations:
- Steam:
C:Program Files (x86)SteamsteamappscommonGrand Theft Auto V - Rockstar Games Launcher:
C:Program FilesRockstar GamesGrand Theft Auto V - Epic Games:
C:Program FilesEpic GamesGTAV
Right-clicking the game in your launcher and selecting "Browse local files" or "Open file location" is the fastest method.
2. Delete the Core ScriptHookV Files
In the root game folder, locate and delete the following:
| File | Purpose |
|---|---|
ScriptHookV.dll | Core mod hook library |
dinput8.dll | DirectInput loader (if installed by ScriptHookV) |
NativeTrainer.asi | Bundled trainer script |
Any other .asi files | Third-party scripts using the hook |
⚠️ Before deleting dinput8.dll, confirm it was placed there by ScriptHookV. Some games use a legitimate system dinput8.dll. If you only installed ScriptHookV and no other tools that use this file, it's safe to remove.
3. Check for a Scripts Folder
ScriptHookV2 also supports a /scripts subfolder in the game root. If this folder exists and contains .cs, .vb, or .dll files from mods, those won't be removed automatically. Delete the /scripts folder entirely if you no longer want any script-based mods running.
4. Remove Any ASI Loader (If Applicable)
Some users install ASI Loader separately (commonly distributed by Alexander Blade as well). This may have added its own version of dinput8.dll. If you installed this as a standalone component, it should also be removed as part of a full cleanup.
5. Verify Game File Integrity After Removal 🎮
After deleting the files, run a file integrity check through your launcher:
- Steam: Right-click GTA V → Properties → Local Files → Verify integrity of game files
- Rockstar Launcher: Settings → My installed games → GTA V → Verify integrity
- Epic Games: Library → GTA V → three dots → Manage → Verify
This step replaces any legitimate game files that may have been modified or mistakenly deleted, and confirms your installation is clean.
Why People Delete ScriptHookV2 Before GTA Online
This is one of the most common reasons for removal. GTA Online bans the use of mod menus and script injectors, and even passive presence of ScriptHookV2 files can be flagged by Rockstar's anti-cheat. ScriptHookV itself is designed to disable when it detects an Online session, but relying on that behavior entirely is risky.
Players who switch between story mode modding and Online play typically delete the framework before launching Online, or maintain two separate game installations — one modded, one clean.
Variables That Affect How Your Removal Goes
Not every ScriptHookV2 installation looks the same. What you actually need to delete depends on:
- How it was installed — manual file placement vs. mod manager (like OpenIV or Vortex)
- Which version of ScriptHookV2 you're running — older builds had different file structures
- What other mods were installed alongside it — some mods add their own
.asiplugins that depend on the hook - Whether you used a mod manager — tools like Vortex may track installed files and offer a cleaner uninstall path
- Your OS permissions — some users on Windows 11 with UAC settings need to run File Explorer as administrator to delete files in protected program directories
When ScriptHookV2 Removal Doesn't Fix the Problem
If GTA V still crashes or behaves oddly after removing ScriptHookV2, the cause may be unrelated. Other possible culprits include:
- OpenIV-installed
.rpffile replacements — these modify game archives and persist independently of ScriptHookV - ENB or ReShade installations — graphics injectors that hook similarly but are separate tools
- Corrupted game files — predating the mod installation entirely
A full file integrity verification after removal is the clearest way to separate mod-related issues from underlying game problems.
One Setup, Different Outcomes
A player who dropped ScriptHookV2 files manually into a clean GTA V folder has a simple, predictable removal process. Someone who installed a full mod menu pack that included an ASI loader, trainer, custom scripts, and archive edits is dealing with a meaningfully different situation.
How straightforward your cleanup is depends entirely on the state of your current installation — and that's the part only you can assess by looking at what's actually in your game directory.