Known issues

Here are some known issues with Chrome. If available, we list a workaround to help troubleshoot the issue.

Open all   |   Close all

ChromeOS devices

Network issues when setting up ChromeOS devices

Known issue

The network connection is not working properly during the initial setup of some ChromeOS devices.

Workaround

Option 1—Troubleshoot in guest mode.

Test the following steps with WLAN or LAN.

1. Connect to the internet using LAN or Wi-Fi.
   A network error is displayed.

2. Click Troubleshoot in guest mode.

3. In the Status bar, go to Settings.

4. Click About ChromeOS.

5. Click Search for updates.

6. Restart the device.

Option 2—Create a recovery stick.

To do this, you need a device with Chrome browser installed.

1. Connect the USB stick, 8 GB minimum, to a device.

2. Open Chrome browser.

3. Search for Chrome Web Store and open it.

4. In the search bar, enter Chromebook Recovery Program and install it.

5. Select the affected device from the manufacturer.
   The recovery stick is created.
   Important: It is essential to select the affected device as there is currently no
   universal variant available.

6. When the process is complete you can remove the stick.

The ChromeOS device starts up automatically with the latest version.

Option 3—Manual update with the console.

This is without developer mode, such as, Lenovo Duet, Asus CZ1, or HP x360 14B.

Test the following steps with WLAN or LAN.

1. Connect to the internet using LAN or Wi-Fi.
   A network error is displayed.

2. Click Troubleshoot in guest mode.

3. Enter CTRL + ALT + T to open an input mask.

4. Enter autest and click Enter.

5. In the Status bar, go to Settings.

6. Click About ChromeOS.
   Update is being downloaded should be displayed. If not, try with developer mode as detailed in option 4.

7. Restart the device.

Option 4—Update with the developer mode.

This is with developer mode, such as, ASUS CX1400 or Asus C523.

1. Click Esc + Refresh + Power and then click Ctrl + D to activate developer mode.
   The operating system check must remain deactivated.

2. Click ESC to exit.

3. Connect to the internet using LAN or Wi-Fi.
   A network error is displayed.

4. Click Troubleshoot in guest mode.

5. Enter CTRL + ALT + T to open an input mask.

6. Enter shell and confirm.

7. Enter update_engine_client --channel=beta-channel -update and confirm.
   Important: This code must be entered exactly as displayed above. There are spaces in the code that must be included.

8. In the Status bar in the lower right corner, go to Settings.

9. Click About ChromeOS.
   Update is being downloaded should be displayed.

10. Restart the device.

Last updated: Jan 25, 2023

ChromeOS file manager—Failure to move items into a shared drive

Known issue

Moving items into a shared drive that is at or above the storage limit will fail without notification.

Last updated: Jan 23, 2023

Playback issues on some websites that use protected content

Known issue

Some users with ChromeOS version 89 or earlier might experience issues playing protected video or audio content on some websites.

Workaround

Option 1—Update to ChromeOS version 90 or later.

Option 2—For users with ChromeOS version 89 or earlier who cannot upgrade to 90 or later, use a corresponding Android app to play back content.

Last updated: August 3, 2021

“Your Chromebook is locked due to a known issue” error message

Known issue

Some users can’t sign in to their Chromebook. The error message on the screen includes a countdown timer showing the length of time that users need to wait before they can sign in. During this time, users need to keep their Chromebooks powered on and connected to power. Users should not turn off their Chromebooks.

Workaround

Option 1—Reset Chromebook to factory settings immediately

If users can’t wait the specified amount of time, they can reset their device to factory settings. Resetting erases all the information on the device’s hard drive, including all the files in the Downloads folder. For information about how to factory reset a Chromebook, go to Reset your Chromebook to factory settings.

After users factory reset the device, make sure that the Chromebook's OS has been updated to the latest version. For details, see Update your Chromebook's operating system.

Option 2—Save files by first keeping Chromebook awake for 48 hours

Some users might have files that they need in their Downloads folder that are not backed up to Google Drive or an external storage device.

On Chromebooks that are showing the error message:

1. Make sure that charger or adapter cables are fully plugged into the Chromebook and the power outlet.
2. Sign in as a guest.
3. Update the Chromebook’s settings so that it stays awake:
   1. At the bottom right, select the time.
   2. Select SettingsDevice.
   3. Click Power.
   4. Under When idle, for While charging and While on battery, choose Keep display on.
   5. Turn off Sleep when cover is closed.
4. Keep the device awake with the lid open for 48 hours. Don't turn it off.
5. After 48 hours, exit guest mode.
6. Sign in using your Google Account.
7. Back up each file that’s needed. For details, see Open, save, or delete files.
8. Factory reset the Chromebook.
9. Make sure that the Chromebook's OS has been updated to the latest version. For details, see Update your Chromebook's operating system.

Last updated: September 30, 2020

Can't unlock device with fingerprint sensor

Known issue

Users can't use their fingerprint to unlock devices.

Workaround

In your Google Admin console, make sure that Fingerprint is selected for the Quick unlock setting on the User & browser settings page. For details, see Set chrome policies for users or browsers.

Last updated: June 18, 2020

"A registration certificate could not be obtained" error message

Known issue

You will see this error message when forced re-enrollment is enabled on a ChromeOS device. This error occurs when auto re-enrollment fails because the device is connected to a network with TLS or SSL inspection that does not have the hostname chromeos-ca.gstatic.com added to an allowlist.

Workaround

Users can switch to the manual re-enrollment screen by clicking X in the top-right corner of the error screen. Or, the administrator can add the hostname chromeos-ca.gstatic.com to an allowlist on the proxy server to allow ChromeOS devices to automatically re-enroll.

Some Chromebook batteries don't recharge after prolonged storage

Known issue

Lithium ion batteries typically drain slowly when left uncharged for long periods of time, such as during school breaks. The Chromebook models below may discharge so deeply during storage that it affects the battery’s ability to be recharged:

• CTL J2 / J4 Chrome for education device
• CDI eduGear Chromebook K Series
• HiSense Chromebook 11
• Poin2 Chromebook 11

Workaround

For instructions on how to store these devices for a long time, see Storing Chromebooks long term.

Limitation on number of saved hidden SSID networks a ChromeOS device can scan and connect to

Known issue

The number of manually saved and managed hidden SSID networks that a ChromeOS device can scan and connect to is limited by what the WLAN chipset supports, which can vary between device models.

This can be verified on a device in dev mode with the following command:

$ /usr/sbin/iw phy | grep -i ssid

As an example, entering this command on an Acer Chromebook C720 would result in the following:

$ /usr/sbin/iw phy | grep -i ssid
        max # scan SSIDs: 4

In this example with an C720 gives us the answer 4. One is consumed by the scan, so it is advised to have a maximum of three hidden SSID networks saved on the device, either by managed network policy or manually added.

Workaround

We encourage admins not to use hidden SSID on their access points.

Important: Please tag these cases with crbug.com/577993 - "FR: Support for more hidden SSIDs than the hardware supports".

Kiosk

Customized kiosk app policies do not apply

Known issue

Your app policies are not applied after adding a new kiosk app.

Workaround

Select the app from the Auto-launch Kiosk App list in the Kiosk settings.

Chrome Enterprise

Drive files suggestions in Chrome only available to Google Workspace Enterprise Plus users

Known issue

Only users who are assigned the Google Workspace Enterprise Edition license can use the Drive file suggestion feature in Google Chrome with all the available search options.

Workaround

Users with other types of licenses can search in Drive using the search box on drive.google.com. For details, see Find files in Google Drive.

Users need to enter CAPTCHA challenge for Search

Known issue

This issue can occur if your organization routes all search requests through a single IP using a proxy. Google Search might detect these requests as potential spam and abuse, which triggers a CAPTCHA challenge.

Workaround

• If you use the DefaultSearchProviderSuggestURL policy, change the URL to {google:baseURL}complete/search?output=chrome&q={searchTerms}.
• Run a malware check on your network.
• Stop users from using Hola VPN.

Related topics

• Unusual traffic from your computer network
• What is CAPTCHA?

Device management

Can't re-enable a disabled ChromeOS device

Known issue

If you have tried to enable a ChromeOS device, but the device stays stuck in disabled mode, check the serial number.

To find and check the serial number:

1. Turn on the device.

2. Before signing in, press Alt+V.

3. Compare the serial number you see on the screen to the serial number printed on the device. Some refurbished or otherwise modified devices might have incorrect serial number stickers.

4. If the serial numbers don’t match, the printed number is incorrect. If you use the printed number in the enable command, the command will fail.

Workaround

We recommend that you ask the manufacturer to replace the device. If you continue to use the device, use the serial number found on the screen (not on the device’s sticker) to manage the device.

For more details, see View ChromeOS device information.

Changes not recorded in admin audit log

Known issue

Currently, changes to ChromeOS devices using the Directory API and third party tools are not recorded in admin audit logs.