Error problems

[Tr285-ai]

Select Topic Area

Question

Feature Area

Issues

Body

Can someone help me with these error messages

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[ddryzhov]

Hello! I can help you resolve both of these issues. They are actually connected.

You are getting Error 1069 because the password for the account running the GitHub Actions Runner service is incorrect, expired, or the account lacks the "Log on as a service" permission. You likely tried to open secpol.msc to fix the permissions, but you got the first error because Windows Home edition does not include secpol.msc (Local Security Policy).

The good news is that you don't need secpol.msc to fix this! Here is the step-by-step solution:

Step 1: Fix the Service Logon (Error 1069)

Press Win + R on your keyboard, type services.msc, and press Enter.

Scroll down and find your runner service: GitHub Actions Runner (Tr285-ai-N5StyleEA_Pro.win-docker-01).

Right-click on it and select Properties.

Go to the Log On tab.

Here you have two options:

Option A (Recommended): If you are using a specific user account ("This account"), re-enter your Windows user password in both the "Password" and "Confirm password" fields. Click Apply. (Note: When you click Apply, Windows will automatically grant this account the missing "Log on as a service" right!)

Option B: Select Local System account. This is easier and usually bypasses permission issues, though it gives the runner high privileges on your machine.

Go back to the General tab and click Start.

Step 2: What to do about secpol.msc?
As mentioned, this is missing because you are likely on Windows 10 or 11 Home. You can completely ignore this error. Simply applying the password via the services.msc window (Step 1) automatically grants the necessary background permissions that secpol.msc would have given you.

Tip: If the service still refuses to start after fixing the password, the easiest fix is to open your terminal as Administrator in the runner folder, run .\config.cmd remove, and then configure it again.

Let me know if this works for you!

[Tr285-ai]

thanks

[frazrajpoot01]

These two errors are actually closely related! You are likely seeing the secpol.msc error because you were trying to look up a fix for the "Error 1069" logon failure.

Here is exactly what is happening and how to fix both issues.

1. Why you are getting the secpol.msc error

The secpol.msc command opens the Local Security Policy editor. However, this tool is not included in Windows Home edition (it is only available on Pro, Enterprise, and Education). If you are running Windows Home, Windows will throw that "cannot find" error. People usually try to open this tool to manually grant an account the "Log on as a service" right, but you actually don't need secpol.msc to fix this!

2. How to fix Error 1069 (Logon Failure)

Error 1069 means the GitHub Actions Runner service is trying to start, but the Windows user credentials (password) assigned to the service are incorrect, have changed recently, or the account lacks the required permissions.

You can fix this and automatically grant the right permissions directly from the Services menu:

1. Press Win + R, type services.msc, and press Enter.
2. Scroll down the list and find your GitHub Actions Runner service (it will match the name in your screenshot).
3. Right-click the service and select Properties.
4. Go to the Log On tab at the top.
5. You will see "This account" selected. Re-type your current Windows account password in both the Password and Confirm Password boxes. (Make sure the username is correct as well).
6. Click Apply.
   (Note: If the password is correct, Windows will automatically pop up a message saying that the account has been granted the "Log On As A Service" right!)
7. Click OK, then right-click the service in the list again and click Start.

Alternative: If you don't need the runner to run under your specific user account, you can go to that same Log On tab, select Local System account, and click Apply. However, running as a specific user is generally recommended for GitHub Actions so it has access to the correct user-level paths and tools.

[Tr285-ai]

Thanks

[code-with-bhumi]

Hi @Tr285-ai,
It looks like you're hitting two common Windows configuration issues while setting up your runner. Here’s how to resolve them:

1. Fix for Error 1069 (Logon failure)
This happens because the account assigned to the service has an incorrect password or lacks "Log on as a service" permissions.
The Quick Fix:

Open services.msc (Win + R).
Find the GitHub Actions Runner service, right-click it, and select Properties.
Go to the Log On tab and select "Local System account".
Click Apply, then OK, and try starting the service again. This usually bypasses the credential issue entirely.

Reference: Microsoft Troubleshooting for Error 1069

2. Fix for "Windows cannot find 'secpol.msc'"
This error occurs because you are likely on Windows Home Edition, which does not include the Local Security Policy tool.
Solution:

If you follow the "Local System account" fix mentioned above, you don't actually need to use secpol.msc. The Local System account already has the necessary permissions to run services.

[Tr285-ai]

Thanks

[riteshpandey2024-cyber]

Hey bro ,

You're dealing with two separate issues here — let me break them down:

1. secpol.msc not found
   This means you're on Windows Home, which doesn't include the Local Security Policy editor. It's only available on Windows Pro/Enterprise.

Workaround for Windows Home: Open Command Prompt as Administrator and run:
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" /v LimitBlankPasswordUse /t REG_DWORD /d 0 /f

This achieves the same effect as the policy setting you were trying to access.

2. Error 1069 — GitHub Actions Runner service failed to start (Logon Failure)
   This is the main issue. Error 1069 means the Windows Service is configured with a user account whose credentials are wrong or the account doesn't have "Log on as a service" rights.

Fix:

1. Open Services (services.msc)
2. Find the GitHub Actions Runner service → right-click → Properties
3. Go to the Log On tab
4. Either switch to Local System account, or re-enter the correct username/password for the account
5. Then go to Local Security Policy (or use the reg fix above on Home) and grant that user "Log on as a service" rights under:
   Security Settings → Local Policies → User Rights Assignment
6. Restart the service

Tip: If you recently changed your Windows account password, the service still has the old password stored — that's the most common cause of Error 1069. Just update the credentials in the Log On tab.

[Tr285-ai]

Thanks