Windows Self-Hosted runner continues to throw an error failing to update the status.

Question

I'm trying to execute the PowerShell script provided and continue to get the following exception.

I've tried several things.  I've removed brackets around the UID's. I've tried concatenating the PowerShell arguments to a string versus an array.  I've installed PowerShell 7 and ran the script as an admin. I've also tried to execute the runner.jar application directly.

Below is the initial error using the provided script. Any help would be appreciated.

[2026-10-14 15:45:33,532] Runner starting.

[2026-10-14 15:45:34,611] Failed to set up a Bean Validation provider: jakarta.validation.NoProviderFoundException: Unable to create a Configuration, because no Jakarta Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath.

[2026-10-14 15:45:34,645] Runner version: 6.0.8

[2026-10-14 15:45:34,646] Runner runtime: windows-powershell

[2026-10-14 15:45:34,647] Metrics registry configured: io.micrometer.core.instrument.simple.SimpleMeterRegistry

[2026-10-14 15:45:34,719] Updating runner state to "OFFLINE".

[2026-10-14 15:45:35,729] An error occurred whilst updating runner state to "OFFLINE".

com.atlassian.pipelines.stargate.client.core.exceptions.StargateBadRequestException: Response Summary: HttpResponseSummary{httpStatusCode=400, httpStatusMessage=Bad Request, bodyAsString={"key":"agent-service.request.bad-request","message":"Can not transition runner state from UNREGISTERED to OFFLINE","arguments":{}}}

at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)

Suppressed: The stacktrace has been enhanced by Reactor, refer to additional information below:

Error has been observed at the following site(s):

*__checkpoint ⇢ 400 BAD_REQUEST from PUT https://api.atlassian.com/ex/bitbucket-pipelines/rest/internal/accounts/%7B{UID}%7D/repositories/%7B{UID}%7D/runners/%7B{UID}%7D/state [DefaultWebClient]

Mark Smith · Answer

We did some more testing and found that the runner was not able to run from a server running in Hyper-V. Not sure why… but that's something to consider.

We were able to execute and start the runner on any other machine outside of Hyper-V.  Is this an issue? Is there a way to get the runner to execute on a virtual server?

Trevan Householder_Isos-Tech-Consulting_ · Answer

Good work narrowing it down, @Mark Smith. Working from your dev machine but not the build server points squarely at that host's network, and @Arkadiusz Wroblewski nailed it with BCLOUD-23446 . That UNREGISTERED to OFFLINE message is just the runner failing its first handshake, not the root cause.

When you talk to your network team, have them check outbound HTTPS (443) from the build server to api.atlassian.com and bitbucket.org, plus any SSL inspection. The ranges are in IP addresses for runners behind corporate firewalls. If there's a proxy, Windows runners pick it up from the host config, and authenticated proxies aren't supported.

One tip: I'd create a separate runner for the build server instead of reusing the one now online from your dev machine.

Mark Smith · Answer

It looks like there might be something blocking on the build server that I'm trying to use.  I was able to get the runner online using my development machine.  I'll talk with the guys about it.

I reply back if I was able to resolve it.  Thanks.