Skip to main content

Category filter

Clear Password command queued on Android due to Direct Boot mode

TL;DR

On Android devices, the Clear Password command can remain queued after a restart if the device is still in Direct Boot mode. Ask the user to unlock the device once after boot, keep the device connected to a network that works before first unlock, and then run Actions > Scanning & Monitoring > Scan Device from the Hexnode console. Device Wipe may still work in this state because it does not require access to credential-encrypted user storage.

Executive Summary

Android enters Direct Boot mode after a restart and stays in that state until the user unlocks the device for the first time. While in Direct Boot mode, Credential-Encrypted Storage remains locked. The Hexnode UEM agent may need access to this storage to modify or clear the lock screen password, so the Clear Password command can remain queued even when the device appears to be checking in. A Device Wipe command can still execute because it is a lower-level system command that does not need to read or modify encrypted user credentials.

To process the pending password command without wiping or re-enrolling the device, perform a first unlock, verify direct network access, and manually sync the device from the Hexnode UEM console.

Why Clear Password can remain queued on Android

When an Android device restarts, it enters Direct Boot mode until the screen is unlocked for the first time. During this state:

  • Credential-Encrypted Storage is locked: User-specific credentials and cryptographic keys remain encrypted and unavailable.
  • Password changes may queue: The Hexnode UEM agent may be unable to modify or clear the lock screen password until the encrypted storage becomes available.
  • Device Wipe can still run: A factory reset does not need to access user-specific encrypted data. It wipes the storage block, so it can complete even when Clear Password remains queued.

Resolve a queued Clear Password command without wiping the device

  1. Perform a first unlock. Ask the user to enter the device passcode once after the device boots. This unlocks credential-encrypted storage and allows the Hexnode UEM agent to process pending password actions.
  2. Ensure direct network access. Keep the device connected through cellular data or a basic pre-shared Wi-Fi network. During Direct Boot, the device may not connect to Wi-Fi networks that require enterprise certificates or user credentials.
  3. Force a manual sync. After the device is unlocked and connected, go to Actions > Scanning & Monitoring > Scan Device in the Hexnode UEM console to push pending queued actions to the device.

Troubleshooting queued password commands

The device was restarted recently

If the device restarted and has not been unlocked since boot, it may still be in Direct Boot mode. Perform the first unlock before expecting the Clear Password command to run.

The device is online but the command does not apply

The device may be checking in but still unable to process commands that require access to Credential-Encrypted Storage. Unlock the device once and then use Actions > Scanning & Monitoring > Scan Devicee.

The device cannot connect to its usual Wi-Fi before first unlock

Some Wi-Fi networks require enterprise certificates or user credentials that may not be available during Direct Boot. Use cellular data or a basic pre-shared Wi-Fi network until the device is unlocked and synced.

Note:


If an updated file uses an unsupported format, it will be removed from the following associated policies:

  • Device Wipe succeeding does not necessarily mean Clear Password should also succeed in the same device state. The two actions rely on different Android capabilities.
  • A wipe or re-enrollment is not required for this Direct Boot scenario if the device can be unlocked once and synced.
  • If the user cannot unlock the device at all, the confirmed remediation in this scenario does not apply because the first unlock cannot be completed.

Frequently Asked Questions

Why did Device Wipe work while Clear Password stayed queued?

Device Wipe is a lower-level system command that can reset the device without reading or modifying credential-encrypted user data. Clear Password may require access to storage that remains locked during Android Direct Boot mode.

What is the first unlock on Android?

The first unlock is the first time a user enters the device passcode after the device boots. This decrypts Credential-Encrypted Storage and allows queued actions that depend on that storage to proceed.

Should the device be wiped when Clear Password is queued?

Not for the Direct Boot behavior described here. First unlock the device, confirm network access, and run Actions > Sync Device from the Hexnode UEM console.

Which network should be used before the first unlock?

Use cellular data or a basic pre-shared Wi-Fi network where possible. Networks that require enterprise certificates or user credentials may not be available during Direct Boot.

Troubleshooting Guides