IE11 losing dropping cookies

Fixed Issue #8748123


Lakshman B.
Sep 2, 2016
This issue is public.
Found in
  • Internet Explorer
Found in build #
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

IE11 Version: 11.0.9600.18314
Update Versions: 11.0.31 (KB3154070)
OS: Windows 7 Pro

Browser intermittently drops the cookies and causing the user redirected to login page with our vendor site. The Fiddler shows cookie getting dropped and server is returning 302 with login page. This is not easy to create and vendors have trouble to reproduce in their environment.
I thought if we can use the proposed workaround by setting registry as specified in the below link it would solve our problem. But that option is also ruled out. We are also not using persistent cookies and Fiddler shows one IE process ID.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Status to “Fixed”

    • Thank
      you for the feedback. This issue appears to have been fixed in Microsoft Edge.
      We’re not presently working on feature bugs in Internet Explorer outside of
      security-related issues. If you have a premier support contract you can visit and open
      a support incident and work with an engineer to address this issue.


      Microsoft Edge Team

    • Brad,
      This problem did not occur in IE11 prior to the 1607 release. The Edge browser did have the problem prior to 1607 and it was fixed in 1607.

      However, IE11 became broken with the 1607 update.

      Best Regards,

    • HI Don: Whats is the FIX for this issue? I’m facing similar issue with
      Windows 10 and IE11 (OS Build 10586.1045)

      Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko.


    • We are also having the same issue with our web application. Multiple simultaneous requests in different tabs are making the browser to drop the cookie and trying to open a new session. Solutions mentioned in the link in the main post have not helped to solve the issue. We are using the following version of IE.

      Version: 11.0.9600.18792
      Update versions: 11.0.46 (KB4036586)

    • I am also facing same issue. When trying to open new window from IFRAME control. But my issue was resolved when I added below registry entry on my local machine :

      HKEY_CURRENT_USER/Software/Microsoft/Internet Explorer/Main/TabProcGrowth and set value to 0

      Hopy this will solve the problem !

    • We’ve been through a long process of trying to resolve the loss of session cookies for our IE customers, where our ActiveX controls are used to make HTTP requests to the server from our web client (using the COM XmlHttpRequest object). Ultimately, after a lot of time spent trying to figure things out ourselves, we opened a Microsoft Premiere incident…and after a lot of time on their end, they were able to identify the problem as follows: “By design session cookies are not supported to be handed across processes.” At some point there was an API change where reading the cookies was taken over by the InternetGetCookie WinInet API; this API will only search for session cookies in the current process. If the ActiveX or IFrame is run in a separate iexplore.exe process…then session cookies will be lost in the affected environments. Why the session cookies are deleted in the process where they were first created is unknown at this time. With all of that said, the solution outlined by Kamlesh B makes a lot of sense (assuming it will work across all IE versions and 64bit operating systems), where IE is forced to run everything in a single iexplore.exe process. See the note from Kamelsh B about setting the TabProcGrowth to 0. Our solution is more complex and involves encrypting the session cookies and passing them to the ActiveX where they are decrypted and sent to the server in a custom header; the server then processes the cookies from this special header and adds them to both the request and response (we’re using ASP.NET).

    • Just a follow up regarding attempting to set the TabProcGrowth to 0 as noted above: Unfortunately, this has the effect of making our ActiveX inaccessible; however, the more complex solution I mentioned above is working ok for us…so it’s currently a non-issue.

    • My organization is also experiencing this problem.

      A more thorough description of the “complex” solution above would be appreciated.

    You need to sign in to your Microsoft account to add a comment.

    Sign in