Starting this morning, Edge does not remember logins to any website

Anonymous
2020-10-10T13:52:48+00:00

Starting this morning, every time I close Edge and reopen it, it doesn't remember any of my login so I have to login every time to every website.

I confirmed my setting is set to NOT clear cookies when I close my browser and it has always been this way.  I have never had this issue until this morning.

A features update was installed this morning and that's when this problem started.  Is there a bug with this update?  I'm running Windows 10 and Edge Version 86.0.622.38.  As you can imagine, it is quite annoying having to login to every time to every website.  

Update-There must be a bug because other people on Reddit are starting to report the same issue.

Microsoft Edge | Website issues | Windows 10

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2021-01-08T20:46:00+00:00

Hi folks, 

The original topic of this thread (Microsoft Edge not remembering logins) has been resolved. Make sure you've updated to the latest version of Edge to get the fix! I'm locking this thread as it is becoming difficult to moderate and troubleshoot individual issues, and this thread has turned in to a catch-all for all password issues. 

If you are still seeing issues with Edge not remembering passwords and all other programs are remembering your logins as expected, please start a new thread so we can help you individually. 

If you are seeing system-wide issues with passwords being saved:

• Check your Windows version to confirm if you are on Build 19041.173 or later

• If yes, reference this troubleshooting document Outlook and other apps won't remember password after Windows Updates - Outlook (microsoft.com) Note that this is a workaround until this Windows issue is patched.

-Alex

Was this answer helpful?

3 people found this answer helpful.
0 comments

222 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-27T23:46:35+00:00

    Edge Stable 86.0.622.56 has been released and seems the bug is fixed now.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-28T00:05:34+00:00

    The PowerShell command you posted returned a registry Key, not a named task.  that's why i looked it up in registry and came up with Carbonite.  Other than that nothing showed up.  

    I also thought the problem may have started when I created a second account on the computer so i removed that.

    No Improvement

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-29T17:38:39+00:00

    there was another Edge update today 10/25... didn't help.  

    If you can confirm that you're now running build 86.0.622.56 (or newer), and you're still losing log-ins between browser sessions and computer restarts, then you have a problem different from the one fixed in that build.  It's likely that it's the one caused by changes to the Data Protection API (DPAPI) in Windows 10 20H2. That bug is waiting for a Windows Update. You may find this thread interesting: Data Protection API (DPAPI) seemingly broken - Microsoft Community; it's safe enough to try out AyrA.ch's little utility to see whether DPAPI is working properly on your machine, but I'd steer clear of his 'potential solution.' 

    Not sure why I now have a Edge Update app in my Settings.. but whatever. 

    You should see two separate Edge installations in your program files directory, one in a folder called Edge containing msedge.exe,  and the other in a folder called EdgeUpdate containing MicrosoftEdgeUpdate.exe, the program that tries to keep Edge updated by calling home regularly. Where are you seeing 'Edge Update' in Settings?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-29T19:14:58+00:00

    The PowerShell command you posted returned a registry Key, not a named task. 

    You may have been misled by the PS result. Carbonite have given the task a particularly unfriendly Name, which happens to be the GUID of the Carbonite class in the registry. You should have been able to see the task's Name in Task Scheduler:

    It's the circled option that triggers the problem: if it's selected, S4U is invoked. In Windows 10 2004 and later, this breaks the normal retrieval of credentials and you have to log in repeatedly in some places.

    Was this answer helpful?

    0 comments