Member Avatar for sganandhsg

Hi Team,

Earlier we used IE options in Edge for opening our URL (application) with updating No-Merge option in Enterprise XML to access multiple sessions on the same server. But right now we are using Edge (pure) to use the same URL and unable to access more than one session (sessions are merged with recently opened)

Can anyone faced this problem earlier and how to overcome with this problem?

Thanks In Advance

  • 3 Contributors
  • 2 Replies
  • 865 Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by Dani

Dani AI

Generated

Short summary tied to the thread: previously used IE-mode “No‑Merge” to get independent sessions; that feature won’t behave the same in Chromium Edge. ’s InPrivate idea works for short-lived isolation, and ’s comment rightly points to browser/server behaviors, but the most practical fixes for “same URL, multiple concurrent sessions” are client-side isolation or true OS-level isolation.

Practical options (ordered by ease):

  • Use separate Edge profiles. Each profile has its own cookie/localStorage and will give you fully independent sessions. Click the profile avatar (top right) → Add profile → Continue without signing in (or sign in if you need persistence). Use Manage profile → Create desktop shortcut to open that profile quickly.

  • Launch Edge with a separate user data directory (good for automation or temporary test instances). Example:

    msedge --user-data-dir="C:\Temp\EdgeProfileA"

    Pick a unique folder for each instance. Do not point two running Edge processes at the same folder.

  • Use stronger isolation when needed: Windows Defender Application Guard, a VM, Windows Sandbox, or a different physical/virtual machine. These provide full OS-level separation and avoid any shared credentials or OS-auth artifacts.

Caveats to check before deciding: if the app uses Windows Integrated Authentication or the server maps sessions to an AD principal, browser-side isolation alone may not help — the server could still treat multiple windows as the same user. In that case use separate test accounts or full VM-level isolation. If persistent behavior is required across many test machines, ask the app owners to support multi-session test accounts or token-based session separation.

Recommended Answers

All 2 Replies

Member Avatar for rproffitt

What happens if you open a Private Browser instance? From the web:

The Microsoft Edge Incognito Mode is called InPrivate. To start an Edge private browsing session, press the “Settings and more” button in the top-right corner, and then click or tap on “New InPrivate window.” NOTE: You can also use the Microsoft Edge incognito keyboard shortcut: Ctrl + Shift + N.

Member Avatar for Dani

I think this is a limitation of Edge, not of your web application. They have a hard limit on the number of concurrent connections per hostname that are allowed, at least with HTTP/1.1. I'm not sure if the same limitation exists with HTTP/2. Does your web app use HTTP/2?

I'm not sure if there is a workaround via a registry edit, sorry.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.