Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
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.
Install the Valheim-specific BepInExPack Valheim package, not a generic BepInEx archive. For a manual installation, extract the package outside the game directory, move everything inside BepInExPack_Valheim into the Valheim game or dedicated-server directory, and confirm that the resulting root contains BepInEx, winhttp.dll, and doorstop_config.ini. On Linux, make start_server_bepinex.sh executable, update its launch arguments, and run it. BepInEx bootstrap messages in the server terminal confirm that the loader started.
Choose the correct Valheim package
The package you need is BepInExPack Valheim by denikson, distributed through Thunderstore. It is customized for Valheim and should not be replaced with an unmodified upstream BepInEx download. The package includes the loader files, Valheim-specific configuration, and startup scripts expected by the game and dedicated server.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Thunderstore lists automated installation through Gale, Thunderstore Mod Manager, and r2modman. Those workflows are mainly designed for the game client. A managed dedicated-server host may also provide an automatic BepInEx option, but the exact controls depend on that host. If you need predictable files, portability, or an installation you can repair yourself, use the manual method below.
Package contents, launch scripts, and compatibility can change when Valheim or the pack is updated. Check the current BepInExPack Valheim listing before installing a new release or upgrading an existing server.
Prepare the server before copying files
Stop the game and make a rollback copy
Stop the Valheim client or dedicated server before changing its files. Copy the complete installation directory, or at minimum the existing BepInEx directory and server configuration, to a separate backup location. A clean backup lets you remove the loader without guessing which files belonged to it.
Locate the directory that must contain the loader
For a client, this is the directory containing the Valheim executable. For a dedicated server, use the directory containing the server executable and the normal server launch files. The loader files must sit beside that executable; placing them in a parent directory, a download folder, or a nested copy of the package will prevent startup injection.
Free tools Windows power users keep installed
One-click scans. No signup required.
Record the normal server command
Before installing BepInEx on Linux, save the command that currently starts the server successfully. You will copy its values into the BepInEx launcher script. Record the server name, port, world name, password, visibility setting, and any arguments added by your hosting environment. BepInEx does not replace those settings.
Manual installation on Windows or Linux
- Download the manual archive. From the BepInExPack Valheim Thunderstore listing, choose the manual download rather than assuming a mod-manager package is suitable for a dedicated server.
- Extract to a temporary location. Unpack the archive somewhere outside the Valheim installation, such as a temporary folder on your desktop or home directory. Do not extract directly into the game directory. This makes it easier to see which files belong to the pack and avoids creating an accidental extra directory level.
- Open the package folder. Inside the extracted files, open
BepInExPack_Valheim. The files you need are inside this folder, not one level above it. - Move the contents, not the outer folder. Move every file and directory inside
BepInExPack_Valheiminto the Valheim installation or dedicated-server directory. If the operating system asks whether to merge directories, allow theBepInExdirectory to merge with an existing one only when you intentionally are updating the same installation and have a backup. - Check the resulting root. The destination should directly contain the loader directory and bootstrap files. A typical root looks like this:
| Item | Purpose | Where it should appear |
|---|---|---|
BepInEx/ |
Configuration, plugins, patchers, and runtime data | Directly in the Valheim or server directory |
winhttp.dll |
Windows loader/bootstrap component | Beside the Valheim executable |
doorstop_config.ini |
Loader configuration used during startup | Beside the Valheim executable |
| Additional Unity/Mono support files | Runtime support included by some pack releases | At the same installation root when supplied by that release |
If you instead see a path such as Valheim/BepInExPack_Valheim/BepInEx, the files are one level too deep. Move the contents of the inner folder up so that the executable and loader files share the same root.
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!
- Start the program once. Launch the client or server using its ordinary method. The first run creates or updates BepInEx configuration and log files. Do not add plugins until the loader itself starts cleanly.
Linux dedicated-server procedure
Make the supplied launcher executable
From the directory containing the script, run:
chmod u+x start_server_bepinex.shThe command grants execute permission to your user without changing permissions for everyone else. If you copied the files as another account, make sure the account that runs the server can read the entire installation and execute the script.
Match the script to your existing server settings
Open start_server_bepinex.sh in a text editor. Keep the BepInEx wrapper and change the Valheim launch parameters so they match the command that previously started your server. At minimum, verify the server name, port, world, password, public or private visibility, and any host-specific arguments. Preserve required quoting around names containing spaces and do not remove arguments your host uses for data paths, graphics mode, or process management.
Recommended Free Tools
Do not create a second, conflicting set of world or network settings in another script. The BepInEx script should become the one command used to launch this instance, while retaining the same values that made the unmodded server reachable.
Run the script
Start it from the server directory:
./start_server_bepinex.shWatch the terminal from the beginning of startup. Successful loading is indicated by BepInEx bootstrap messages appearing in that terminal before or alongside the normal Valheim server output. If the server reaches its normal ready state but no BepInEx output appears, stop it and troubleshoot the file placement, script permissions, and script path before adding mods.
Rank #3
- Gaming Inspired Design
- Geek Culture
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Windows client and dedicated-server notes
Windows client
With the package files beside the Valheim executable, launch the game normally. The Windows pack requires no additional configuration for the standard game path; when the loader is active, a separate console window should appear. Close the game and review the installation root if the console never appears.
Windows dedicated server
Keep the BepInEx pack files beside the dedicated-server executable and adapt the host’s ordinary Windows start command so it launches that executable from the modified directory. The package documentation does not publish a separate, exhaustive Windows-server script, so retain the server’s existing name, port, world, password, visibility, and host-specific arguments rather than copying a client shortcut. Test from a backup or staging installation first if the server is publicly used.
Automated installation and when to use it
| Approach | Best fit | Important limitation | Rollback and control |
|---|---|---|---|
| Manual archive | Dedicated servers, Linux systems, and administrators who need direct file control | You must place files, set permissions, and maintain launch scripts yourself | Strongest control; a clean backup makes removal straightforward |
| Gale, Thunderstore Mod Manager, or r2modman | Client-side mod profiles and repeatable desktop setup | The documented workflows primarily target the game client, not every dedicated-server layout | Convenient profile management, but server files still need separate verification |
| Managed-host automation | Operators whose host exposes an automatic BepInEx installation switch | Menus, paths, restart behavior, and supported versions vary by host | Easy to enable, but keep an independent backup because host rollback controls differ |
Do not assume that installing BepInEx in a desktop mod profile also installs it on a remote dedicated server. The server has its own filesystem and must contain the loader beside its own executable.
Verify that BepInEx loaded
Linux server verification
Use the startup terminal as the primary check. BepInEx bootstrap messages should be visible during launch. Save a copy of the first successful startup output if you administer several worlds; it provides a useful baseline when a later plugin or Valheim update changes behavior.
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
Windows client verification
The loader’s console window is the immediate visual indication on the standard Windows client path. If it is absent, check that winhttp.dll and doorstop_config.ini are beside the executable and that you did not leave them inside BepInExPack_Valheim.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Use a small test plugin when the indication is unclear
The package documentation suggests installing a simple test plugin such as MessageCenter from BepInEx.Utility. Add only that test plugin to the BepInEx/plugins directory, start the game or server, and look for its visible message or corresponding log entry. Remove the test plugin after verification if you do not need it. A test plugin confirms that the plugin chain is functioning; it does not prove that every gameplay mod is compatible.
Troubleshoot the common failure modes
| Symptom | Likely cause | Corrective action |
|---|---|---|
| No loader output on Linux | The script is not being used, lacks execute permission, or the pack is in the wrong directory | Run chmod u+x start_server_bepinex.sh, launch the script from the directory containing the server executable, and verify the root-level file layout. |
| Server starts unmodded | The normal server command still launches the original executable from another directory | Change the service, panel, shortcut, or shell command to use the BepInEx script and confirm its working directory. |
| Permission denied on Linux | The script is not executable or the server account cannot read the installation | Apply the user execute permission, check ownership and read access for the server account, and avoid running the process from a directory mounted with execution disabled. |
| Game or server fails immediately after copying | Files were merged into an old, incompatible installation or an archive was unpacked at the wrong level | Stop the process, restore the backup, create a clean Valheim installation, and repeat the extraction and move operation without nesting the package folder. |
| Plugins do not appear to load | The loader starts but the plugin is in the wrong directory, has missing dependencies, or is incompatible | Confirm the plugin is under BepInEx/plugins, test with one simple plugin, and add other plugins one at a time so the failing addition is identifiable. |
| Clients cannot join after enabling mods | Launch parameters changed, the server is using a different world or port, or clients and server have incompatible mod sets | Compare the BepInEx script with the saved unmodded command, verify the world and network values, and have every player use the mod versions required by the server. |
| A mod breaks after a Valheim update | Valheim, the community pack, or the mod has changed compatibility | Reproduce the issue with only BepInEx enabled, consult the current Valheim-specific package and mod documentation, and restore the last known-good backup while waiting for compatible releases. |
Updating, removing, and rolling back safely
Update the pack
Stop the server, back up the complete installation, and compare the new archive with the existing root. Replace pack-managed files according to the current release instructions, but preserve your server worlds and carefully review changes under BepInEx/config. Start without third-party plugins first, confirm the loader, and then re-enable plugins in small groups.
Remove BepInEx
Use the backup made before installation when possible. Otherwise, stop the process and remove the BepInEx directory, bootstrap files, and pack-specific support files from the server root, then restore the original launch command. Do not delete world saves or unrelated server configuration files.
Best Value
- Gaming Inspired Design
- Gaming and Geek Inspired
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Keep client and server changes coordinated
A dedicated server installation and a client installation are separate. Updating one does not update the other. Record the pack version and plugin list used by the server, and give players the same information before they connect. This prevents a working server from appearing broken when the actual mismatch is on a player’s client.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesSupport boundaries for this package
BepInExPack Valheim is community-maintained and customized for Valheim. Its package documentation states: “The Valheim community runs a customized version of BepInEx and the official BepInEx folks are unable to help.” For that reason, start troubleshooting with Valheim-specific package documentation and the mod’s own instructions rather than assuming guidance for a generic BepInEx game applies unchanged.
When requesting help, include the operating system, whether the installation is a client or dedicated server, the pack version, the exact launch command or script parameters, the root-level file listing, and the first startup log. Redact passwords and private addresses before sharing logs.
Quick Recap
Final preflight checklist
- The package is BepInExPack Valheim, not a generic archive.
- The archive was extracted outside the game directory before copying.
- The contents of
BepInExPack_Valheimwere moved into the executable’s directory without an extra nesting level. - The root contains
BepInEx,winhttp.dll, anddoorstop_config.ini, plus any support files included by the release. - The original server command, world, network, password, and visibility settings are backed up.
- On Linux,
start_server_bepinex.shis executable and contains the correct launch parameters. - The server is started through the BepInEx script, not an old unmodded shortcut or service entry.
- Startup output or the Windows console confirms the loader before additional plugins are installed.
- A clean backup exists before every pack or plugin update.
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.
