Try the new Overwolf Troubleshooter now!
Windows OS Updates ▾
Overwolf may not launch properly or even crash when Windows is outdated. We highly recommend making sure that all Windows system updates are installed, as they are necessary for the proper operation of different components (.NET Framework, for instance). To check if there are updates available for your system, please click here.
If you have any system updates pending, please install them, restart your system and then try to launch Overwolf again.
In case you're still unable to launch Overwolf, please try the following solutions:
"Failed to start application" ▾
Please uninstall Overwolf from your system and reinstall it to the default directory, C:\Program Files (x86)\Overwolf\.
- This issue can also be caused due to a missing Windows component - Microsoft Visual C++ Redistributable (read more about it here).
Download this component here, install it, restart your system and try to launch Overwolf again.
If these solution did not help, please try the System File Checker.
System File Checker ▾
Running a system file check can fix faulty system files that are required for Overwolf to run properly.
It's easy to run such a check - just follow these steps:
- Run CMD as administrator
- Paste the following command into the CMD and press 'Enter' to run it: sfc /scannow
- The process can a bit of time, that's normal :)
Once the process is finished check if the issue is fixed.
If it isn't, try to run it again with 3 additional commands, in the following sequence:
- sfc /scannow
- Dism /Online /Cleanup-Image /CheckHealth
- Dism /Online /Cleanup-Image /ScanHealth
- Dism /Online /Cleanup-Image /restoreHealth
- sfc /scannow
If that doesn't fix the issue either, please open this folder: C:\Windows\Logs\CBS and send us the file called CBS.log as well as your Overwolf logs for inspection, so we can provide further assistance.
Antivirus Software ▾
- Stuck on "Preparing for first launch..."
In certain cases, Overwolf's first launch (after installation) comes across an issue and cannot continue.
We have found this can happen due to an antivirus software called 'SAntivirus' (or Segurazu Antivirus) and that disabling it can solve the issue. For more information, please click here. - Even though Overwolf is 100% safe to use and is very popular among gamers all over the world, some antivirus programs have blacklisted it in the past, and using them might prevent Overwolf from launching properly on your PC.
If upon launching Overwolf, nothing happens (the Appstore won't open, you can't see the dock, etc.), please follow the next steps:
- Click on the Windows key + R
- Type: "regedit" and click "Yes"
- In the file explorer to your left, start opening folders by this path:
HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows NT -> CurrentVersion -> Image File Execution Options
- On the file explorer to your left, look for folders named 'overwolf.exe' and 'overwolflauncher.exe'
- If they exist, right-click them and choose "Delete"
- Try running Overwolf
Failed to start application please contact support
If you have any antivirus program (except for Windows Defender) such as 360 Total Security, please temporarily close or disable it, then run the Overwolf Troubleshooter to fix Overwolf.
If it works and Overwolf runs properly, please let us know the name of the antivirus service (and any additional relevant information) so we can work this out with them.
If you do not have an antivirus program or the solution above hasn't worked, please download this file: chrome_elf.dll, put it in Overwolf's version installation folder (for example: ‘C:\Program Files (x86)\Overwolf\*version*’), then try to launch Overwolf again.
.NET Framework ▾
Overwolf is based on .NET Framework 4.8 and later .NET versions.
It's possible that .NET 4.8 wasn't installed properly on your PC, in which case Overwolf won't be able to run due to some corrupted files.
This might occur due to a Windows update gone wrong or due to outdated drivers.
The best solution is reinstalling your current .NET Framework 4.8 version:
- Press the Windows key + R
- Type in: appwiz.cpl
- Click on "Turn Windows features on or off"
- Look for the ".NET Framework 4.8" and uncheck the box next to it
- Click "OK" and wait
- Once it is done close it and restart your computer
- Follow steps 1-4 in order to re-check the ".NET Framework 4.8" option
- Restart your computer
- Try running Overwolf
machine.config file ▾
Certain corruptions in .NET Framework's machine.config files may prevent Overwolf from running.
To fix these corruptions, please follow these steps:
- Open the folder C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\
- Locate the file called 'machine.config'
- Delete the file
- Locate the file 'machine.config.default'
- Create a copy of it (just as back up)
- Rename the original 'machine.config.default' file to 'machine.config'
- Repeat steps 2-4 for the folder C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\
- Re-launch Overwolf
"Could not find essential Overwolf files..." ▾
If you received this error, please try the following solutions:
- Open the following directory C:\Program Files (x86)\Common Files\Overwolf\0.xxx.x.xx (version number) and check if it contains the following files: OverwolfHelper.exe and OverwolfHelper64.exe
If these files are missing, please reinstall Overwolf using this installer. - Open the following directory C:\Program Files (x86)\Overwolf, check that it contains the file Overwolf.exe and that the file is not set to run as an administrator.
If the file is missing, please make sure that it's not getting deleted/quarantined by an anti-virus software, then reinstall Overwolf using this installer.
Overwolf Setup Installer ▾
If the above-mentioned solutions did not help you overcome the issue, please try to run the setup installer. It comes in a zipped file, so you will first need to extract it by using any program like WinZip, WinRAR or 7-Zip.
Issue not resolved? Try running the Overwolf Troubleshooter!
If it doesn't resolve the issue please click on Create Logs Zip and then Contact Support to open a support ticket with your log files so we can further investigate the matter.