com.sec.android.app.SecSetupWizard Copy

Labelled "Samsung setup wizard" on the device, this is Samsung's own out-of-box experience on Galaxy hardware. It is made by Samsung and signed by a Samsung OEM key that also signs the Android framework, so it is a platform-signed system component; it has no Play listing and no launcher entry in our sample. It sits alongside Google's com.google.android.setupwizard, documented separately on this site, rather than replacing it: the permissions recorded for it here include com.google.android.setupwizard.SETUP_COMPAT_SERVICE, together with MANAGE_ROLE_HOLDERS, INVOKE_CARRIER_SETUP and its own com.sec.android.app.SecSetupWizard.permission.SHOW_SETUP_WIZARD, which is consistent with it driving first-boot screens and handing off to the Google setup flow. It also declares Samsung account, Samsung Cloud and Kids Home permissions, matching the Samsung-specific steps a Galaxy device shows during setup. For Android Enterprise, EMM and kiosk work the important point is that Samsung documents this exact package as something you can block, and warns what happens if you block it at the wrong moment. Knox KBA-1273 tells administrators to disable com.sec.android.app.SecSetupWizard before updating to One UI 6 in order to suppress the One UI 6 welcome screen that otherwise appears after the update, applying the block through an EMM app-restriction policy. The same article is explicit that this is only a workaround for devices that have already been set up: on a new device, disabling it results in a device enrolment failure with an "Action Not Allowed" error. Samsung also notes that fully managed devices running One UI 6.1.1 or higher do not show the welcome screen at all, so the workaround is unnecessary there. Treat it as a package to leave alone during provisioning and to touch only with a specific, tested reason afterwards. Version note: the role of this package is version-sensitive on two counts. The welcome-screen behaviour above changed with One UI 6 and again by One UI 6.1.1, per the Knox article. Separately, Samsung documents an optimised setup wizard for Android Enterprise Recommended devices, on the basis that collecting diagnostic data and sending marketing information is not appropriate on a managed device: the user is still shown the consent options during setup, and where the corresponding data collection is disallowed the agreement is withdrawn by policy afterwards and the user is told so, with the settings then reachable from the device's privacy menu. Samsung does not state Android or Knox version requirements for that AER behaviour, so we cannot pin it to a release. The builds observed in this database run from 4.1.44.1 to 9.0.23.1 with target SDKs from 30 to 36, so it has been seen across several Android and One UI generations.

• KBA-1273: Disable One UI 6 welcome screen - Knox Platform for Enterprise, Samsung Knox Documentation →
• Optimized Setup Wizard for AER (Android Enterprise Recommended) - Knox SDK, Samsung Knox Documentation →
• Provision for device management - Android Open Source Project →
• Package provenance for com.sec.android.app.SecSetupWizard - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, but 2 different certificates appear across the fleet, so OEMs ship their own builds of it. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on Samsung devices (493 packages, 7791 observations).
• Its largest observed manifest declares 27 permissions: 4 signature or system-level, 5 install-time and 18 vendor or uncatalogued.
• APK size ranges from 5.4 MB to 12.9 MB across the reporting device profiles, so the build differs substantially between them.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.