Google is being implemented Chrome OS 150 to supported Chromebooks, featuring new Gemini-based classroom management tools and two enterprise policies for local PIN and password authentication.
This update also marks the final release before Chrome apps stop working in kiosk mode, according to Google’s official release notes and Chrome Unboxed coverage.
The update is primarily aimed at managed education and enterprise environments and includes a scheduled deprecation plan for legacy Chrome apps and older Chromebook Flex hardware.
The release notes also detail upcoming changes for ChromeOS 151 and 154 that will affect update eligibility and version numbering.
Gemini in Class tools and new local login policies in ChromeOS 150
The latest major update to ChromeOS 150 introduces Gemini in Class Tools, a new set of classroom management features integrated with Google Classroom.
Teachers now have the ability to restrict student devices to Gemini Guided Learning mode during class, limiting interactions with the assistant to a focused learning experience rather than open consultations.
Google explains that this integration works across all Google Classroom features. Educators can lock student screens on Gemini Notebook, formerly known as NotebookLM, for research assignments, restrict use of the device during test preparation, or prevent students from browsing beyond Google Search. These controls are accessed through the existing Class Tools interface within Google Classroom.
ChromeOS 150 also adds two new enterprise policies that enable local PIN and password authentication on managed Chromebooks. Administrators can customize complexity requirements to meet their organization’s security standards. Both policies are configured through the Google Admin Console.
Additionally, Google is automatically migrating a small group of managed business and education users who have added accounts and set up local PINs in late June 2026.
Affected users will revert to standard online password authentication when they sign in to ChromeOS 150. Google says these users will see a single informational screen upon signing in and that no local files or profile data will be affected during the migration.
Chrome apps leave kiosk mode and arrive isolated web applications
ChromeOS 150 is the final version to support legacy Chrome apps in Kiosk sessions. Starting with ChromeOS 151, Chrome apps will no longer work in kiosk mode.
Organizations that rely on kiosk mode should plan to migrate affected workflows to progressive web apps before the release of ChromeOS 151. Force-installed Chrome apps in managed guest sessions and standard user sessions will continue to work as before. This deprecation only affects kiosk sessions.
Administrators now have the option to allow users to manually install isolated web applications on managed devices. This feature is controlled by the new InsulatedWebAppUserInstallationEnabled policy, which is managed through the Google Admin console under Devices, then Chrome, then Apps & Extensions, and finally User App Settings. The policy is disabled by default and must be enabled by an administrator before users can install isolated web applications outside of the forced installation list.
Google has also improved the way ChromeOS verifies and retrieves token identifiers stored in user accounts. The update aims to reduce unexpected re-authentication messages on the login screen.
Admin checklist for deploying ChromeOS 150 to schools and businesses
IT administrators managing ChromeOS fleets in education or enterprise environments should check the following before deploying updates to their devices: Review all Kiosk sessions for Chrome apps that need to be replaced with progressive web apps before the release of ChromeOS 151.
Review the new local authentication policies in the Google Admin console to decide whether to enable local PIN or password authentication and set appropriate complexity requirements:
- Notify managed business and education users who set up local PINs by the end of June 2026 that their authentication method will revert to online passwords and that they will see a one-time informational message when they log in for the first time.
- Decide whether to enable the InsulatedWebAppUserInstallationEnabled policy, which controls user-initiated installations of isolated web applications.
- Confirm that documentation exists to implement managed guest sessions and standard user session Chrome apps, as these workflows are still supported but are potential candidates for deprecation in the future.
Teachers using Class Tools should verify that Gemini restriction options appear in Google Classroom after updating devices, as their availability depends on the version of ChromeOS installed on each student’s device.
ChromeOS 151/154: Flexible hardware limits and version number changes in the future
Google’s release notes also mention upcoming features planned for future versions. Accessibility will include an option for an inverted colored mouse cursor that will allow users to view content below a magnified pointer. The notes referenced by Chrome Unboxed did not specify a target version for this accessibility update.
Starting with ChromeOS 151, updates will be blocked on non-certified Chromebook Flex devices that use legacy graphics hardware. This includes Intel and AMD graphics from 2010 and earlier, as well as Nvidia graphics from 2014 and earlier. Devices affected by this change will remain on their current version of ChromeOS and will not receive any further updates.
Starting with ChromeOS 154, the number of versions will increase by two every four weeks. This change aligns more closely with the Chrome browser update schedule. Administrators should consider this faster release cycle when planning to track compatibility milestones for testing purposes.
Google has not announced specific release dates for ChromeOS 151 and 154. The release of ChromeOS 150 is happening gradually, so not all eligible Chromebooks will receive the update right away.
