Device enrolled in Knox Configure not booting correctly

Environment

• Knox Configure

Overview

Some customers are reporting that their Knox Configure (KC)-enrolled device is either not booting, or booting in safe mode.

Cause

This boot issue typically occurs because critical system apps are blocklisted in your KC profile. These apps are required for the device to function correctly.

A common cause is including the package com.android.settings in your blocklist. If you want to restrict Settings access for your users, see Restrictions > Prevent end users from accessing the settings menu in the KC admin guide for the proper steps.

Resolution

Please check your specified blocklist in the profile the device is enrolled in. For steps on how to do this, see Applications & content in the KC admin guide.

If you identify that a system app is causing the issue, please remove the package from the blocklist and factory reset any affected devices to apply the change.