ANAVEM
Languagefr
How to Enable or Disable Edge Startup Boost using Microsoft Intune

How to Enable or Disable Edge Startup Boost using Microsoft Intune

Configure Edge Startup Boost feature through Intune Settings Catalog policies to improve browser startup performance across your organization with proper monitoring and verification.

Evan MaelEvan Mael
March 28, 2026 12 min
mediumintune 9 steps 12 min

Why Configure Edge Startup Boost Through Microsoft Intune?

Edge Startup Boost significantly improves browser startup performance by running core Edge processes in the background when users sign into Windows. Instead of waiting for the full browser initialization when users click the Edge icon, the browser launches almost instantly because essential components are already loaded in memory.

Managing this feature through Microsoft Intune provides centralized control over browser performance across your entire organization. You can enable Startup Boost for users who need fast browser access while disabling it for devices with limited resources or specific security requirements.

How Does Edge Startup Boost Work in Enterprise Environments?

The Startup Boost feature works by launching lightweight Edge processes during Windows startup, consuming minimal system resources while dramatically reducing browser launch time. When configured via Intune Settings Catalog policies, administrators can deploy this setting at scale while preventing end users from modifying the configuration.

The policy integrates with other Edge management features and respects hardware limitations automatically. Devices with less than 4GB RAM or traditional hard drives may not benefit as much from this feature, but modern systems with SSDs see substantial performance improvements.

What Are the Benefits of Intune-Managed Edge Policies?

Using Intune to manage Edge Startup Boost ensures consistent browser performance across all managed devices while maintaining security and compliance standards. The Settings Catalog approach provides granular control over individual Edge features without requiring complex XML configurations or registry modifications.

This tutorial walks you through creating, deploying, and monitoring Edge Startup Boost policies using the current Intune interface, including verification steps and troubleshooting common deployment issues.

Implementation Guide

Full Procedure

01

Access Microsoft Intune Admin Center and Create New Policy

Start by signing into the Microsoft Intune admin center where you'll create the configuration policy for Edge Startup Boost.

Open your web browser and navigate to https://endpoint.microsoft.com. Sign in with your Intune administrator credentials.

Once logged in, navigate to Devices in the left sidebar, then select Windows > Configuration profiles. Click the Create profile button to start creating a new policy.

In the profile creation wizard, select:

  • Platform: Windows 10 and later
  • Profile type: Settings catalog

Click Create to proceed to the next step.

Pro tip: Always use descriptive naming conventions for your policies. Include the purpose, scope, and date to make management easier later.

Verification: You should now see the policy creation wizard with the "Basics" tab active.

02

Configure Policy Basics and Naming

Configure the basic information for your Edge Startup Boost policy with clear naming and description.

In the Basics tab, fill in the following information:

  • Name: Edge Startup Boost - Enable (User Scope)
  • Description: Enables Edge Startup Boost feature for improved browser startup performance. Applied to user scope for cross-device functionality.

The naming convention helps distinguish between different Edge policies and their scope. User scope policies follow users across devices, while device scope policies stay with specific machines.

Click Next to proceed to the configuration settings.

Warning: Avoid creating policies with more than 400 settings as this can cause performance degradation during policy processing.

Verification: The policy name and description should be clearly visible at the top of the wizard as you proceed.

03

Add Edge Startup Boost Settings

Now you'll add the specific Edge Startup Boost setting to your configuration policy.

In the Configuration settings tab, click + Add settings to open the settings picker.

In the search box, type Startup Boost and press Enter. You'll see the Microsoft Edge category appear.

Expand Microsoft Edge > Performance to find the Startup Boost options.

You'll see two options:

  • Enable startup boost: Device scope policy
  • Enable startup boost (User): User scope policy

Select Enable startup boost (User) for user scope deployment. Check the box next to it and click Close to add it to your policy.

In the settings list, you'll now see the "Enable startup boost (User)" setting. Click on it to configure the value.

Set the dropdown to Enabled to turn on Startup Boost, or Disabled to turn it off.

Click Next to continue.

Verification: The setting should appear in your configuration list with the correct enabled/disabled status.

04

Configure Scope Tags (Optional)

Scope tags help organize and control access to policies in large organizations. This step is optional but recommended for enterprise environments.

In the Scope tags tab, you can assign tags to control which administrators can see and modify this policy.

If your organization uses scope tags:

  • Click + Select scope tags
  • Choose the appropriate tags (e.g., "IT Department", "Pilot Group")
  • Click Select

If you don't use scope tags or want this policy visible to all Intune administrators, leave this section empty.

Click Next to proceed to assignments.

Pro tip: Use scope tags like "Pilot", "Production", or department names to organize policies and control administrative access in large organizations.

Verification: Selected scope tags (if any) should be listed in the scope tags section.

05

Assign Policy to Target Groups

Configure which users or devices will receive this Edge Startup Boost policy.

In the Assignments tab, you'll configure the target audience for your policy.

Click + Add group under "Included groups" to select your target audience.

Choose your assignment type:

  • Users: For user scope policies (recommended for Startup Boost)
  • Devices: For device scope policies

Search for and select your target groups. For initial deployment, consider:

  • A pilot group like "IT Test Users" for testing
  • Specific departments like "Sales Team" or "Marketing"
  • All users group for organization-wide deployment

If needed, you can also add exclusion groups under "Excluded groups" to prevent certain users from receiving the policy.

Click Next to continue.

Warning: Always test policies with a small pilot group before deploying organization-wide to avoid unexpected issues.

Verification: Your selected groups should appear in the "Included groups" section with the correct assignment type.

06

Review and Create the Policy

Review all policy settings before final creation and deployment.

In the Review + create tab, carefully review all the configuration details:

  • Name and description: Verify they're clear and accurate
  • Settings: Confirm "Enable startup boost (User)" is set to your desired state
  • Assignments: Check that the correct groups are targeted
  • Scope tags: Verify any organizational tags are correct

If everything looks correct, click Create to deploy the policy.

The policy will be created and begin deploying to assigned users/devices. Initial deployment can take up to 8 hours for devices to check in and receive the policy.

Verification: You should see a confirmation message that the policy was created successfully, and it will appear in your configuration profiles list.

07

Monitor Policy Deployment Status

Track the deployment progress and ensure the policy is applying successfully to target devices.

Navigate back to Devices > Windows > Configuration profiles and locate your newly created Edge Startup Boost policy.

Click on the policy name to open its details page. Here you can monitor:

  • Device and user check-in status: Shows how many devices have received the policy
  • Per-setting status: Displays success/failure rates for the Startup Boost setting
  • Error reports: Lists any devices that failed to apply the policy

To force immediate policy sync on test devices:

  1. Go to Devices > All devices
  2. Select a target device
  3. Click Sync to force policy check-in

Policy application typically occurs within 15 minutes of sync, but can take up to 8 hours for automatic check-ins.

Pro tip: Use the "Sync" feature on test devices to speed up policy validation during initial deployment and troubleshooting.

Verification: The policy status should show "Success" for devices that have received and applied the configuration.

08

Verify Edge Startup Boost Configuration on Client Devices

Confirm that the policy has been applied correctly on target devices by checking the Edge browser settings.

On a device where the policy should be applied, open Microsoft Edge and navigate to the system settings page:

edge://settings/system

Look for the "Startup boost" setting in the System section. When the policy is applied correctly:

  • The toggle will reflect your policy setting (enabled/disabled)
  • The setting will be grayed out with a policy icon, preventing user modification
  • A tooltip will indicate "This setting is managed by your organization"

You can also verify policy application through the Windows Event Viewer:

  1. Open Event Viewer
  2. Navigate to Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider
  3. Look for events related to policy application

For additional verification, check the Edge policy status page:

edge://policy

Search for "StartupBoostEnabled" to see the current policy value and source.

Verification: The Startup Boost setting should be locked to your configured value and show as managed by organization policy.

09

Test Startup Performance and Troubleshoot Issues

Validate that Edge Startup Boost is working as expected and address any common deployment issues.

To test Startup Boost functionality:

  1. Restart the target device to trigger the startup boost processes
  2. After login, wait 30 seconds for background processes to initialize
  3. Launch Microsoft Edge and note the startup time
  4. Compare with devices where Startup Boost is disabled

Check if Startup Boost processes are running:

Get-Process | Where-Object {$_.ProcessName -like "*msedge*"}

You should see Edge processes running even before manually launching the browser.

Common troubleshooting steps:

  • Policy not applying: Force device sync in Intune and wait 15 minutes
  • Setting still user-configurable: Check policy assignment and scope
  • Performance issues: Verify device meets hardware requirements (>4GB RAM or >1GB with SSD)
  • Conflicts with other policies: Review BackgroundModeEnabled policy interactions

For devices not receiving the policy:

  1. Verify the device is Azure AD joined
  2. Check Intune enrollment status
  3. Confirm user is in the assigned group
  4. Review device compliance status
Warning: If BackgroundModeEnabled policy is set to disabled, Edge may not restart properly after being closed, affecting Startup Boost functionality.

Verification: Edge should launch noticeably faster on devices with Startup Boost enabled, and background processes should be visible in Task Manager.

Frequently Asked Questions

What hardware requirements are needed for Edge Startup Boost to work effectively?+
Edge Startup Boost requires Windows 10 or later with either more than 4GB of RAM, or more than 1GB of RAM combined with modern storage (SSD or HDD supporting Trim/Seek Penalty). The feature automatically adapts to hardware capabilities, but systems with SSDs and adequate RAM see the most significant performance improvements. Devices not meeting these requirements may have the feature automatically disabled.
How long does it take for Edge Startup Boost policies to apply to target devices?+
Edge Startup Boost policies typically apply within 15 minutes when devices are manually synced through Intune. For automatic policy check-ins, it can take up to 8 hours depending on the device's check-in schedule. You can force immediate policy application by selecting target devices in the Intune admin center and clicking the 'Sync' button to trigger an immediate policy refresh.
Can users override Edge Startup Boost settings when managed by Intune policies?+
No, when Edge Startup Boost is managed through Intune policies, users cannot modify the setting. The toggle in edge://settings/system becomes grayed out with a policy icon, and users see a tooltip indicating 'This setting is managed by your organization.' This ensures consistent browser performance across all managed devices while preventing users from disabling performance optimizations.
What's the difference between user scope and device scope for Edge Startup Boost policies?+
User scope policies follow users across all their devices, meaning the Startup Boost setting applies regardless of which managed device they sign into. Device scope policies stay with specific machines, affecting all users who sign into that particular device. User scope is typically preferred for Edge Startup Boost as it provides consistent browser performance for users across their work devices.
How does Edge Startup Boost interact with other Edge policies like BackgroundModeEnabled?+
Edge Startup Boost works in conjunction with the BackgroundModeEnabled policy. If BackgroundModeEnabled is set to disabled, Edge may not restart properly after being completely closed, which can affect Startup Boost functionality. For optimal performance, ensure BackgroundModeEnabled is either enabled or not configured when deploying Startup Boost policies. Both policies can be managed through the same Intune Settings Catalog configuration profile.
Evan Mael
Written by

Evan Mael

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

Sign in to join the discussion