I have a Windows 11 PC that runs Chrome continuously in full-screen kiosk mode for a dedicated display or application. A browser update or restart during the workweek would interrupt its purpose, so I'm looking for a way to create a defined maintenance window.
Ideally, Chrome would avoid updating or restarting during the week, allow updates during a weekend period, and then automatically return to the weekday restrictions. I'd prefer to manage this with Chrome Enterprise policies, Group Policy, the registry, scheduled tasks, or PowerShell instead of changing settings manually.
I understand that Chrome needs to stay current for security. The goal is to control when maintenance occurs rather than leave the browser permanently outdated. What's the most reliable way to manage Chrome's update services, scheduled tasks, or policies on Windows 11?
3 Answers
Chrome Enterprise policies are the better-supported starting point. The Google Update policy templates can be deployed through Group Policy, and the equivalent settings can be configured under HKLMSOFTWAREPoliciesGoogleUpdate.
Those policies let you control update checks and related behavior without manually editing the machine every week. You can deploy different settings with scheduled scripts or management tooling, then run a separate scheduled task to restart Chrome during the maintenance window if an update is waiting. This is generally safer than permanently disabling the updater services.
For a dedicated kiosk, the most predictable approach is to coordinate Chrome’s update policies with Windows scheduled tasks. You can use a weekday task to stop or restrict the Google Update services and scheduled tasks, then create a weekend maintenance task that restores the normal startup settings and triggers an update check.
After allowing enough time for the update to finish, schedule a controlled reboot so Chrome starts cleanly with the new version. Before the operating period begins again, the weekday task can reapply the restrictions. Test this carefully on a spare machine, since disabling the updater can leave the browser without security fixes if the weekend task fails.
A scheduled reboot is useful for a kiosk, but I’d make the script verify that the update completed before restarting. Otherwise a slow download or locked Chrome process could make the maintenance window unreliable.
The Chrome policies can get close, but they don’t provide a perfect weekly maintenance-window control. Some settings can prevent checks during specified daily time ranges, while version-pinning policies can reduce unexpected feature changes. However, critical security updates may still be handled differently, and a daily time range is not the same as allowing updates only on weekends.
For that reason, I’d use policy as the baseline and add an explicitly scheduled weekend maintenance task. Make sure the machine has a recovery plan if the task fails, and monitor the installed Chrome version so an unsuccessful weekend update is noticed quickly.
This has worked well for us as a set-and-forget policy. We use a scheduled task or PowerShell action for the browser restart, while leaving the update configuration centrally managed.