Microsoft recently rolled out Edge version 135, packed with new features and enhancements aimed at improving user experience and security. However, the update has hit a roadblock for many users, particularly in enterprise environments, where the browser’s First-Run Experience (FRE) fails to load, displaying an “ERR_INVALID_URL” error. Usually, when users launch Microsoft Edge 135 for the first time after the update, they’re greeted by a welcome page designed to guide them through account setup and browser configuration. However, for many, the page fails to load, showing an “ERR_INVALID_URL” error on the edge://welcome-new-device page that can’t be dismissed easily. Here’s a closer look at the update’s highlights, the issue plaguing it, and how users can navigate the glitch.
Contents
What’s New in Microsoft Edge 135
Edge 135 introduces several improvements designed to make browsing smoother and more secure. Key additions include:
- Enhanced Tab Grouping: A revamped tab management system that lets users collapse, color-code, and pin tab groups for better organization, ideal for multitasking professionals.
- Improved Password Manager: A more intuitive interface for storing and autofilling credentials, with added prompts to detect weak or reused passwords.
- Performance Optimizations: Faster page rendering and reduced memory usage, making Edge more efficient on both high-end and older devices.
- Security Upgrades: Updated defenses against phishing and tracking, including stricter default settings for third-party cookies.
These features aim to keep Edge competitive in the browser market, catering to both casual users and IT-managed workplaces. However, the update’s launch has been overshadowed by a significant bug affecting first-time users.
Root Cause of ERR_INVALID_URL Error
The error occurs because of a conflict with the “HideFirstRunExperience” policy, often used by IT administrators to skip the welcome page and direct Edge to a homepage or blank tab. In version 135, this policy causes the browser to attempt loading the welcome page anyway, only to fail with the ERR_INVALID_URL message. Unlike previous versions, Edge 135 mishandles this setting, creating a roadblock for users.
Microsoft has confirmed the issue, attributing it to how the updated First-Run Experience interacts with the policy. While a fix is reportedly in development, no official patch has been released as of now. Until Microsoft resolves the issue, several workarounds can help users bypass the error and use Edge 135 normally.
Disable the HideFirstRunExperience Policy
- Open the Group Policy Editor or Registry Editor.
- Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge.
- Set HideFirstRunExperience to 0 or remove it.
- Restart Edge.
Note: This may cause the welcome page to appear on all devices, which could disrupt workflows in managed environments.
Open a New Window from the Taskbar
A quick workaround is to bypass the error by opening a new browser window:
- Right-click the Edge icon on the taskbar.
- Select “New window.”
- A fresh window should open without the error. The original error window can often be closed or ignored.
Launch Edge with a Blank Tab
You can force Edge to open a blank tab, sidestepping the welcome page:
- Press Win + R to open the Run dialog.
- Enter start microsoft-edge:about: blank and hit Enter.
- Edge will launch to a blank tab, ready for use.
Also, Roll Back to Edge Version 134 avoids the issue entirely, as it predates the bug. This involves uninstalling version 135 and installing the older version, but it’s a short-term fix that may skip critical security updates included in 135.
The error has frustrated IT teams, with Reddit threads highlighting the challenge of managing the glitch across fleets of devices. One sysadmin noted, “Disabling the policy works, but now every user gets the welcome screen—not great for our setup.” The new window trick has gained traction as a quick fix, though some report the error window persists in the background.
Microsoft has issued guidance, recommending disabling the HideFirstRunExperience policy or reverting to version 134 as interim solutions. The company is working on a patch, with early indications suggesting a future build—possibly 135.0.3179.66 or later—may resolve the issue.
Also Read:
