Configure the Autopilot Enrollment Status Page to Block Desktop Use Until Required Apps Install
Hold Autopilot devices on the ESP until required apps install: set Block device use, pick Selected blocking apps, check InstallationState and back out safely.

This playbook covers
Advertising disclosure: this article includes partner links. KBY may earn a commission if you sign up or buy through one, at no extra cost to you. How we make money.
Table of Contents
Table of contents
To stop a Windows AutopilotThe KBY LexiconWindows AutopilotWindows Autopilot registers device hardware identity to a tenant so new or reset Windows devices self-configure via Entra ID join and Intune policy during first boot.
device reaching the desktop before its essential software is in place, create a device-targeted Enrollment Status Page (ESP) profile in the Microsoft IntuneThe KBY LexiconMicrosoft IntuneMicrosoft Intune is Microsoft's cloud-based unified endpoint management service for enrolling, configuring, securing and retiring Windows, macOS, iOS and Android devices.
admin center, set Block device use until all apps and profiles are installed to Yes, and set Block device use until these required apps are installed if they are assigned to the user/device to Selected with a short list of blocking apps. Those apps must be required-assigned to a group that contains the device and must install in device context, or the ESP never tracks them. The constraint to plan for is time: the default time-out is 60 minutes, and every blocking app has to finish inside it. Prove the result on a pilot device by reading the Locked and InstallationState values under HKLM\SOFTWARE\Microsoft\Windows\Autopilot\EnrollmentStatusTracking, and keep a pilot-only assignment until the time-outs stop.
#How the setup page is usually handled today
The quick set-up is to run Autopilot on the Default ESP profile, or on one profile assigned to every device that blocks on All required apps. Both work until the app catalogue grows. With All, every required app assigned to the device or user becomes a reason to hold the device, so a slow or broken installer for a minor tool keeps a new starter from reaching the desktop. Without a custom message, the user sees the generic “Setup could not be completed. Please try again or contact your support person for help.” and the service desk has no quick way to tell which app held the page.
The opposite habit causes a different ticket. Profiles with Block device use set to No let users leave the ESP before Intune has finished, so the endpoint protection agent or VPN client may still be installing when the user opens Outlook. The gap may only show up later, in a compliance report or a missing drive mapping.
Neither approach tells anyone why a device was held. The ESP does record what it tracked in the device registry, and the workflow below uses that record on purpose.
#A better way: one device profile and a short blocking list
The improved workflow separates two questions that the All setting merges: which apps must exist before anyone uses the device, and which apps simply need to arrive eventually. The first group goes in the ESP’s Selected list. Everything else stays a required assignment and installs in the background.
The selected list is a filter, not a deployment. Intune only waits for apps that are both in the list and assigned to the device or user. If the list holds App 1, App 2 and App 3, and only App 3 and App 4 are assigned, the ESP tracks App 3 alone. In user-driven and self-deploying mode, an unlisted Win32, Microsoft Store or Enterprise app catalog app such as App 4 installs after the ESP completes, which is exactly the behaviour you want for non-essential software.
Target the profile at devices rather than users. Intune applies the highest-priority profile assigned to the device first, falls back to the highest-priority user profile only when there is a user, and uses the Default profile when nothing else matches. Pre-provisioning and self-deploying deployments only ever read device-targeted profiles, so a device profile is the one that applies in every Autopilot mode. Profile priority 1 is the highest.
Rendering diagram...
The trade-off is honest delay. A held device costs the user time at first sign-in, so the list should contain only what the device is unsafe or useless without: typically the security agent, the network access client and any app another blocking app depends on. Microsoft allows up to 100 apps in the list, but every entry adds install time against the same time-out.
#Setting up the profile step by step
Before you start, confirm three things. You can create ESP profiles in Intune (a tenant holds at most 51, the Default plus 50). You have a pilot device group of Autopilot-registered devices; a group tag and dynamic device group, as described in routing Autopilot profiles with group tags and dynamic device groups, makes this easy to scope. And the pilot users hold an Intune licence, because the ESP can sit in the Identifying state indefinitely when the signing-in user has none.
- Prepare each blocking app. Package it as a Win32 app, assign it as Required to the pilot device group and install it in device context with no user-context applicability rules. Do not mix line-of-business MSI apps with Win32 apps during Autopilot: both use TrustedInstaller, so the Win32 install fails with “Another installation is in progress, please try again later” and the ESP fails. Deploy Microsoft 365The KBY LexiconMicrosoft 365Microsoft 365 is Microsoft's subscription suite of Office apps and cloud services such as Exchange Online, SharePoint, OneDrive and Teams, run on an Entra ID tenant. Apps as a Win32 app too: Microsoft documents ESP hangs when the Microsoft 365 Apps app type starts installing while another tracked Win32 app is installing.
- Move restarts into Intune. Reboots packaged inside an installer can hang the ESP. In each app’s program settings, set Device restart behavior to Determine behavior based on return codes and map the installer’s codes to Hard reboot, Soft reboot, Retry, Failed or Success. Restarts are supported in the device setup phase only, not account setup.
- Create the profile. Go to Devices > Device onboarding > Enrollment, open the Windows tab, select Enrollment Status Page under Windows Autopilot, then Create. Name it for its purpose, for example “ESP – blocking core apps – pilot”.
- Configure the settings. Set Show app and profile configuration progress to Yes. Raise Show an error when installation takes longer than specified number of minutes from 60 only if your pilot timings show you need it; on Microsoft Entra hybrid join deployments, expect the ESP to run 40 minutes beyond the value you set. Turn on the custom message with the service desk contact, and turn on Turn on log collection and diagnostics page for end users (the diagnostics page appears on Windows 11). Set Block device use until all apps and profiles are installed to Yes, choose Selected for the required apps setting, then Select apps and add only the blocking apps.
- Decide the error options. Allow users to reset device if installation error occurs gives a clean retry. Allow users to use device if installation error occurs lets the user bypass the failure, which defeats the purpose when the blocking apps are security controls, so leave it at No for those and rely on the custom message.
- Check the quality update setting. Install Windows quality updates (might restart the device) defaults to Yes on new profiles. It adds 20 to 40 minutes after the ESP completes, may restart without signing the user back in, and can break autologon provisioning. Set it deliberately rather than inheriting the default.
- Assign and prioritise. Assign the profile to the pilot device group. Assignment filters are limited to the model, manufacturer, osVersion, operatingSystemSKU, deviceOwnership and enrollmentProfileName properties. On the profile list, drag the new profile above any broader device profile so it wins for pilot devices.
Stop before widening the assignment if any pilot device times out, if an app reports error state 4, or if the ESP shows Identifying for longer than the time-out. Each of those is a packaging or licensing fault that a bigger group will only repeat.

#Limits and who can change the profile
An ESP profile decides whether every device in its groups can be used at all, so treat changes to it like a change to a security baseline. Use scope tags so that only the endpoint team can see and reprioritise ESP profiles; a scoped administrator can still see the relative priority of their own profile. Keep the blocking list under change control, because adding one slow app raises the install time for every device the profile covers.
Know what the page does not cover. The ESP does not track device restriction and similar security policies, which install in the background, and it does not wait for PowerShell scripts to finish. If a blocking app needs a script to run first, build that prerequisite into the Win32 app itself rather than relying on the Intune Management Extension running scripts before apps.
#Prove the device was held on a pilot
Run a user-driven Autopilot deployment on one pilot device and watch the device setup phase list the blocking apps. To read the tracking state, press Shift+F10 during OOBE on a non-S mode device and query the ESP’s Win32 tracking keys:
1reg query "HKLM\SOFTWARE\Microsoft\Windows\Autopilot\EnrollmentStatusTracking\Device\Setup\Apps" /v Locked
2reg query "HKLM\SOFTWARE\Microsoft\Windows\Autopilot\EnrollmentStatusTracking\Device\Setup\Apps\Tracking\Sidecar" /sThe Locked value shows whether device use is blocked until device setup completes. Under each Win32App_{AppID} subkey, InstallationState reads 1 (NotInstalled), 2 (InProgress), 3 (Completed) or 4 (Error). A passing pilot shows every blocking app at 3 before the desktop appears. If any app shows 4, the ESP stops installing apps; read the Intune Management Extension log for the cause.
For a complete record, collect the diagnostics package from the same command prompt and keep it with the pilot notes:
1mdmdiagnosticstool.exe -area Autopilot -cab C:\Temp\esp-pilot.cabThe output path can be any folder that exists on the device.
Use -area Autopilot;TPM instead for self-deploying and pre-provisioned devices. The cab’s MDMDiagReport_RegistryDump.Reg holds the ESP settings the device received under HKLM\SOFTWARE\Microsoft\Enrollments\{EnrollmentGUID}\FirstSync, which confirms the right profile arrived. On an admin workstation, Install-Script -Name Get-AutopilotDiagnostics -Force followed by Get-AutopilotDiagnostics -CABFile C:\Temp\esp-pilot.cab summarises the same logs; remove it afterwards with Uninstall-Script -Name Get-AutopilotDiagnostics.
#Where it goes wrong
- The time-out fires on every device. The usual cause is a time-out too short for the number of blocking apps. Time each blocking app during the pilot runs, then either shorten the list or raise the time-out, not both at once.
- An app you listed is never tracked. It is assigned as available rather than required, assigned to a group that does not contain the device, or installs in user context. Fix the assignment rather than switching the profile to All.
- The ESP hangs after an app installs. The installer restarted the device itself. Move the restart into the app’s return codes.
- The wrong profile applies. A higher-priority device profile also covers the device. Compare the FirstSync settings in the diagnostics cab with the profile you expected, and reorder priorities. If the device never received an Autopilot profile at all, work through why an Autopilot device shows profile not assigned first.
- Enrolment is refused before the ESP appears. That failure happens before the device has enrolled and read any ESP profile; error 0x80180014 and blocked Windows MDM enrolment covers that case.

#Backing out a profile that blocks enrolment
Before you change a profile that is already in production, record its settings, blocking list, assignments and priority position by hand, so you have a known state to return to. Then back out in the smallest step that stops the harm:
- Remove the pilot group from the new profile’s assignment, or drag the profile below the profile you were using before. New enrolments then receive the next profile in priority order, or the Default profile.
- For a device already stuck on the page, collect logs first, then use the reset option if the profile allows it (the device has not yet reached the desktop), and re-run the deployment once the assignment change is in place.
- Do not expect disabling the profile to help devices that already have it. ESP policy is set at enrolment, and a disabled profile is not removed from devices; users still see the ESP at their first sign-in.
- If enrolled devices must stop showing the user part of the page, Microsoft documents a custom OMA-URI,
./Vendor/MSFT/DMClient/Provider/MS DM Server/FirstSyncStatus/SkipUserStatusPage, Boolean,True. Try it on one test device first and treat it as an escalation step, because the documentation does not describe how to reverse it.
After backing out, enrol one pilot device again and confirm the FirstSync settings in its diagnostics cab match the profile you meant to apply.
#What to track after rollout
Take a baseline from the pilot: the number of deployments, how many ended at the desktop with every blocking app at state 3, how many hit the time-out, and the longest time a blocking app took. Collect the same figures weekly from the service desk’s ESP failure tickets and the diagnostics cabs users submit. The profile is working when time-outs come from identifiable apps rather than unknown causes, and when no device reaches the desktop without its blocking apps. Review the blocking list whenever an app is added to it or its installer changes, and treat any repeat time-out for the same app as a reason to pull that app from the list until its package is fixed. If your Autopilot build turns on BitLocker, the script that lists Windows devices with no BitLocker recovery key in Entra ID is a useful second check that new devices escrowed their keys after each wave.
#Before you go live with the blocking profile
- Every blocking app is a Win32 app, required-assigned to a device group, installing in device context.
- No blocking app restarts the device itself; restarts come from return codes.
- No line-of-business MSI apps are assigned alongside the Win32 apps during Autopilot.
- The time-out covers the slowest pilot run; on hybrid join the ESP adds its own 40 minutes on top.
- The custom error message names the service desk, and log collection is on.
- Install Windows quality updates is set on purpose, not left at the default.
- The profile’s priority beats any broader device profile for the target group.
- The previous profile’s settings and priority are recorded so you can back out.
- Pilot users are licensed for Intune, and at least one pilot run per Autopilot mode you use has passed.
About this page
Credited to
Dates
Published
Sources
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Read-only scripts
- Windows devices with no BitLocker recovery key in Entra IDMicrosoft Entra ID, Windows
- Intune devices that haven't synced in N daysMicrosoft Intune
- Mailboxes forwarding to external addressesExchange Online
- BitLocker status of every volume on this PCWindows
Upcoming deadlines
- Intune moves to macOS 15 and laterQ4 2026
- SAP SuccessFactors provisioning: move from basic auth to workload identityNovember 2026
- Intune November release: JIT registration reminder at APNs renewal and automatic JIT for eligible tenantsNovember 2026
Explore KBY
The KBY Brief
A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.
SubscribeRelated articles
Zero-Touch & Automation
Autopilot Device Shows Profile Not Assigned: Find the Cause
Imported Autopilot device showing no deployment profile? Check group membership and profile assignment, fix one cause and confirm before shipping.
Enterprise IT Management
Part 2: Register Devices in Windows Autopilot: Import Hardware Hashes into Intune
Capture a pilot laptop's hardware hash with Get-WindowsAutopilotInfo, tag it AP-Pilot, import the CSV into Intune, and leave the Entra device object that registration creates alone.
Outages
Apple Fixes Outage That Signed iPhone and Mac Users Out of iCloud and Took Down the App Store
Apple says it has resolved Tuesday's outage, which signed users out of iCloud and hit the App Store, Apple Music and Apple Pay, and blames an internal update. What to check now it is back.
Discover more
Graduate Learning
Ops Playbook
- PlaybookRun Intune Remediations On Demand to Fix One Windows Device Without Waiting
- PlaybookRoute Windows Autopilot Profiles With Group Tags and Dynamic Device Groups
- PlaybookIntune Endpoint Analytics Devices Missing Startup Performance Scores
- PlaybookIntune Remediation Script Shows Without Issues but Never Runs
Lexicon Definitions
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Operate smarter, with fewer recurring tickets.
Receive new operational playbooks, incident-prevention guidance, automation scripts and recovery runbooks.
Comments
Add a thoughtful note on Configure the Autopilot Enrollment Status Page to Block Desktop Use Until Required Apps Install. Comments are checked for spam and held for moderation before appearing.