Original announcement: · Reporting prepared on the publication date above.
What to know
- Use the stable release information for your operating system.
- Check the running browser after relaunch, not only the download status.
- Keep a device list and test the applications your team actually uses.
The 29 October release
Google announced a Chrome Stable and Extended Stable update on 29 October 2026: 156.0.8078.79/.80 for Windows and Mac, and 156.0.8078.79 for Linux. The release lists 21 security fixes, including a critical memory-corruption issue in MediaStream. Availability rolls out over time; consult the official Chrome release archive for the complete announcement and later releases.
Check that the update has actually applied
On desktop, open Chrome’s menu, choose Help, then About Google Chrome. Let it check for updates and relaunch when prompted. Linux installations may need their package manager. Google explains these differences in its Chrome update instructions. Downloading an update and running the updated browser are separate steps.
Build a useful office inventory
For a small team, a shared device list is more useful than an announcement that “everyone should update.” Record each device owner, operating system, browser channel, installed version, restart status and any application that needs testing. Include spare laptops, reception computers and devices used only for invoicing.
Have one person own the follow-up. A browser on an offline laptop does not update just because every computer currently in the office passed a check.
Try the workflows your team depends on
Use a pilot group to check the actual workday: sign in to the customer portal, complete a test video call, open the document tools and verify any required extensions. Record a simple pass or fail and who can resolve a problem. Avoid entering real customer data into an unapproved test environment.
Keep the production fleet on its intended channel. Installing a development-channel browser is a separate decision, not the normal remedy for a delayed stable rollout.
Make browser maintenance repeatable
Choose a regular review time, a clear deadline for restarts and an exception process for devices that cannot update. Pair version checks with a review of extensions and account access. These are Kiava’s operational recommendations; the release notice alone does not prove that any particular device was compromised.
Read our passkey and MFA guide for the sign-in layer. For a coordinated office rollout, outline your requirements through Kiava IT services.
Sources & further reading
Primary sources supporting this article. The practical recommendations are Kiava’s general guidance and should be adapted to your project.