Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Install the Valheim-specific BepInExPack Valheim package, not a generic BepInEx archive. For a manual installation, extract the package somewhere outside the game directory, open BepInExPack_Valheim, and move everything inside it into the Valheim installation or dedicated-server directory. The resulting root should contain BepInEx, winhttp.dll, and doorstop_config.ini. On Linux, make start_server_bepinex.sh executable, update its Valheim arguments, and run it; BepInEx bootstrap messages in the terminal confirm that the loader started.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Valheim servers with free DDoS protection and up to three free backups a day.
What you are installing
BepInEx is the loader and plugin framework used by many Valheim modifications. A server installation places the loader beside the Valheim server executable so that BepInEx can initialize before the game server and load compatible plugins.
As an Amazon Associate I earn from qualifying purchases.
Use BepInExPack Valheim by denikson from Thunderstore. It is a Valheim-specific, community-maintained package with files and launch handling prepared for this game. Do not substitute a generic upstream BepInEx archive simply because its name looks similar. The package documentation warns that Valheim runs a customized version and that the official BepInEx maintainers cannot support it; Valheim-specific package documentation is the appropriate troubleshooting reference.
Package contents and Valheim compatibility can change between releases. Check the current package listing and the release notes that accompany the archive before applying an update to a production server.
Choose an installation method
| Approach | Best fit | What you control | Important limitation |
|---|---|---|---|
| Manual file installation | Self-hosted Windows or Linux servers, and administrators who need predictable files | Exact package version, folder placement, backups, and rollback | You must maintain the files and launch command yourself. |
| Automated client manager | A local Valheim game installation used for playing | Profile-based mod installation and removal | Gale, Thunderstore Mod Manager, and r2modman workflows are primarily documented for the game client, not a dedicated server. |
| Managed host automation | A rented dedicated-server service that exposes a BepInEx installer | Usually fewer file and startup tasks | Availability, file paths, backup behavior, and update timing depend on the host. |
The package documentation confirms that managed dedicated-server hosts may offer automatic BepInEx installation, but it does not establish a universal control-panel procedure. If you use a host, follow its current instructions and verify the resulting server directory and startup log rather than assuming a client manager installed the server.
Prepare the server before changing files
Stop the server cleanly
Shut down the Valheim process before copying or replacing loader files. A running process can keep files open and can write configuration or world data while you are making a backup.
Back up the installation and world data
Keep a copy of the current server directory and your world saves. A clean backup makes it possible to remove BepInEx without guessing which files were added, and it gives you a recovery point if a plugin or package update prevents startup.
Record the normal launch command
Write down the command that currently starts your server, including its server name, port, world, password, visibility setting, and any host-specific arguments. On Linux, you will copy those values into the BepInEx launcher script. Do not replace working values with examples from another server.
Use a clean or known-good Valheim installation
The manual workflow is simplest when the game or dedicated-server directory is clean. If an earlier loader or partial extraction is present, restore your backup or remove the old installation first so that you do not mix files from different package releases.
Download the correct Valheim package
- Open the Thunderstore listing named BepInExPack Valheim and confirm that the author is denikson.
- Choose the manual archive when you intend to copy files yourself. Automated installation buttons for Gale, Thunderstore Mod Manager, and r2modman are aimed mainly at a client game installation.
- Save the archive somewhere temporary, such as a downloads or staging directory, rather than directly inside the Valheim folder.
- Note the package release version and retain the original archive with your backup. This lets you identify which package was installed and return to it if a later release causes a problem.
Do not extract the archive directly into the final game directory. The package contains a wrapper folder, and extracting at the wrong level is the most common reason the server cannot find the loader files.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Manual installation on Windows
1. Extract outside the game directory
Use Windows Explorer or an archive utility to extract the downloaded package into a temporary folder. After extraction, open the folder named BepInExPack_Valheim. You should see the package payload inside that folder rather than immediately in the Valheim directory.
Rank #2
- Viking Game laminated laptop stickers All approx 3"-4" in length
- Laminated, Not UV Proof. Will fade in sun. Best used indoors.
- Great for Laptops, Phones, Computers, Tablets and more!
- Handmade by a Stay at Home Small Business Mama!
2. Move the payload, not the wrapper folder
Select everything inside BepInExPack_Valheim and move or copy those items into the directory that contains the Valheim executable or the dedicated-server executable. Do not create an extra level such as Valheim/BepInExPack_Valheim/BepInEx; the loader files must be beside the executable.
3. Check the expected root
At the end of the copy, the server root should include at least:
BepInEx, the loader and plugin directory.winhttp.dll, the Windows loader component.doorstop_config.ini, the loader configuration file.
Some versioned releases also include unstripped Unity or Mono support files. Keep those files in place when they are included in the package; do not copy only the three easily recognizable items.
Recommended Free Tools
4. Start the server with its usual command
Use the same Windows server shortcut, batch file, control-panel command, or executable arguments that worked before installation. The searched package documentation does not publish a separate, exhaustive Windows dedicated-server script, so adapt the host’s existing launch method rather than inventing a new command line.
For the Windows game client, the package requires no extra configuration: when the loader is working, launching the game opens a BepInEx console. A dedicated server may present its own console behavior, so use the server’s startup output and a test plugin rather than relying on the client-specific window description.
Install and launch on a Linux dedicated server
1. Copy the package into the server directory
Extract the manual archive into a temporary location, open BepInExPack_Valheim, and move its contents into the directory used by the Valheim dedicated server. The final directory should contain the BepInEx directory and the package’s loader files, including doorstop_config.ini and the Linux-compatible files supplied by that release.
Keep the package’s directory structure intact. Do not place the entire BepInExPack_Valheim folder beside the server executable and do not move only the BepInEx directory.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- Gaming Inspired Design
- Geek Culture
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
2. Make the launcher executable
Change to the directory containing the supplied script and run:
chmod u+x start_server_bepinex.shThe u+x mode grants execute permission to the file’s owner. If your hosting account uses a different owner or a control panel invokes the script under another account, make sure that account can read the files and execute the script.
3. Match the script to your existing server command
Open start_server_bepinex.sh in a text editor. Replace the example or inherited Valheim launch values with the values from your normal command:
- server name;
- port;
- world name;
- password;
- public or private visibility;
- any arguments required by your Linux host or service manager.
Preserve the BepInEx-related parts of the script. The goal is to change the Valheim parameters, not to remove the loader setup. Keep a copy of the edited script with your server backup so a reinstall does not lose your working command.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall4. Run the script
From the server directory, execute the launcher:
./start_server_bepinex.shIf your host starts services through a panel, systemd unit, container entry point, or another supervisor, configure that service to invoke the BepInEx script instead of the original Valheim executable command. The exact integration is host-specific; the essential requirement is that the BepInEx launcher is the process that starts the server.
5. Read the terminal output
Successful Linux startup produces BepInEx bootstrap messages in the server terminal. These messages are the practical indication that the loader initialized. If the server reaches its normal startup output but no BepInEx bootstrap messages appear, stop and check the directory level, execute permission, script command, and package contents before adding plugins.
Verify that BepInEx loaded
Use the server terminal on Linux
Watch the first part of the startup log for BepInEx bootstrap messages. This is more useful than waiting for a mod to change gameplay because it confirms that the loader itself started. Save a copy of a successful log when you first install the package; it provides a baseline for later comparisons.
Rank #4
- Valheim Boar Loves You quote. A perfect design for fans of the best selling Viking game.
- An amazing and unique design which is also perfect as a gift.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Use the console behavior on Windows client installations
For the Windows game path described by the package, launching the game should produce a BepInEx console when the loader is working. This observation applies to the client workflow documented by the package and should not be treated as a universal dedicated-server display requirement.
Use a small test plugin when the indication is unclear
If there is no obvious client-side indication, the package suggests installing a simple test plugin such as MessageCenter from BepInEx.Utility. Install a version compatible with your Valheim and BepInEx package, start the game or server through the correct launcher, and look for the plugin’s expected message. Remove the test plugin after verification if you do not need it; it is a diagnostic aid, not a requirement for BepInEx itself.
Check the placement before checking plugins
A plugin cannot load when the bootstrapper is not loading. Confirm the root directory and startup command first, then investigate an individual plugin’s compatibility or configuration. This order prevents a plugin problem from being mistaken for a failed BepInEx installation.
Troubleshoot the common failure modes
No BepInEx messages appear on Linux
- Confirm that
start_server_bepinex.shis in the directory from which the server is launched. - Run
chmod u+x start_server_bepinex.shagain and verify that the account starting the server owns or can execute the file. - Check that the contents of
BepInExPack_Valheim, rather than the wrapper directory itself, were moved into the server root. - Verify that the service, panel, or shell is invoking
./start_server_bepinex.shand not the old Valheim command. - Compare the script’s name, world, port, password, visibility, and other arguments with the known-working command.
The server starts but the game or world settings are wrong
The loader can initialize even when the script contains incorrect Valheim arguments. Reopen the script and compare every launch parameter with the normal server command. Pay particular attention to the world name, port, password, public visibility, and any arguments added by your host.
Free tools Windows power users keep installed
One-click scans. No signup required.
The files seem to be present but the loader still does not start
Look for an extra extraction level. The correct arrangement has BepInEx, doorstop_config.ini, and the other package files directly in the same installation or server directory as the executable. If you see BepInExPack_Valheim as the only item at that level, move its contents up one level.
A plugin fails after BepInEx loads
Separate the loader test from the plugin test. First confirm BepInEx bootstrap messages. Then remove or disable the newly added plugin and start again. A plugin can be incompatible with the current Valheim build, the package release, or another plugin even when the base loader is functioning. Use Valheim-specific package documentation for compatibility and configuration guidance.
Support is unclear
The package documentation explicitly sets a support boundary: “The Valheim community runs a customized version of BepInEx and the official BepInEx folks are unable to help.” Direct questions to the Valheim-specific package documentation and community channels rather than assuming generic BepInEx instructions apply unchanged.
Best Value
- Gaming Inspired Design
- Gaming and Geek Inspired
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Keep the installation maintainable
Preserve a rollback copy
Keep the original package archive, the working launcher script, and a backup of the server directory and worlds. If an update fails, stop the server, restore the previous files, and return to the recorded launch command. A clean rollback is safer than deleting files at random because package releases can contain additional Unity or Mono support files.
Update one layer at a time
When Valheim, BepInExPack Valheim, and plugins all change, update them separately where practical. Start the server after the package update and check bootstrap output before adding or updating plugins. This gives you a clear point of failure if startup changes.
Keep client and server profiles aligned
A dedicated server installation is separate from a modded client installation. Installing BepInEx through a client manager does not, by itself, place the loader on a remote server. Players may also need client-side plugins or matching versions, but those requirements belong to each mod’s documentation; do not infer them from the server loader’s successful startup.
Document host-specific paths
Managed hosts can place the executable, save data, and startup script in different directories. Record the actual server root, the command used by the control panel, the package version, and the date of a successful start. This documentation turns a future migration or restore into a repeatable procedure.
Windows, Linux, and automation: practical trade-offs
| Decision | Manual installation | Automation or manager |
|---|---|---|
| Control over files | You choose exactly what is copied and can retain a release archive. | The tool or host determines placement and update behavior. |
| Dedicated-server suitability | Works when you can access the server directory and startup command. | Client managers are primarily for the game client; host automation varies. |
| Linux startup | Requires editing and executing start_server_bepinex.sh. |
A host may expose a one-click installer, but its script and paths are host-specific. |
| Rollback | Straightforward when you made a clean backup before copying files. | Depends on whether the manager or host retains package versions and backups. |
| Verification | Read bootstrap output and test with a simple plugin if needed. | Still requires checking the actual server log; an installation button is not proof of loading. |
There are no published benchmark figures, success-rate statistics, or universal prices for these approaches. The meaningful choice is operational: manual installation gives you file and rollback control, while automation can reduce routine copying when your host supports it.
A compact installation checklist
- Back up the server directory, world data, and current launch command.
- Download BepInExPack Valheim by denikson, not a generic archive.
- Extract the manual archive outside the Valheim directory.
- Open
BepInExPack_Valheimand move its contents into the executable’s directory. - Confirm the root contains
BepInEx,winhttp.dllon Windows,doorstop_config.ini, and any other files supplied by the release. - On Linux, run
chmod u+x start_server_bepinex.sh. - Edit the script so its server name, port, world, password, visibility, and host arguments match the normal command.
- Start Linux servers with
./start_server_bepinex.shor configure the host service to invoke that script. - Look for BepInEx bootstrap messages in the Linux terminal.
- If the indication is unclear, test with a simple compatible plugin such as MessageCenter, then isolate plugin problems from loader problems.
- Keep the package release, script, backup, and successful startup log together for rollback.
What a successful installation looks like
The final result is not merely a folder named BepInEx. The package payload is in the same root as the Valheim executable, the server starts through the BepInEx-aware launcher, and the startup output shows the BepInEx bootstrap process. On Linux, those terminal messages are the clearest practical success signal. On Windows client installations, the package documents a BepInEx console; dedicated-server presentation can differ, so verify the server’s own output.
Once that baseline works, add plugins one at a time and retain the ability to restore the clean backup. If a Valheim update or package release changes behavior, repeat the placement and launch checks before assuming that every plugin has failed.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
