If Chrome still shows 157 after you read about Chrome 158, check the release note for your device before troubleshooting. Google’s November 12 notices describe limited rollouts for Windows and Android. Two devices can report different versions even when both are updating normally.

Check the operating system and release channel
Google’s November 12 desktop notice lists builds 158.0.8127.36 and 158.0.8127.37 for Windows, with Mac to follow in the early rollout. Its separate Android notice lists 158.0.8127.36 for a small percentage of users and says Google Play availability would expand over the following days. Those notices describe the start of distribution. They do not say when any particular installation will receive 158.
Check for an update through the usual route
On a personal Windows or Mac computer, open Chrome’s menu and choose Help → About Google Chrome. Record the full version shown. If Chrome downloads an update and offers Relaunch, save any work in your open tabs before restarting. Visit the About page again to confirm which build is running. On Android, check Chrome’s listing in Google Play for an Update button. Google’s Chrome update instructions explain the normal update paths.
Tell a rollout delay from an update error
Say your personal laptop has Chrome 158 and your Android phone still shows Chrome 157. Check each device against its own release notice and update screen. If the phone’s store listing offers no update, check again later as the rollout expands. If the browser instead shows a specific installation error, save its wording and the current version. The error is a better starting point for troubleshooting than the difference between two version numbers.
On a managed computer, ask your administrator which channel and update policy apply. Google’s release cadence guide explains why Extended Stable receives major versions on a different schedule. A colleague’s browser may be on a different channel even if both computers run the same operating system.
Report the exact build when a site behaves differently
If a page only fails on one device, record its operating system, full Chrome version and the step that fails. For example, note whether a form button disappears at a narrow window width or whether a submitted form returns an error. That lets a developer test the specific behavior on the affected browser. TechPulse’s browser support guide covers how to choose versions for a compatibility check.
Prepared with AI assistance using Google’s release and support documentation. The device comparison is illustrative. Read the TechPulse editorial policy.
✍️ Leave a Comment