Enable lock pages in memory configuration on Github-hosted windows runners

[diogomatsubara]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Actions Runner

Discussion Details

We have a CI job that requires the following registry edit:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v LockedPagesLimit /t REG_DWORD /d 0 /f

After the edit this requires a reboot of the instance to take effect. If the runner is rebooted, I believe the job will automatically fail. Is there any way to preconfigure the instance to have such config before startup? Or any way to make the change and reboot the instance so they can take effect?

[Denoroy737]

Hi, @diogomatsubara

GitHub-hosted runners cannot be rebooted or preconfigured with custom registry edits like LockedPagesLimit. Each runner instance is ephemeral, meaning it’s destroyed after each job.

To use that configuration, you must:

• Self-host a Windows runner where you have admin access.
• Apply the registry edit and reboot that machine manually once.
• Register it as a self-hosted runner in your repository or organization.

Official docs:
🔗 GitHub Docs – Hosting your own runners

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬