T3rM1nat0Rr3

Microsoft’s latest browser update, Edge version 135, rolled out with a suite of upgrades designed to enhance productivity and security. However, a pesky bug is stealing the spotlight, greeting many users — particularly in enterprise environments — with an “ERR_INVALID_URL” error during the First-Run Experience (FRE). This article explores the update’s highlights, the issue disrupting it, and practical solutions to get back to browsing smoothly.
What’s new Microsoft Edge 135
Edge 135 brings a handful of improvements that make it a compelling choice for both casual users and professionals. Key features include:
Advanced Tab Grouping: Users can now collapse, color-code, and pin tab groups, streamlining workflows for those juggling multiple projects.
Upgraded Password Manager: A refreshed interface simplifies credential management, with proactive alerts for weak or reused passwords to bolster security.
Performance Boosts: Optimized page rendering and lower memory usage ensure Edge runs efficiently, even on older hardware.
Stronger Security: Enhanced protections against phishing and tracking, including tighter controls on third-party cookies, keep users safer online.
When launching Edge 135 for the first time, users expect a sleek welcome page to guide them through account setup and browser customization. Instead, a significant number — especially on managed enterprise systems — are met with an “ERR_INVALID_URL” error on the edge://welcome-new-device page.
The issue has ignited discussions across tech forums like Reddit’s r/Intune and r/sysadmin, where administrators report disruptions in deploying the update. One sysadmin lamented, “New users are stuck on this error, and it’s slowing down our rollout.”
What’s causing this error?
The root of the problem lies in the “HideFirstRunExperience” policy, commonly used by IT teams to bypass the welcome page and send users straight to a homepage or blank tab. In Edge 135, this policy triggers a conflict, causing the browser to attempt loading the welcome page anyway, only to fail with the ERR_INVALID_URL message.
Microsoft has acknowledged the bug, pinning it on the interaction between the updated First-Run Experience and the policy. A fix is in the works, but no patch has been released yet. Fortunately, several workarounds can bypass the error and restore Edge 135’s usability.
Disable the HideFirstRunExperience Policy
Turning off this policy lets the welcome page load properly. In the Group Policy Editor or Registry Editor, navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge, set HideFirstRunExperience to 0 (or delete it), and restart Edge. Be aware this may cause the welcome page to appear on all devices, which could disrupt enterprise setups.
Open a New Window
A quick fix is to right-click the Edge taskbar icon and select “New window.” This opens a fresh browser window without the error, though the original error window may need to be closed via Task Manager.
Launch with a Blank Tab
Force Edge to open a blank tab by pressing Win + R, typing start microsoft-edge:about:blank, and hitting Enter. This sidesteps the welcome page entirely.
Revert to Version 134
Rolling back to Edge 134 avoids the issue but sacrifices 135’s updates. Uninstall version 135 and install the older build, though this is less ideal due to potential security gaps.
Edge 135’s tab grouping, password upgrades, and performance tweaks promise a better browsing experience, but the ERR_INVALID_URL error has dampened its debut. Microsoft’s forthcoming patch will be critical to ensuring smooth adoption, especially in workplaces. For now, users can lean on these workarounds to keep browsing uninterrupted.
Have you hit this bug? Which fix worked for you? Share your thoughts as we await Microsoft’s solution.


What is Microsoft Edge WebView2 Runtime?
Microsoft Edge WebView2 is a runtime installation used to provide web-based features in Microsoft 365 desktop apps that Microsoft began installing on Windows devices earlier this year. WebView2 uses Microsoft Edge as the rendering engine.
In Windows 11, the component is installed on the system by default. On earlier versions of Windows, it is automatically installed for users with modern versions of Microsoft Office for the specific purpose of running Office applications and the components built into the applications, built on top of web frameworks.
For PC users looking to take advantage of new or improved Office features or add-ins that depend on WebView2, they do not require any user input/action; as soon as WebView2 is available on the device, the component will be installed automatically. Regarding updates, WebView2 Runtime uses its own automatic update process, separate from the update channel used by Microsoft 365 Apps, to keep WebView2 up to date with the latest security and reliability updates.

Silent installation
Windows 11/10

Silent installation
Windows 11/10
Edge with WebView2




https://www.mediafire.com/file/xm8uyowlo1ga3tm/Microsoft+Edge-WebView2+Runtime+135.0.3179.85+AIO+Silent+Install.7z/file

 
https://seyarabata.com/6802694bd64b0 

Windows 7/8
تثبيت صامت
Silent installation


Microsoft Edge-WebView2 Runtime 109.0.1518.140 Aio Win 7 Silent Install
Edge with WebView2



https://www.mediafire.com/file/3uckk412kgsd9m3/Microsoft+Edge-WebView2+Runtime+109.0.1518.140+Aio+Win+7+Silent+Install.7z/file


https://mir.cr/0EUVSWWV