Launching Microsoft Edge on Windows 10
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Microsoft community,
Since updating to Edge version 135, we encountered an issue where the First Start Wizard fails to load and displays the error "ERR_INVALID_URL." This happens when the "Hide First-Run Experience" policy is enabled. Disabling this policy resolves the issue, suggesting that changes in Edge version 135 conflict with this setting.
I came across a Reddit discussion mentioning similar experiences. Has anyone else faced this issue, or found a different solution?
Thank you in advance for your help and insights!
Evert
Launching Microsoft Edge on Windows 10
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
The issue we are experiencing with the First-Run Experience in Microsoft Edge has already been acknowledged by Microsoft. It is listed on their official Known Issues page.
I found a way to fix this for smaller companies (temporarily until microsoft does something about this problem). When we put the properties on Microsoft Edge on the desktop we can reconfigure the target in the desktop shortcut. Add to the end :
--no-first-run --disable-features=WelcomePage.
Then the edge will turn on without the Welcome Page.
I hope this will help someone.
Installed version 135.0.3179.73 but unfortunatly the issue is still there.
Just updated MS Edge to version 135.0.3179.66, the issue persists.
same here, dont want to disable HideFirstRunExperience for all of my 1200 users (if you do, the wizard gonna run for them) so I asked the tech team just before they deliver a new computer to change the reg key : computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge hideFirstRunExperience to 0
it's give enough time for a first session opening/opening Edge with wizard active
so i hope Microsoft gonna patch this issue