Google plans Chrome updates that won’t require browser restarts

That restart gap has been a persistent headache for administrators managing fleets of devices. Google’s own Chrome update help page says updates happen automatically in the background, but enterprise forums and admin communities have repeatedly documented the same problem, patches land first, then users have to relaunch Chrome for them to finish. In Spiceworks Community threads, administrators described having to force Chrome closed, schedule reboots or push updates through group policy and endpoint tools because the browser would not fully update until the session ended.

The security stakes are high because browsers sit at the center of daily work, from student logins to payroll systems and court records. A restart-free model would give IT teams less time to coordinate with users and fewer delays before fixes reach vulnerable machines. It would also matter for organizations that can least afford downtime, including school districts, hospitals and local agencies that leave browsers open for hours or days at a time.

Google has already moved Chrome in ways that tighten security while changing how users experience the browser. On Dec. 21, 2023, the company announced performance and safety features for Chrome. On May 30, 2024, it began the Manifest V2 phase-out, and on Oct. 10, 2024, Google said it had started disabling extensions still using Manifest V2 in Chrome stable. Those changes showed a willingness to push security updates and policy shifts even when they disrupt established workflows.

The new dynamic patching work appears to go further by aiming to remove the restart step altogether for some updates. That could help close the exposure window between disclosure and protection, but it also raises familiar tradeoffs: users may not notice when a browser has changed, administrators may lose a clean checkpoint for testing and rollout, and troubleshooting could become less transparent if fixes arrive silently.