Jan 21 2020 10:16 AM
I am currently evaluating Edge Chromium at our school. We are still running an on premise SharePoint 2016 Server and using Internet Explorer to access certain ActiveX functions. Therefore, the integrated IE mode comes in very handy.
However, I am facing an odd problem right now. If I open any Office document by right-clicking and selecting "Open in Office desktop app" the current tab gets closed. Although, the document will be opened correctly I will have to reopen said tab every time I open a document. This procedure does work in both Internet Explorer and Chrome without any problem. Does anyone have a clue on how to resolve this issue?
I have attached the chrome_debug log if this is of any help as well as a screenshot showing how I am trying to open a document.
Output of edge://version
Microsoft Edge81.0.400.0 (Offizielles Build) canary (64-Bit)Revision0bf87b6a890741739bc9951fea30553031d8d6f2BetriebssystemWindows 10 OS Version 1909 (Build 18363.592)JavaScriptV8 8.1.152Flash32.0.0.255 internal-not-yet-presentBenutzer-AgentMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4027.0 Safari/537.36 Edg/81.0.400.0Befehlszeile"C:\Users\HessSi\AppData\Local\Microsoft\Edge SxS\Application\msedge.exe" --flag-switches-begin --flag-switches-end --enable-audio-service-sandboxPfad zu ausführbarer DateiC:\Users\HessSi\AppData\Local\Microsoft\Edge SxS\Application\msedge.exeProfilpfadC:\Users\HessSi\AppData\Local\Microsoft\Edge SxS\User Data\DefaultAbweichungen202c099d-ca7d8d80
835c479f-ca7d8d80
7d846ba2-ca7d8d80
59e4e625-ca7d8d80
5be901aa-ca7d8d80
d883e2d7-ca7d8d80
efa3da2-ca7d8d80
fe8519a9-ca7d8d80
68743a2c-ca7d8d80
e8d5f23c-ca7d8d80
77cf2e93-ca7d8d80
1409bb6d-ca7d8d80
6707838f-ca7d8d80
cd1b70ba-ca7d8d80
8eb184f7-ca7d8d80
648a1f10-ca7d8d80
7b1b2ab3-ca7d8d80
43236943-ca7d8d80
29c45004-ca7d8d80
f60fa5c1-ca7d8d80
6382e2dd-ca7d8d80
ad41aff7-ca7d8d80
f1013d31-ca7d8d80
4ea303a6-ca7d8d80
2ccd073f-ca7d8d80
ce85c22a-ca7d8d80
caf7f8f1-ca7d8d80
d6e9f2d6-ca7d8d80
840bcf71-ca7d8d80
e6931c56-ca7d8d80
3e38b4f0-ca7d8d80
b76f455-ca7d8d80
3ee6367e-ca7d8d80
5e585ed7-ca7d8d80
1362429d-ca7d8d80
ab4a3c02-ca7d8d80
daff722c-d8d26f5e
b229a814-d8d26f5e
d8db6806-d8d26f5e
9539fc9e-d8d26f5e
8aef1b08-d8d26f5e
1a96c400-d8d26f5e
d338cc79-d8d26f5e
f959761-d8d26f5e
cf1d8a5d-d8d26f5e
ac75c30d-d8d26f5e
Mar 19 2020 10:08 AM
We have the same behavior in the latest Edge version 80.0.361.66 and ONLY in IEmode. When browsing to an on-premise sharepoint site and opening a Microsoft word or excel document, the current Edge tab closes, but only when you have more then 1 tab open. No solution found yet...
Apr 16 2020 04:09 PM
@Gleeman @SimonHessBZP Apologies for the delay and thank you for reporting the issue. We believe we have identified and fixed the issue. However, since it is an IE fix, it will ship as part of the OS updates. At the moment, given the current public health situation we are prioritizing our monthly security updates (Update Tuesday) over all other optional, non-security updates. As a result, this fix is a few months out. I'll provide an update closer to release.
May 11 2020 09:03 AM
@Shilpa_Subramanian Thank you very much for your feedback. Unfortunately, this issue still blocks the rollout of the new Edge at our organization. Therefore, I really appreciate that the issue should be fixed soon. Is there any possibility to already test it out, e.g. with a current Insider build of Windows 10?
Jun 30 2020 02:56 AM
We are several months out and have not received an update. Could you please provide one?
Thanks.
Jul 02 2020 11:44 AM
Solution@Jsink We are currently targeting the week of July 20th for an OS update to resolve this issue. The fix is available in Insider builds 20130 or after if you'd like to validate.
Thanks!
Jul 22 2020 05:42 AM
@Shilpa_Subramanian Thank you for the update. I can confirm that the latest cumulative update KB 4559004 solves the issue for us.
Aug 04 2020 04:45 AM
Hello
Is there a corresponding patch for Windows Server 2016?
We have the same problem on our Citrix XanApp farm.
thank you
Jul 02 2020 11:44 AM
Solution@Jsink We are currently targeting the week of July 20th for an OS update to resolve this issue. The fix is available in Insider builds 20130 or after if you'd like to validate.
Thanks!