Forum Discussion
adrianghc
Aug 15, 2020Iron Contributor
On version 20H2, the File Explorer on the taskbar often shows an active window with an Edge tab
On the Windows beta channel (version 20H2, build 19402.450), the File Explorer on the taskbar often shows an active window with an Edge tab. Clicking the explorer icon or the thumbnail that shows the...
- Apr 05, 2021Same problem around here since august 2020. Yesterday, I found the flag #edge-window-tab-manager. If you disable it, the problem goes away. There's is a nausty bug with the integration of edge chromium in windows.
alex4998
Mar 14, 2021Copper Contributor
Having the same problem. Also, reported it many times in many boards. No response, no workaround suggestions, no fixes, no idea when it will finally be resolved. It's very annoying. I see only one possibility that this issue does not have a lot of attention from Microsoft. Apparently it is a problem of using Edge and most likely there won't be an issue with Chrome. I didn't switch back to Chrome only because I don't want to deal with moving my passwords and all other settings over but I'm really close to doing that.
adrianghc
Mar 14, 2021Iron Contributor
alex4998 I think this was solved in Insider builds months ago, so at worst I guess we'll have to wait until 21H2 is released.
- MatmanMar 14, 2021Brass ContributorI tested with a 21H2 build and it was not solved.
- adrianghcMar 14, 2021Iron Contributor
Matman Well, I thought so, since the changelog for build 21277 says the following:
- We fixed an issue that could result in Microsoft Edge windows unexpectedly being grouped with File Explorer in the taskbar.
- MatmanMar 15, 2021Brass Contributor
Yes, I was fooled by that as well, but a conversation with a Microsoft employee on Reddit revealed that the issue was fixed for "regular Windows desktops" (an issue I never had) but that she was unsure if it had been resolved for virtual desktop users. As I mentioned, I only ever had this problem while using the Windows virtual desktop feature, and can confirm the issue persists beyond the 21277 update.