Home » Articles » Features » Troubleshooting » 7 Ways to Fix Fellowship Not Launching on a Windows PC

7 Ways to Fix Fellowship Not Launching on a Windows PC

Discover how you can fix Fellowship not launching on Windows PCs with the potential resolutions covered within this troubleshooting guide. Is your Fellowship game a non-starter? If so, try kick-starting that game with the potential fixes below.

7 Ways to Fix Fellowship Not Launching on a Windows PC

The Fellowship MMO is now available as an Early Access title and has attracted many new players. Yet, some players say that the game doesn’t start on their PCs. One Fellowship player said, “Game [Fellowship] won’t launch… I press play on Steam and nothing happens.” This is how you can fix Fellowship not launching on Windows PCs.

Verify the Integrity of Fellowship Game Files

First, try repairing the Fellowship game files with a verification scan. There’s always a chance that a game that doesn’t start might have corrupted or missing files to repair. Click the Verify integrity button for Fellowship, as instructed on this Steam page.

The Verify integrity of game files option

The Verify integrity of game files option

Start Fellowship With Admin Rights

Running the Fellowship EXE game file with admin rights can be an effective way to fix Fellowship not launching for some players. Applying this possible fix can bypass permission issues preventing it from starting. You can run Fellowship with administrator rights like this:

  1. First, make sure Steam isn’t running in the background.
  2. Go to the C:\Program Files (x86)\Steam\steamapps\common\Fellowship\Binaries\Win64 game installation folder in File Explorer.
  3. Right-click the fellowship-Win64-Shipping file and select its Properties option on the context menu.
  4. Click on the Compatibility tab, and select Run this program as an administrator there.
    The Compatibility tab

    The Compatibility tab

  5. Select Apply > OK to finish.
  6. Double-click the fellowship-Win64-Shipping file to start the game.

Run the Arc3InstallSilent and EasyAntiCheat_EOS_Setup Files

Some players confirm that running the Arc3InstallSilent and EasyAntiCheat_EOS_Setup files can fix Fellowship not launching. Running those files will repair or install the required supporting software for the game that might be corrupted or missing. You can run the Arc3InstallSilent and EasyAntiCheat_EOS_Setup files like this:

  1. Open the Fellowship installation folder.
  2. Double-click the Arc3InstallSilent file there.
  3. Select a setup language and click OK.
    The Arc3InstallSilent file

    The Arc3InstallSilent file

  4. Next, open the EasyAntiCheat folder.
  5. Double-click the EasyAntiCheat_EOS_Setup in that directory to run it.
The EasyAntiCheat_EOS_Setup file

The EasyAntiCheat_EOS_Setup file

Set a DirectX Launch Option

Another player-confirmed way to fix Fellowship not launching is to set a DirectX launch option for it. That launch parameter can be for DirectX 11 or 12. This is how you can configure a DirectX API launch option for Fellowship:

  1. Start your Steam gaming client to go to its Library tab.
  2. Right-click the Fellowship game to select a Properties option.
  3. First, try entering -dx11 in the launch options box and then run the game.
    The Steam launch options

    The Steam launch options

  4. If the game still doesn’t start, input a -dx12 parameter in the launch options text box.

Run the Fellowship-launcher File With Admin Rights

Running the Fellowship-launcher file with administrator rights is a method that has worked for some players to resolve the issue of Fellowship not launching. Fellowship-launcher is the application (EXE) file for the game’s launcher. Try running that file with admin rights like this:

  1. Activate File Explorer by simultaneously pressing the Windows logo + E key combination.
  2. Navigate to the C:\Program Files (x86)\Steam\steamapps\common\Fellowship folder.
  3. Then, right-click the fellowship-launcher.exe file and select Run as administrator.
    The fellowship-launcher file

    The fellowship-launcher file

  4. If this works, I recommend setting the fellowship-launcher file to always run with administrator rights as instructed in steps three to five of resolution two above.

Uninstall Arc Launcher

Uninstalling Arc Launcher is a potential way to fix Fellowship not launching, as that might erase outdated or corrupted installation files. Then, the game will automatically install the latest and correct version when started. Applying this potential fix is especially recommended for those players with a beta version of the game installed. You can uninstall Arc Launcher like this:

  1. Activate Run by clicking Start with the mouse’s right button and selecting that accessory on the shortcut menu.
  2. Input the appwiz.cpl Run command and click OK.
  3. Select Arc Launcher in Programs and Features and click Uninstall to remove.
    The Programs and Features Control Panel applet

    The Programs and Features Control Panel applet

  4. Then, start the Fellowship game, which will automatically install Arc Launcher.

Reinstall Steam and Fellowship

Finally, try reinstalling Steam and the Fellowship game with it if nothing else works for you. Note that uninstalling Steam also removes all games installed with it unless you back them up. This Valve page tells you how users can uninstall and reinstall the Steam gaming client. Then, you’ll need to select the Install option for Fellowship in the Steam games Library tab to reinstall it.

I hope you fix Fellowship not launching by applying one of the potential resolutions above. Those troubleshooting methods are currently among the most widely confirmed ways to fix the game not starting. If the Fellowship still doesn’t start, you can ask the Arc Games support service for more potential fixes from this ticket submission page.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>