## Summary I cannot run the build because the build path has the short token of 9 on server while on git is registered with 8. Any suggestion? Gitlab-runner version=15.11.0 and version=18.3.1 executor shell GitLab Enterprise Edition v17.11.6-ee <!--Briefly summarize the bug--> ## Steps to reproduce Add new runner on biosphere, get the token and run on windows server 2025 > .\\gitlab-runner.exe register --url [https://xxxxx](https://xxxxx) --token glrt-12345678UQ3xMKbWcFqu Runtime platform arch=amd64 os=windows pid=14120 revision= 436955cb version=15.11.0 Enter the GitLab instance URL (for example, https://gitlab.com/): \[[https://xxxxx](https://xxxxx)\]: Enter a name for the runner. This is stored only in the local config.toml file: {----}: MSBuild .NET NEW2 Enter an executor: parallels, shell, ssh, virtualbox, docker-autoscaler, docker-ssh+machine, kubernetes, custom, docker, docker-windows, docker-ssh, docker+machine, instance: shell Verifying runner... is valid **runner=12345678U** Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded! Configuration (with the authentication token) was saved in "..\\config.toml" On Gitlab the new runner is labeled with **(12345678)** Running the pipeline fail to find the solution because the build path on file system is ...\\builds\\12345678U\\0 and NOT ...\\builds\\12345678\\0 as expected I'm just moving the runner on new PC with newer OS. In the past with Windows Server 2019 I had no problem with the pipeline <!--What do you need to do to reproduce the bug? Please include job definitions or git repository structure if relevant--> <!--Please add the definition of the job from `.gitlab-ci.yml` that is failing inside of the code blocks (```) below.--> <details> <summary>.gitlab-ci.yml</summary> ```yml Add the job definition that is failing here ``` </details> ## Actual behavior Running the pipeline fail to find the solution because the build path on file system is ...\\builds\\12345678U\\0 and NOT ...\\builds\\12345678\\0 as expected <!--What actually happens--> ## Expected behavior <!--What you should see instead--> ## Relevant logs and/or screenshots <!--Paste the job logs inside of the code blocks (```) below so it would be easier to read.--> <details> <summary>job log</summary> ```sh Add the job log ``` </details> ## Environment description <!--Are you using shared Runners on GitLab.com? Or is it a custom installation? Which executors are used? Please also provide the versions of related tools like `docker info` if you are using the Docker executor.--> <!--Please add the contents of `config.toml` inside of the code blocks (```) below, remember to remove any secret tokens!--> <details> <summary>config.toml contents</summary> ```toml [[runners]] name = "MSBuild .NET NEW2" url = "https://xxxxx" id = 7535 token = "glrt-12345678UQ3xMKbWcFqu" token_obtained_at = 2025-11-19T08:24:57Z token_expires_at = 0001-01-01T00:00:00Z executor = "shell" [runners.cache] MaxUploadedArchiveSize = 0 Add your configuration here ``` </details> ### Used GitLab Runner version Version: 18.3.1 Git revision: 5a021a1c Git branch: 18-3-stable GO version: go1.24.4 X:cacheprog Built: 2025-09-04T15:24:16Z OS/Arch: windows/amd64 and Version: 15.11.0 Git revision: 436955cb Git branch: 15-11-stable GO version: go1.19.6 Built: 2023-04-21T20:32:42+0000 OS/Arch: windows/amd64 <!--Please run and paste the output of `gitlab-runner --version`. If you are using a Runner where you don't have access to, please paste at least the first lines the from build log, like: ``` Running with gitlab-ci-multi-runner 1.4.2 (bcc1794) Using Docker executor with image golang:1.8 ... ```--> ## Possible fixes <!--(If you can, link to the line of code that might be responsible for the problem) --->