Windows Runners only register successfully once, then 404 (Not found)

[MarkusWillinger]

Hello,
I am running ARC Windows Runners on AKS Azure Kubernetes. Basically the setup seems to work, after initial installation I get 1 successfully registered Windows Runner in my GitHub repo. The build starts and everything seems to be fine. But after the build the runner disappears from runner list in Github. In AKS nodepool I can see that the Windows runners try to register again or connect again? But without success. Below is the log of the pods. Anyone has an idea what I could check? Any help would be highly appreciated!

| ____ _ _ _ _ _ _ _ _ |
| / () || | | | | |_ / \ | |() ___ _ __ ___ |
| | | | | __| || | | | | ' \ / _ \ / | | |/ _ | ' / | |
| | || | | || _ | || | |) | / ___ \ (| || | () | | | __ \ |
| _||_|| ||_,|.__/ // __|_||_/|| ||___/ |
| |
| Self-hosted runner registration |
| |

---

Authentication

Http response code: NotFound from 'POST https://github.xyz.com/api/v3/actions/runner-registration'
{"message":"Not Found","documentation_url":"https://docs.github.com/[email protected]/rest"}
Response status code does not indicate success: 404 (Not Found).
1 file(s) copied.
An error occurred: Not configured. Run config.(sh/cmd) to configure the runner.
"Runner listener exit with terminated error, stop the service, no retry needed."
"Exiting runner..."

[MarkusWillinger]

Figured it out myself: That happens when running ./config runner registration script with expired runner token or PAT (which is not supported for registration of runners).