Street Fighter V Root Kit Removal Tool Released
Peter Donnell / 4 years ago
Capcom really dropped the ball with their Street Fights V update, which used a root kit to manage the games licence without requiring online access, although it did need Kernal access to your OS, which is never a good thing. They later backtracked the update, but have now released an official tool to ensure you can close this gaping security loophole they installed on your system.
The Capcom.sys file was intended to protect against piracy and cheating, but it caused more problems than it resolved for many users, including crashes, BSOD and more. The newly released tool will help you remove the file, and all you have to do is download the latest Steam update for the game and follow the instructions below.
- Close the Street Fighter V application.
- Please keep the Steam client open. The Street Fighter V game update will begin automatically. Once the update is complete, you will notice 2 batch files have been added to the folder path below. (Please note that the location of the batch files may vary, depending on the users settings)
- C:\Program Files (x86)\Steam\steamapps\common\StreetFighterV\Tools
- Right click on DeleteSFVdriver_en.bat, and select “Run as administrator.”
- If you double click on the tool to run it, the tool will not run.
- DeleteSFVdriver_ja.bat is the same tool with Japanese instructions.
- Follow the instruction prompts.
- The tool will prompt you to restart your PC. Please restart your PC.
- Once your PC has restarted, right click on the DeleteSFVdrive_en.bat and select “Run as administrator”.
- Once the message “Capcom.sys or related registry doesn’t exist. End the program.” is displayed, the files have been deleted.
Capcom has warned that you should only use the official tool, not a third-party source. While some may be worried about running a .bat file, Capcom opted for this method “so that users can see the source code and be assured that this file does not contain any harmful data.”
They shouldn’t have created this mess in the first place, but at least the issue is now resolved.