Forum Discussion
Looks like installing the Stable version breaks the browser
"...from the official Microsoft Link... the word stable and an official link made it a good candidate to install ..."
You aren't the first to be lured into the honeypot, and a honeypot it is.
However, for the record, the leaked URLs** are not "official Microsoft links"*** but instead leaked URLs to builds being used to test deployment processes, which entail embedding Edge Chromium into Windows 10, removing Edge (Classic) as a Windows 10 browser, and removing the ability to uninstall Edge Chromium. Installation creates an ugly mess for anyone who falls into the honeypot.
And too many have fallen into for the lure. We've had numerous discussions on this Forum, and early on, before the full scope of the problems were reported, even experienced Insiders were posting things like "Unlike the previously leaked beta versions, this time the stable leaks come straight from Microsoft servers, so they are safe."****
I understand that Microsoft needs to test deployment "in the wild", but the less scrupulous among the trade press have published these links many times without warnings about the disastrous side effects (we had a round of trade press articles in August and another round in the last week).
Elliot Kirk josh_bodner David Rubino I think that Microsoft has an obligation to step up and put a flash screen in front of the URLs clearly warning the unwary of the dangers of downloading the builds being tested through those links. It is not helping anyone to create major problems for consumers who fall into the honeypot.
==================
** to Microsoft servers used by Microsoft to deploy software and test deployment processes
*** to my best knowledge as of this date, there are no links to the URLs on any Microsoft site
**** see, for example, comments to the "Stable Version" post, 2019-08-22
tomscharbach wrote:"...from the official Microsoft Link... the word stable and an official link made it a good candidate to install ..."
You aren't the first to be lured into the honeypot, and a honeypot it is.
However, for the record, the leaked URLs** are not "official Microsoft links"*** but instead leaked URLs to builds being used to test deployment processes, which entail embedding Edge Chromium into Windows 10, removing Edge (Classic) as a Windows 10 browser, and removing the ability to uninstall Edge Chromium. Installation creates an ugly mess for anyone who falls into the honeypot.
And too many have fallen into for the lure. We've had numerous discussions on this Forum, and early on, before the full scope of the problems were reported, even experienced Insiders were posting things like "Unlike the previously leaked beta versions, this time the stable leaks come straight from Microsoft servers, so they are safe."****
I understand that Microsoft needs to test deployment "in the wild", but the less scrupulous among the trade press have published these links many times without warnings about the disastrous side effects (we had a round of trade press articles in August and another round in the last week).
Elliot Kirk josh_bodner David Rubino I think that Microsoft has an obligation to step up and put a flash screen in front of the URLs clearly warning the unwary of the dangers of downloading the builds being tested through those links. It is not helping anyone to create major problems for consumers who fall into the honeypot.
==================
** to Microsoft servers used by Microsoft to deploy software and test deployment processes
*** to my best knowledge as of this date, there are no links to the URLs on any Microsoft site
**** see, for example, comments to the "Stable Version" post, 2019-08-22
That's the direct link to the Microsoft Edge stable and it is on Live servers which belong to Microsoft.
HotCakeX "That's the direct link to the Microsoft Edge stable and it is on Live servers which belong to Microsoft."
For the record, that URL is one of two URLs being distributed in the trade press without warning about the side effects of installation, both URLs linking to directories on servers used by Microsoft to deploy software.
But that is the problem, isn't it -- Microsoft is not publishing the URL's or (to my best knowledge) linking to them from any public Microsoft site as of this date (presumably because Microsoft does not want consumers downloading from either URL at this point**), but others are publishing the URLs without any warnings to the innocent or the unwary, who are lured into the honeypot.
It is because others are publishing links to the URLs (and in that sense, the URLs have now become public) that Microsoft should put a splash screen with warnings in front of the URLs.
======================
** Microsoft appears to be testing deployment processes from live servers precisely because Edge Chromium will be, at some point in the future, deployed from those live servers, but that does not suggest (to me, anyway) that Microsoft intends to have consumers downloading from those links at this point.
- I didn't mention any press site, it's only what you are saying.
It's not important either, the link is publicly accessible.
And the link for Microsoft Edge Stable version is working Flawlessly 🙂
Also as expected and mentioned in the official document here
https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-sysupdate-windows-updates
it did automatically replace the Edge classic on Windows 10 build 19008
HotCakeX "And https://c2rsetup.officeapps.live.com/c2r/downloadEdge.aspx?ProductreleaseID=Edge&platform=Default&version=Edge&Channel=Stable&language=en is working Flawlessly :)"
That is a link to the c2rsetup.officeapps.live.com download URL.
Did you get that link from a public-facing Microsoft website publishing that URL, or did you get it from the trade press?
If you have a link to that URL from a public-facing Microsoft website, would you please give us the link to the Microsoft site (not the URL, but the Microsoft site containing the link) on which Microsoft publishing that URL?
- If Microsoft didn't want people to test and download it, they would have made that file on their server private