actions-runner fails to start the service as "Failed to Lock Service Database for Write" is being thrown when registering an Azure VM as github runner

[pb185235]

I am using the actions-runner version 2.316.1 but still getting the error saying "Failed to Lock Service Database for Write" while trying to register an Azure VM as github runner. Please suggest how do we fix it? I am trying to register VM as github runner through "az vm run-command" and using config.cmd.

[wisecort]

This usually means Windows Service Control Manager (SCM) could not get a write lock while installing the runner as a service. With az vm run-command, that often happens because the command is not running elevated, or another installer is holding the SCM lock.

Fix

1. RDP into the VM (or use a serial/admin shell) and open PowerShell as Administrator
2. Configure the runner without relying on az vm run-command for the service install:

cd C:\actions-runner
.\config.cmd --url https://github.com/<org-or-repo> --token <TOKEN> --runasservice

3. If it still fails, install the service explicitly after config:

.\config.cmd --url https://github.com/<org-or-repo> --token <TOKEN>
.\svc.cmd install
.\svc.cmd start

Also check

• No other MSI/service install running at the same time
• You are on a supported Windows image with admin rights
• Avoid installing the Windows service through az vm run-command when possible (elevation/lock issues are common there)

If this solves it, please mark as accepted.