In enterprise and managed education environments, standardising web browser startup behaviour and default home pages ensures that employees and students instantly access core intranet portals, productivity suites, and single sign-on landing pages upon launching Microsoft Edge. Rather than manually configuring settings through the user interface or relying solely on complex Active Directory Group Policy Objects (GPOs), IT administrators and systems engineers can enforce browser startup policies directly through Windows PowerShell. By writing to the managed enterprise policy registry hive for Microsoft Edge (HKLM:\SOFTWARE\Policies\Microsoft\Edge), administrators can enforce non-overridable startup URLs, lock down homepage settings, or restore prior browsing sessions deterministically across Windows 11.
Architecture of Microsoft Edge Enterprise Startup Policies
Microsoft Edge Chromium evaluates startup behaviour via several interconnected policy keys residing within the Windows Registry:
- RestoreOnStartup: An integer flag determining what happens when the browser launches. Supported values are:
1: Open the New Tab page.4: Open a specific set of URLs defined inRestoreOnStartupURLs.5: Restore the previous session (reopen tabs from the previous browsing session).
- RestoreOnStartupURLs: A string list specifying mandatory landing pages that open automatically when Edge starts.
- HomepageLocation: A string defining the destination opened when the user clicks the Home toolbar button.
- HomepageIsNewTabPage: A boolean flag dictating whether the Home button navigates to the New Tab page or the custom URL defined in
HomepageLocation. - ShowHomeButton: Enables or hides the Home button on the primary navigation toolbar.
Auditing Existing Edge Registry Policies in PowerShell
To inspect whether any administrative Edge policies are currently active on Windows 11, open Windows PowerShell as an Administrator and query the policy registry keys:
# Query Edge machine policies
Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -ErrorAction SilentlyContinue
# Query Edge user policies
Get-ItemProperty -Path "HKCU:\Software\Policies\Microsoft\Edge" -ErrorAction SilentlyContinue
If the Edge key does not exist yet under HKLM:\SOFTWARE\Policies\Microsoft, PowerShell can create it prior to deploying settings.
Enforcing Mandatory Startup URLs via PowerShell
To configure Microsoft Edge so that it always opens a specific set of company portal URLs upon launch, create the policy container and populate the startup list.
# Define the registry policy base path
$EdgePolicyPath = "HKLM:\SOFTWARE\Policies\Microsoft\Edge"
# Ensure the policy directory exists
If (-not (Test-Path -Path $EdgePolicyPath)) {
New-Item -Path $EdgePolicyPath -Force | Out-Null
}
# Set RestoreOnStartup to 4 (Open specific URLs)
Set-ItemProperty -Path $EdgePolicyPath -Name "RestoreOnStartup" -Value 4 -Type DWord
# Define mandatory startup URLs subkey
$StartupUrlsPath = "$EdgePolicyPath\RestoreOnStartupURLs"
If (-not (Test-Path -Path $StartupUrlsPath)) {
New-Item -Path $StartupUrlsPath -Force | Out-Null
}
# Populate startup URL list (1-indexed string entries)
Set-ItemProperty -Path $StartupUrlsPath -Name "1" -Value "https://portal.office.com" -Type String
Set-ItemProperty -Path $StartupUrlsPath -Name "2" -Value "https://intranet.company.co.uk" -Type String
When Edge starts, both the Office portal and corporate intranet will open automatically in separate browser tabs.
Configuring the Home Button and Homepage URL
Next, configure the Home button so that clicking it navigates directly to your designated intranet dashboard rather than a search engine or generic new tab.
# Enable the Home button on the navigation toolbar
Set-ItemProperty -Path $EdgePolicyPath -Name "ShowHomeButton" -Value 1 -Type DWord
# Direct the Home button to a specific URL rather than the New Tab page
Set-ItemProperty -Path $EdgePolicyPath -Name "HomepageIsNewTabPage" -Value 0 -Type DWord
# Specify the designated Homepage location
Set-ItemProperty -Path $EdgePolicyPath -Name "HomepageLocation" -Value "https://intranet.company.co.uk" -Type String
Configuring Edge to Restore Previous Session Tabs
In developer or technical workstations, users often prefer Edge to restore previously opened tabs across restarts to preserve active documentation and staging consoles. To enforce session restoration via PowerShell:
# Set RestoreOnStartup to 5 (Restore last session)
Set-ItemProperty -Path $EdgePolicyPath -Name "RestoreOnStartup" -Value 5 -Type DWord
# Remove conflicting startup URL entries if previously configured
If (Test-Path -Path "$EdgePolicyPath\RestoreOnStartupURLs") {
Remove-Item -Path "$EdgePolicyPath\RestoreOnStartupURLs" -Recurse -Force
}
Verifying Enforced Policies in Microsoft Edge
To confirm that Microsoft Edge has ingested the newly written registry policies without restarting the operating system:
- Launch Microsoft Edge.
- In the address bar, navigate to
edge://policy. - Click the Reload policies button in the top banner.
- Examine the policy table:
RestoreOnStartup,RestoreOnStartupURLs, andHomepageLocationwill be listed with Mandatory enforcement and OK status. - Navigate to
edge://settings/startHomeNTPto verify that the startup settings display a managed briefcase icon indicating enterprise administrative enforcement.
Removing Policies and Restoring User Control
To decommission enforced startup policies and return full configuration control back to the end user:
# Remove specific startup and home policy values
Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -Name "RestoreOnStartup" -ErrorAction SilentlyContinue
Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -Name "HomepageLocation" -ErrorAction SilentlyContinue
Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -Name "HomepageIsNewTabPage" -ErrorAction SilentlyContinue
Remove-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge\RestoreOnStartupURLs" -Recurse -ErrorAction SilentlyContinue
Automating Microsoft Edge startup and homepage configurations via PowerShell allows systems administrators to deliver seamless, uniform navigation across fleet deployments in Windows 11.