Choose your game

Inferno shows driver initialization error 1 when I inject

What to do when the Inferno loader stops at driver initialization error 1 on Rainbow Six Siege, and the point at which it needs a human.

You open the Inferno loader, paste your key, click through to the injection step, and instead of loading you get driver initialization error 1. It shows up at the moment injection starts, and it typically repeats across several attempts. It is reported most often by people running Inferno on Rainbow Six Siege, and the same message has also come up on Frost Pro for R6.

Why this happens

Our documentation does not list this exact message, so we will not guess at what it means. What the documentation does say is that security software can flag tools that interact with running applications, and that antivirus can stop a loader running correctly. The steps below are the Windows security checks support works through first when this error is reported. Be aware up front that support records show this particular error often survives all of them. If that happens to you, it is not something you did wrong and it is not something you can diagnose yourself, and the next step is a human rather than more troubleshooting.

How to fix it

  1. Turn off Reputation-based protection in Windows Security. This is the first thing support asks for on this error.
  2. Turn off Core Isolation, including Memory Integrity, then restart your PC. Real-time protection alone being off is not enough here.
  3. Open Virus and Threat Protection and disable all settings, including real-time protection. The Trace 2.0 guide also recommends DControl if you want antivirus fully disabled.
  4. Uninstall any other anti-cheat client completely rather than just closing it. FACEIT and Vanguard are the two that come up most often.
  5. Install the current Microsoft Visual C++ redistributables, restart Windows, then download a fresh copy of the loader from its official guide. Only use loaders linked from an official guide.
  6. Run the loader as administrator and try the injection again.

If your security software flags the loader file itself instead of showing this error, stop and send support the detection name and a screenshot rather than working around it.

Which products this applies to

This page is written for Inferno on Rainbow Six Siege, which is where the error is reported most. The same steps are the ones support uses when the message appears on Frost Pro for R6. Both are Rainbow Six Siege products.

Still broken

If you have done all of the above, restarted, and the error still appears, that is a common outcome on this one and it is the point where it stops being self serviceable. Open live support with your product name, the game, the exact error text, and the steps you have already completed, and a human will pick it up. If you need specifics on what the error means, ask support rather than working around it.

Still stuck after this? Contact support and quote the exact message you see.