Forum Discussion
Edge deletes Edge
After being updated to the new Dev build 77.0.223.0 any other trace of the old Edge has disappeared in the start menu as well as in search. It still shows its installed via Settings-App. The only way I could start it was by changing the Default Apps back to old edge and clicking a link leading to the internet from settings app. Is this intentional?
- Update: we believe we've identified the issue here and hope to fix this soon. Thank you so much for helping to identify this issue before it went out to a broader population!
20 Replies
I need the old Edge back again. In the previous Edge I used a specual Htlm program which is not functioning any more with the new Edge. I don't use Edge anyway except for this htlm program.
What can I do to get the old Edge back ?
Do a bing search!Ton_Hartink
- This happens to me too. I'm on Windows 10 insider build 18945 and Edge Canary "replaced" the old Edge. I'm fine with this move though, just reporting here
- JTKimbell
Microsoft
derekamoss and other folks - thanks so much for reporting this and the information you've provided so far. This is not the behavior we want to enable for users right now, Insiders or not.
If you are seeing this on your device, can you provide a few pieces of information?
- If you are in the Windows Insider Program or not
- Your version of Windows - you can run winver to get this, it will be something like "Version 1809 (OS Build 17763.292).
- What channel of the new Microsoft Edge you have installed: dev or canary.
Thank you!
- JTKimbellUpdate: we believe we've identified the issue here and hope to fix this soon. Thank you so much for helping to identify this issue before it went out to a broader population!
JTKimbell "Update: we believe we've identified the issue here and hope to fix this soon. Thank you so much for helping to identify this issue before it went out to a broader population!"
I think that the problem expanded with the introduction of KB4505903, which is to suggest that we are advancing backwards.
I reported on Wednesday July 24 that I could not replicate the error using Windows 10 Pro 1903 Build 18362.239 and Edge Dev Version 77.0.223.0.
This morning, the error showed up. The only change in environment was installation of KB4505903 this morning, which updated my computer to Windows 10 Pro 1903 Build 18362.267.
The error does not manifest on another computer which has not yet been updated, running Windows 10 Pro 1903 Build 18362.239 and Edge Dev Version 77.0.223.0.
So whatever else happened, it looks like the error may have been released into the wild, so to speak, by KB4505903.
In response to your question regarding Windows Insider participation (which might or might not be relevant at this point), I am a member of the Windows Insider Program, but am not currently testing any Insider builds on any of my computers. I am running the production 1903 version on both computers I'm using to test Edge Chromium.
derekamoss see this - https://www.onmsft.com/news/old-edge-may-soon-be-hidden-on-pcs-running-edge-insider-builds
Really would have been nice to point this happening though. I had figured that was what it was but figured it was to early to start. Assumed they would wait at least till beta flighting to do this. Thanks for the share though. I see it mentions release preview which is exactly what I am on.
derekamoss Yes they should have but may be beta is right around the corner.
derekamoss I am unable to replicate the issue on any of the three computers on which I'm running Dev 77.0.223.0. Both "Microsoft Edge" and "Microsoft Edge Dev" show up in the Start menu. You might consider https://microsoftedgesupport.microsoft.com/hc/en-us/requests/new.
tested it on multiple computers and the same happens. Wrote a thread on reddit about it and other people have the same problem. Are you in the windows insider program? Maybe thats the difference
derekamoss "[I] tested it on multiple computers and the same happens. Wrote a thread on reddit about it and other people have the same problem."
I don't doubt you, but I'm not seeing those results.
"Are you in the windows insider program?"
No, I am not. I am running Windows 10 Pro 1903 Build 18362.239 on two of the computers I checked, and Windows 10 Home Build 18362.239 on the other. I am running Version 77.0.223.0 (Official build) dev (64-bit) on all three. I am running Edge Chromium "out of the box", that is, without flags, extensions or other changes not included in the Settings menus.
"Maybe that's the difference."
It could be. I've read articles to the effect that Microsoft is taking steps to depreciate EdgeHTML in recent 20h1 Windows Insider builds, and if you and the others are testing 20H1, that might be reason why you are getting the results you are getting and I am not.
However, if the change in behavior occurred upon upgrade to Dev Version 77.0.223.0, it could be a bug, and it might make sense for you to report the issue to https://microsoftedgesupport.microsoft.com/hc/en-us/requests/new (as well as Microsoft Windows Insider Support) so that Microsoft can get on top of the issue.
