# Install QBCore on Windows with txAdmin

Use a new test profile and an empty database. This guide covers the Windows FXServer artifact layout and the [project-maintained QBCore recipe](https://github.com/qbcore-fivem/txAdminRecipe). Do not deploy the recipe over an existing production server.

> **What was checked**
> The recipe source was reviewed at commit `0f4f6d96bf707ef9de123afd59a4233504befab1`. The checks below are instructions for you to perform, not a claim that a Windows or FiveM runtime test was executed for this guide. Artifact filenames and compatibility can differ between GTA V Legacy and Enhanced.

![Windows QBCore installation flow with txAdmin](/diagrams/txadmin.svg)

*Conceptual diagram; verify the behavior against your installed resource version.*

## Before you begin

Have a Cfx.re account and server license key, an archive extractor, and a running MySQL or MariaDB service. txAdmin is bundled with FXServer; it does not install the database service for you. See the [Cfx.re illustrated txAdmin walkthrough](https://docs.fivem.net/docs/server-manual/setting-up-a-server-txadmin/) for screenshots of its setup screens.

### Create an isolated server directory

For example, keep binaries in `C:\FXServer\server` and let txAdmin create a separate data directory for your test profile. Do not use Downloads, a cloud-synced directory, or an existing production tree. Record the data directory chosen in txAdmin; that is where the recipe's `server.cfg` and `resources` belong.

### Install a current FiveM artifact

Download the recommended Windows artifact from the [Cfx.re artifacts service](https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/) and extract the complete archive into the binaries directory. Record its artifact build number.

Start `FXServer.exe` without `+exec server.cfg` to enter txAdmin setup. Open the URL printed in the console, use its setup PIN, link your Cfx.re account, and create an administrator password. Keep the console running. Follow the actual artifact's instructions if its executable has a different name.

**Checkpoint:** the txAdmin setup page loads and you can create a server profile. This is not yet proof that the game server is running.

### Prepare the database

Create an empty database and an application account restricted to it using your database administration tool. Use distinct credentials, not the database administrator's account.

| Deployment field | Example for a database on the same machine |
| --- | --- |
| Host | `127.0.0.1` |
| Port | Your configured database port; commonly `3306` |
| Database | `qbcore_test` |
| User | `qbcore_app`, granted access to `qbcore_test` only |
| Password | A unique password entered privately in the deployer |

Select that database in the deployer's database options. The account needs permission to import the recipe's schema in the selected database. Test the same host, user, and database in your database client first; an account that works with a different host name is not sufficient evidence.

**Checkpoint:** the application account connects to the empty test database. Do not expose the database port to the public internet or commit its connection string to Git.

### Deploy the QBCore recipe

Create the test profile in txAdmin, select QBCore from the available recipes, and verify the source points to `qbcore-fivem/txAdminRecipe`. Review the recipe before running it. Its [reviewed YAML](https://github.com/qbcore-fivem/txAdminRecipe/blob/0f4f6d96bf707ef9de123afd59a4233504befab1/qbcore.yaml) connects to the database, imports `qbcore.sql`, and downloads resources including `oxmysql`.

Enter the server license key and database options when requested. Run the recipe and inspect each failed task before continuing. Do not manually import a fictional `qb-core/server/database.sql` file or rerun a fresh-install recipe against a populated database to fix an error.

Review the generated [`server.cfg`](/docs/installation/server-config) in the selected data directory, including game endpoints and the private database connection setting. Keep the recipe's resource start order for the first boot, then save and start the server.

### Verify first boot

On the same Windows machine, start FiveM, open its F8 console, and use the configured game port. With the default port:

```text
connect 127.0.0.1:30120
```

For a server on another host, use that host's reachable address instead of `127.0.0.1`. Create a test character, disconnect, reconnect, and check that the character persists. Restart the profile through txAdmin and check again.

**Checkpoint:** the game connects, character data persists, and the console has no unresolved dependency or SQL errors. Continue with the [first-boot checklist](/docs/getting-started) before adding custom resources.

## Windows checks

Keep the database private and restrict txAdmin to an access-controlled administration path. Expose only the game ports actually configured for players; the web panel and database are not game ports. Run without administrator privileges where practical and back up files and the database separately.

`sv_enforceGameBuild` selects the clients' GTA game build, not the FXServer artifact. See the [artifact/build explanation](/docs/overview/faq#what-version-of-fivem-artifacts-should-i-run).

## If a checkpoint fails

| Symptom | Check next |
| --- | --- |
| txAdmin does not open | Read the terminal error, confirm the artifact extracted completely, and start without `+exec server.cfg`. Use the URL printed by that process. |
| Database access denied | Check the exact host, account, password, selected database, and database-scoped grants. Do not solve it by granting access to every database. |
| Table missing after deployment | Check the recipe's SQL task and selected database. Use [database troubleshooting](/docs/troubleshooting) before restarting dependent resources. |
| Missing resource or export | Find the first startup error and use the [resource load-order guide](/docs/troubleshooting/resource-load-order). |
| Remote connection fails | Check the configured game port, host firewall and provider/router rules using [connection troubleshooting](/docs/troubleshooting/connection-issues). |

## Sources and next steps

Source references: [Cfx.re txAdmin setup](https://docs.fivem.net/docs/server-manual/setting-up-a-server-txadmin/), [txAdmin startup behavior](https://github.com/citizenfx/txAdmin#running-txadmin), and the [reviewed QBCore recipe](https://github.com/qbcore-fivem/txAdminRecipe/blob/0f4f6d96bf707ef9de123afd59a4233504befab1/qbcore.yaml). Recipe dependencies may track moving branches; a pinned recipe does not pin every downloaded resource.

Next: [first-boot checks](/docs/getting-started) → [resource documentation](/docs/resources) → [safe update workflow](/docs/troubleshooting/resource-update-conflicts).
