03-03-26 02:22 PM
Since November last year, we have started having issues where Edge reopens tabs from previously closed sessions. This is causing problems with processes being able to log into applications. We have made sure all settings in Edge are set appropriately to load a new tab each time but no matter what settings we select, the previous sessions tabs are loaded as well as the new tab.
Nothing has changed from our end and this seemed to coincide with Microsoft Edge update at the end of October but we cannot see anything relating to this in the release notes. Any help would be much appreciated
03-03-26 02:30 PM
We haven't seen this issue as far as I've seen. Are you 100% sure that the settings are correct? I mean, I believe you, but I'm asking you the same question I'd ask myself in this situation just to make sure.
Maybe screenshot some Edge settings, and I can go look at our settings as well to compare to.
I'm not surprised by an issue like this. Microslop has frankly been doing a pretty bad job of updating Edge for the last couple of years (maybe it's always been bad).
One thing to consider is trying InPrivate mode which theoretically should never open previously-opened tabs.
Another thing to check might be Startup boost. I feel like it shouldn't cause this, but I could imagine a world where Microsoft makes Startup boost keep tabs open in the background even when you close the browser. To avoid this issue, you could either disable Startup boost or always kill msedge.exe before you launch it.
In the end, what I would be very curious about is whether you see this issue even after the msedge process is killed. And if it still happens then, that's when I'd try InPrivate mode. Honestly InPrivate mode prevents a lot of issues. The only real downside that I've found is that the toggle in the extension settings that enables the browser extension to be used in inprivate mode will randomly turn itself off. We have an automation called Set Up MS Edge that we use to run daily on all machines to toggle this setting if it turns off as well as verifying/setting like 20 other various MS Edge settings because we're too lazy to find out how to do it the correct way. 😃
03-03-26 02:41 PM
I have attached images of the settings we currently have set showing all of the suggested settings are switched off/accordingly but still getting previous tabs loading. To note, this happens primarly if we have force closed msedge. We have not yet tried running with an InPrivate session but try this as a possible workaround but would really like to know what has caused this to start happening and a permanent solution if possible. Thanks for your swift reply
03-03-26 03:50 PM
@ormando ,
This is part commiseration and part possible solution.
We have a similar issue where I have been setting all of the 'performance' settings to prevent MS Edge from running in 'efficiency' mode, to no avail. We also had an automation that swept through the settings, but that was it's own exercise in futility. It seemed every 'dot' update somehow reconfigured the structure of the settings, not just the settings themselves. I spent as much time updating the automations as I did updating our Runtimes.
But to the possible solution. As a part of our MS Edge 'launch' object, at the very start we clear out the following folder:
C:\Users\_User_\AppData\Local\Microsoft\Edge\User Data\Default\Cache\Cache_Data\ (replace the '_User_' with the username that is logged into the machine).
This is essentially the 'sledgehammer drive a nail' equivalent to the 'What to Clear on Exit' options, but it is not affected by how the previous session closed out. Since we added this, I cannot remember seeing an orphan session on opening, and we have also not had the 'closed unexpectedly' alert that can disrupt things.
Let me know if it helps,
Red
30-03-26 09:37 PM
We ran into this issue as well.
Solved by adding extra starting switch "--no-restore-session" to App Modeler.