To install AsaApi for an ARK: Survival Ascended dedicated server, install the supported 64-bit Microsoft Visual C++ runtime, extract the AsaApi release into your server’s ARKShooterGameBinariesWin64 directory, launch the server with AsaApiLoader.exe using the same parameters as the normal server executable, and place each plugin in ArkApiPlugins. The server must run on Windows; the official ASA Server API listing names Windows 10 or Windows Server 2019 as minimum operating systems.
Godlike.Host offers hosted ARK: Survival Evolved servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
The exact current AsaApi release and the definitive Visual C++ year are not established consistently in published setup material. Use the latest supported x64 redistributable, follow the plugin’s own README when folder layouts differ, and use ArkApi.log to diagnose loading failures.
As an Amazon Associate I earn from qualifying purchases.
What AsaApi does and what you need
AsaApi is a server-side plugin framework for ARK: Survival Ascended (ASA). It loads native server plugins when a Windows dedicated server starts, allowing plugins to add or change server behavior without modifying the base game files. It is not a client-side mod and does not install through the in-game mod browser.
This guide covers a manual Windows installation. Before changing files, stop the server and make a backup of the server directory and configuration files. A failed plugin should not be allowed to overwrite a working installation while you are troubleshooting.
#1 Best Overall
- ARK: Survival Ascended has completely recreated and redesigned the artwork and worlds of ARK to take advantage of the latest in videogame technology, Unreal Engine 5, using high-end graphics features such as fully dynamic Global Illumination (“Lumen”), so that light bounces realistically of off surfaces and provides realistic reflections, and advanced mesh streaming (“Nanite”) of hundreds of millions of triangles for extreme detail.
- Advanced new physics systems such as dynamic water so that every creature creates waves, ripples, splashes, and bubbles as they move through fluids, and fully interactive physical foliage where every blade of grass, bush, and tree reacts to characters, explosions, projectiles, and physics objects.
- ARK: Survival Ascended includes access to all of ARK’s worlds, including Scorched Earth, Aberration, Extinction, ARK Genesis Part 1, ARK Genesis Part 2, and more. The Island is released now, with the subsequent expansion worlds to be added at no additional cost on a regular basis.
- Thorough Quality of Life revamps in every area: redesigned User Interfaces, dynamic navigation for intelligent creature pathfinding, Wild Babies, Photo Mode, new Camera systems, new Map system, Tracking System, new Structures and Items, new Creatures, and much more.
- Cross-Platform Modding: Download & play new custom content created by players, including new maps, creatures, items, and game modes, through a dedicated new Mod-bowser directly within the game! Enjoy an endless stream of new ARK content as the creativity and talent of the community is fully unleashed for the first time ever across gaming platforms!
Prerequisites
- A Windows ASA dedicated-server installation with access to the server’s files and the account that runs the server.
- Windows 10 or Windows Server 2019 or a later supported Windows release. The official ASA Server API listing names Windows 10 and Windows Server 2019 as minimum requirements.
- The latest x64 Microsoft Visual C++ redistributable that is supported by your Windows version.
- An AsaApi release archive downloaded from the official ASA server API resource or the ArkServerApi GitHub organization.
- Plugin files compiled for ASA and for the AsaApi version you are running.
- A way to edit the server’s launch command or shortcut so the loader can be started instead of the normal server executable.
Which Visual C++ redistributable should you install?
Published instructions disagree on the year, so do not treat a single year number as a permanent compatibility rule. The official ASA Server API listing refers to the Visual C++ 2019 redistributable, one hosting guide names Visual C++ 2022, and the ASA Plugin Template asks for the latest x64 MSVC redistributable while targeting AsaApi v1.19. A Microsoft Q&A community answer says the current Visual C++ 2015–2022 package covers the 2019 and 2022 runtime families; that answer is community guidance rather than a definitive Microsoft compatibility statement.
| Source or project | Runtime wording | How to use the information |
|---|---|---|
| Official ASA Server API listing | Visual C++ 2019; Windows 10 or Windows Server 2019 minimum | Establishes the documented baseline, but may not reflect every newer build. |
| Hosting setup guide | Visual C++ 2022 | Shows that newer instructions may expect the newer runtime family. |
| ASA Plugin Template | Latest x64 MSVC redistributable; template targets AsaApi v1.19 | Use the x64 package and match the plugin’s documented API target. |
| Microsoft Q&A community answer | Latest supported Visual C++ 2015–2022 package | Useful compatibility guidance, but verify the package on Microsoft’s own download page. |
For a normal 64-bit ASA server, install the x64 package rather than relying on an x86-only runtime. The community answer links to Microsoft’s x64 installer at https://aka.ms/vc14/vc_redist.x64.exe. The Microsoft download page should be your authority for the current package, servicing status, and installation requirements.
Verify the runtime before blaming a plugin
- Install or repair the x64 redistributable with the server stopped.
- Reboot if Windows requests it, especially after replacing an older runtime.
- Start the loader once with no third-party plugins installed. This separates a missing runtime from a plugin-specific failure.
- If the loader still exits immediately, inspect the normal Windows application error and the ASA API log before adding plugins.
Download AsaApi and place the loader correctly
Download the AsaApi release from the official ark-server-api.com resource or the ArkServerApi GitHub organization. Check the release notes and the plugin README for compatibility before extracting anything. The current release number was not consistently surfaced in available setup material, so do not assume that an old tutorial’s version is current.
- Stop the ASA server process and close any server-management panel that may automatically restart it.
- Locate the directory that contains
ArkAscendedServer.exe. In a standard installation this is the server’sARKShooterGameBinariesWin64directory. - Extract the AsaApi archive directly into that
Win64directory. Do not leave the archive contents inside an extra nested folder such asWin64AsaApiWin64. - After extraction, confirm that
AsaApiLoader.exeis in the same executable directory as the ASA server binary and that the archive’s accompanying files are beside it. - Keep the original
ArkAscendedServer.exein place. The loader starts the server; it does not replace or rename the original executable.
Why the extraction location matters
AsaApi is loaded from the server’s 64-bit binary directory. Putting the files in the game client directory, the server’s top-level folder, or a panel-specific temporary folder means the loader may not find the server binary or its supporting files. If you maintain several ASA server instances, repeat the installation in each instance’s own Win64 directory; do not point multiple instances at one shared plugin tree unless the hosting software explicitly supports that arrangement.
Rank #2
- Brand new UK Import PAL version. Game in English. UK PSN store account required to use any online features
Start the server through AsaApiLoader.exe
Once the files are extracted, start AsaApiLoader.exe, not ArkAscendedServer.exe. The loader must receive the same launch parameters that the server previously used. This includes the map, server name, ports, passwords, cluster options, and any other arguments already present in your shortcut, script, scheduled task, or hosting panel.
- Open the shortcut, batch file, scheduled task, or panel entry that currently starts
ArkAscendedServer.exe. - Copy the existing argument string without changing its values.
- Change only the executable being launched to
AsaApiLoader.exe, preserving the working directory as the ASA server’sWin64directory. - Save the entry and start the server once with no optional plugins. Watch the console for AsaApi initialization and dependency messages.
- Allow the server to reach its normal ready state, then stop it cleanly. A clean first start confirms that the loader can launch the base server before plugins are introduced.
Do not start the same instance with both executables. Doing so can create port conflicts, lock files, or a false impression that a plugin loaded when the server was actually started without AsaApi.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Panel and service launches
Some control panels expose only a server executable field, while others provide a custom startup command. Set the executable field to AsaApiLoader.exe if the panel permits it and retain the panel’s existing arguments. If the panel cannot launch a custom executable, use its documented custom-startup feature or a Windows service wrapper that can invoke the loader. Do not remove arguments merely to fit a panel form; missing parameters can change the server’s map, ports, or cluster behavior even when AsaApi itself loads.
Install ASA plugins in the ArkApi directory
After a loader-only start succeeds, stop the server and install one plugin at a time. This makes the first failure identifiable and lets you remove the last change instead of guessing among several DLLs.
Rank #3
- Ark graphics and worlds are completely recreated and designed to use the latest video game technology, Unreal Engine 5
- Advanced new physical systems such as dynamic water and fully interactive physical leaves
- Design your survivor, shape the trunk and tame, train, multiply and ride dinosaurs in a vivid ecosystem
- Public online mode for up to 70 players, private multiplayer mode for up to 8 players + local split screen for 2 players
- Create or locate
ARKShooterGameBinariesWin64ArkApiPlugins. - Read the plugin’s README for its required AsaApi version, dependencies, configuration files, and folder layout.
- Copy the plugin files into the required location. A commonly documented layout is a per-plugin directory such as
Win64ArkApiPluginsPluginName. - For plugins using the matching-name rule, ensure the DLL name and its containing folder name match exactly, including capitalization where the plugin documentation requires it. Renaming the folder can prevent the DLL from loading.
- Keep each plugin’s configuration and dependency files with the plugin unless its README specifies a separate location.
- Start the server through
AsaApiLoader.exeand check the log before adding another plugin.
Two layouts appear in published instructions
| Layout | Example | When to use it |
|---|---|---|
| Per-plugin subfolder | Win64ArkApiPluginsPluginNamePluginName.dll |
Described by the ASA server manager documentation and used by many packaged plugins. |
| DLL plus matching folder name | A plugin DLL in its named folder under ArkApiPlugins, with the folder and DLL names matching |
Use when the plugin guide explicitly requires the matching-name rule. |
These descriptions can look contradictory because one describes the directory tree and the other emphasizes the name relationship. Follow the plugin’s own README when it is more specific. Do not invent a second nested directory to “make both” layouts fit; an extra level is a common reason a loader cannot see a DLL.
Install dependencies in the documented order
AsaApi checks plugin dependencies during startup and displays warnings when a requirement is missing. Treat a dependency warning as a load-order or installation problem, not as proof that the plugin itself is broken. Install the required dependency first, restart, and confirm that its warning disappears before evaluating the dependent plugin.
Windows 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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteConfirm that AsaApi and plugins loaded
The regular AsaApi log is located at ARKShooterGameWin64logsArkApi.log. Crash logs are stored under ARKShooterGameSavedLogs. Examine the log from the same startup in which you tested the plugin; an older successful run can otherwise hide a current failure.
What to check in the normal log
- Whether AsaApi initialized before plugin discovery.
- Whether the expected plugin directory was scanned.
- Dependency warnings or messages naming a missing module.
- A DLL load error, architecture error, or missing runtime message.
- The plugin name and version, if the plugin reports them.
Save a copy of the log before restarting repeatedly. A second launch can overwrite or append to the evidence you need for diagnosis.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot “ARK ASA plugin not loading”
The loader does not start or closes immediately
- Runtime: Repair or install the latest supported x64 Visual C++ redistributable. A missing runtime is especially likely when both the loader and every plugin fail.
- Wrong executable: Confirm that the panel, shortcut, or service launches
AsaApiLoader.exe, notArkAscendedServer.exe. - Wrong directory: Verify that the loader is beside the server executable in
Win64, not inside an extra extraction folder. - Working directory: Set the launcher’s working directory to the same
Win64folder so relative paths resolve correctly. - Permissions or locks: Stop duplicate server processes and ensure the account running the service can read and execute the extracted files.
After each correction, start once and inspect ArkApi.log. Avoid changing the runtime, launch arguments, and plugin files simultaneously; that removes the information needed to identify the cause.
AsaApi starts but one plugin is absent
- Open
ArkApi.logfrom that launch and search for the plugin name, a DLL error, or a dependency warning. - Check that the plugin is under
Win64ArkApiPluginsand not one directory above or below it. - Compare the DLL and folder names with the plugin README. A name mismatch can stop loading.
- Confirm that the plugin was built for ASA and for the AsaApi API version installed on the server.
- Install any listed dependency and restart before testing again.
- Remove every other newly added plugin and retest the suspect plugin alone.
The log reports a missing dependency
Install the named dependency in the location specified by its author, then restart the server. If the warning persists, check whether the dependency itself has a version requirement or a required folder name. Do not silence the warning by renaming files: AsaApi’s dependency check is telling you that the plugin’s expected module is not available under the required identity.
Free tools Windows power users keep installed
One-click scans. No signup required.
The server crashes after adding a plugin
Stop the server, remove the last plugin, and start the loader with the previously working set. Check both ArkApi.log and ARKShooterGameSavedLogs for the crash-time module name. If the base loader works, add plugins back one at a time. A crash that appears only when one DLL is present points to that plugin or one of its dependencies; a crash with every plugin removed points back to the loader, runtime, launch parameters, or server files.
A plugin works on one server but not another
Compare the two instances’ AsaApi release, server build, Visual C++ runtime, launch parameters, and plugin directory trees. Also compare the logs for dependency warnings. Separate server instances can silently use different Win64 folders, so verify the absolute path shown by the panel or service rather than assuming both installations share files.
Building a plugin yourself (optional)
The ASA Plugin Template documents a development setup for authors who want to compile their own plugin. It uses AsaApi.lib and targets AsaApi v1.19. The library can be built from the AsaApi solution in a Release/x64 configuration or taken from an AsaApi release.
Development prerequisites
- Visual Studio 2022.
- The Desktop development with C++ workload.
- vcpkg integration, as required by the template.
- The ASA Plugin Template’s source and its stated AsaApi version target.
Build and deploy workflow
- Install Visual Studio 2022 and select the Desktop development with C++ workload.
- Configure vcpkg integration as described by the template.
- Obtain or build
AsaApi.libfor Release/x64. - Open the template project and confirm that its AsaApi target matches the server’s framework version.
- Build the plugin as a 64-bit release DLL.
- Deploy the DLL and any required configuration or dependency files using the plugin’s documented
ArkApiPluginslayout. - Start through
AsaApiLoader.exeand inspect the log for load and dependency messages.
A plugin compiling successfully does not guarantee that it will load on every server. The server’s AsaApi build, the plugin’s target version, runtime libraries, and directory naming must all line up.
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 glitchesVersion, hosting, and maintenance limits
There is no consistently confirmed current AsaApi release number in the available setup references, and the published Visual C++ year differs between sources. Treat version compatibility as a release-specific question: read the AsaApi release notes and each plugin README before upgrading, and keep a copy of the previously working release so you can roll back.
Most setup instructions describe a manually managed Windows server. A hosting knowledge-base article title indicates that managed-host installation may be addressed separately, but its procedure was not verified. Ask a host whether it permits custom executables, DLL plugins, and AsaApiLoader.exe before purchasing or migrating an instance. If a panel cannot launch the loader or expose the required Win64ArkApiPlugins path, a manual installation may not be possible through that panel.
Safe update procedure
- Record the current AsaApi release, server build, plugin versions, and runtime package.
- Back up the entire server configuration and the working
ArkApidirectory. - Stop the server and test the new AsaApi release without third-party plugins.
- Review the log for loader errors before restoring plugins.
- Restore plugins one at a time, checking dependencies after each restart.
- If a regression appears, restore the backed-up loader and plugin set and document which version combination worked.
Quick installation checklist
- Windows 10, Windows Server 2019, or a later supported Windows release is running the dedicated server.
- The latest supported x64 Visual C++ redistributable is installed.
- The AsaApi archive was extracted directly into
ARKShooterGameBinariesWin64. AsaApiLoader.exeis besideArkAscendedServer.exe.- The loader receives the same launch parameters as the original server command.
- Plugins are under
Win64ArkApiPluginsusing the layout and names required by each README. - Dependencies are installed and no unmet-dependency warnings remain.
ARKShooterGameWin64logsArkApi.loghas been checked after the current startup.- Crash evidence, when present, has been checked under
ARKShooterGameSavedLogs.
The Bottom Line
For a reliable AsaApi installation, keep the loader and server executable together, start only through AsaApiLoader.exe, use the same launch parameters as before, and treat each plugin’s README as the authority for names, dependencies, and folder depth. When something fails, the x64 runtime, the exact executable path, and ArkApi.log are the first three checks.
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.
