See the [troubleshooting section](#troubleshooting) if you encounter any
errors during the Runner installation.
1. (Optional) Update Runners `concurrent` value in `C:\GitLab-Runner\config.toml`
to allow multiple concurrent jobs as detailed in [advanced configuration details](https://docs.gitlab.com/runner/configuration/advanced-configuration.html).
to allow multiple concurrent jobs as detailed in [advanced configuration details](../configuration/advanced-configuration.md).
Voila! Runner is installed, running, and will start again after each system reboot.
Logs are stored in Windows Event Log.
...
...
@@ -75,6 +78,10 @@ Logs are stored in Windows Event Log.
```
1. Download the binary for [x86][] or [amd64][] and replace runner's executable.
You can download a binary for every available version as described in
[Bleeding Edge - download any other tagged release](bleeding-edge.md#download-any-other-tagged-release).
If you encounter a _The service did not start due to a logon failure_ error
while starting the service, please [look in the FAQ](../faq/README.md#13-the-service-did-not-start-due-to-a-logon-failure-error-when-starting-service-on-windows) to check how to resolve the problem.
If you don't have a Windows Password, Runner's service won't start but you can
use the Built-in System Account.
If you don't have a Windows Password, Runner's service won't start but you can
use the Built-in System Account.
If you have issues with the Built-in System Account, please read
If you have issues with the Built-in System Account, please read
[How to Configure the Service to Start Up with the Built-in System Account](https://support.microsoft.com/en-us/kb/327545#6)