Microsoft password manager issue in recent edge updates

Question

Microsoft password manager issue in recent edge updates

GabzGonz 30

Hello, I use Microsoft password manager (MPM) with a customized primary password (PP) and it ask for the local PP confirmation every time I want to access passwords or use them in any logged out web page. In last edge update "Version 143.0.3650.139 (Official build) (64-bit)" my PP is not recognized anymore like if was changed or something. This issue was present in a desktop PC Windows 11 Pro, 25H2.

Windows updated recently, but I don't know if this issue is due the windows update or an edge update. I was able to recover all the passwords by reinstalling edge and creating the PP again, though.

I use MPM in my laptop as well with Windows 11 24H2 and this issue is not present there.

Anyone have faced this problem? Clearing cache could solve it in case happen again? maybe an issue from 25H2? This matter is very important, thanks in advance for the assistance.

0 comments

Answer accepted by question author

Hendrix-V 21,000 Microsoft External Staff Moderator

Hi GabzGonz,

Welcome to the Microsoft Q&A forum.

Based on your description, the issue with the Primary Password (PP) not being recognized after updating Microsoft Edge on Windows 11 (25H2) is most likely related to local profile data rather than your password itself.

In this situation, clearing cache generally does not resolve this issue because PP validation depends on encrypted keys, not cached data. Before making changes, ensure to export your saved passwords (requires device PIN) to ensure nothing is lost.

Here are some options that you can consider:

1 - Reset Edge Settings

Open Microsoft Edge, click the three dots (… menu) in the top-right corner.
Go to Settings > Reset settings > Restore settings to their default values.
Confirm by clicking Reset.

2 - Create a New Profile

In Microsoft Edge, add a new profile and sign in with your Microsoft account.

I look forward to receiving your update. Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

GabzGonz 30 Reputation points

2026-01-16T19:00:16.4166667+00:00

Hello, thank you for your answer. Your suggestions is "technically" exactly what I did to solve this situation. I am very curious about what you mentioned on local profile data, is possible a corruption or any change in that encrypted file after an update? I have to add that I "touch" very often files in my local profile directory, but I doubt that the command fd (a find-like tool) is able to corrupt files while doing searches.

As I mentioned the problem is solved, but I don't know if will appear again. For now would be helpful to know the possible causes of this issue. Any idea?
Hendrix-V 21,000 Reputation points Microsoft External Staff Moderator

2026-01-17T03:13:20.5733333+00:00
Hi GabzGonz,

Welcome back and thanks for sharing your concerns. I'm relieved that the issue is solved.

As it is often linked to changes in local profile data, here are some possible causes:

Encryption Key Updates: Microsoft Edge uses OS-level encryption keys to secure credentials. After major updates, these keys may be regenerated or re-associated with your profile, which can temporarily affect PP validation.

Profile Schema Changes: Updates sometimes introduce new fields or migrate data structures. If migration doesn’t complete properly, the password manager may reject the PP.

File Integrity During Updates: While tools like fd only read files and don’t cause corruption, incomplete writes during an update or a crash can lead to inconsistencies in local profile data.

Here are some preventive steps that you can consider:

Enable sync to ensure your passwords are backed up and accessible across devices.

Before making changes, export your saved passwords (requires device PIN).

Avoid manual edits in Profile Folders, as direct changes can break integrity checks.

I hope the insights shared in the forum help address your concerns effectively.

If there is anything else I can assist you with, please feel free to let me know in the Comments section.

In addition, if you found the answer helpful, we’d really appreciate it if you could click "Accept Answer" and kindly give it an upvote.
GabzGonz 30 Reputation points

2026-01-17T14:33:00.54+00:00

@Hendrix-V Thanks again for the info. Updates should not make changes in that file, I use also the password manager from firefox and this have never happened with that tool. Unfortunately, I dont have enough data to report this bug and I dont know exactly what caused it, but I will try to monitor it from now.
Hendrix-V 21,000 Reputation points Microsoft External Staff Moderator

2026-01-18T00:46:22.7333333+00:00

Hi GabzGonz,

I'm relieved to know that you made a great decision and everything is good to go on your side. I hope the insights shared in the forum help address your concerns effectively. And thank you for accepting my answer since accepting it helps others with similar concerns can find useful information.

As you mentioned updates should not interfere with encrypted profile files, here's some information to address your concern:

Firefox and other browsers often handle profile migrations differently, which can make them appear more resilient in these scenarios. In Edge, the Primary Password relies on local encryption keys tied to the OS key store, so when those keys are rotated or re-associated during major updates, it can occasionally cause mismatches that break authentication.

If you have any updates or further questions, please feel free to share them with us.

1 additional answer

Your answer

GabzGonz 30 Reputation points

2026-01-16T19:00:16.4166667+00:00

Hello, thank you for your answer. Your suggestions is "technically" exactly what I did to solve this situation. I am very curious about what you mentioned on local profile data, is possible a corruption or any change in that encrypted file after an update? I have to add that I "touch" very often files in my local profile directory, but I doubt that the command fd (a find-like tool) is able to corrupt files while doing searches.

As I mentioned the problem is solved, but I don't know if will appear again. For now would be helpful to know the possible causes of this issue. Any idea?
Hendrix-V 21,000 Reputation points Microsoft External Staff Moderator

2026-01-17T03:13:20.5733333+00:00

Hi GabzGonz,

Welcome back and thanks for sharing your concerns. I'm relieved that the issue is solved.

As it is often linked to changes in local profile data, here are some possible causes:

Encryption Key Updates: Microsoft Edge uses OS-level encryption keys to secure credentials. After major updates, these keys may be regenerated or re-associated with your profile, which can temporarily affect PP validation.

Profile Schema Changes: Updates sometimes introduce new fields or migrate data structures. If migration doesn’t complete properly, the password manager may reject the PP.

File Integrity During Updates: While tools like fd only read files and don’t cause corruption, incomplete writes during an update or a crash can lead to inconsistencies in local profile data.

Here are some preventive steps that you can consider:

Enable sync to ensure your passwords are backed up and accessible across devices.

Before making changes, export your saved passwords (requires device PIN).

Avoid manual edits in Profile Folders, as direct changes can break integrity checks.

I hope the insights shared in the forum help address your concerns effectively.

If there is anything else I can assist you with, please feel free to let me know in the Comments section.

In addition, if you found the answer helpful, we’d really appreciate it if you could click "Accept Answer" and kindly give it an upvote.
GabzGonz 30 Reputation points

2026-01-17T14:33:00.54+00:00

@Hendrix-V Thanks again for the info. Updates should not make changes in that file, I use also the password manager from firefox and this have never happened with that tool. Unfortunately, I dont have enough data to report this bug and I dont know exactly what caused it, but I will try to monitor it from now.
Hendrix-V 21,000 Reputation points Microsoft External Staff Moderator

2026-01-18T00:46:22.7333333+00:00

Hi GabzGonz,

I'm relieved to know that you made a great decision and everything is good to go on your side. I hope the insights shared in the forum help address your concerns effectively. And thank you for accepting my answer since accepting it helps others with similar concerns can find useful information.

As you mentioned updates should not interfere with encrypted profile files, here's some information to address your concern:

Firefox and other browsers often handle profile migrations differently, which can make them appear more resilient in these scenarios. In Edge, the Primary Password relies on local encryption keys tied to the OS key store, so when those keys are rotated or re-associated during major updates, it can occasionally cause mismatches that break authentication.

If you have any updates or further questions, please feel free to share them with us.

Answer 1

It seems like you are experiencing an issue with the Microsoft Password Manager (MPM) where your primary password (PP) is not being recognized after a recent update to Microsoft Edge. This could potentially be related to the updates in either Microsoft Edge or Windows 11, but without specific details from Microsoft regarding the changes in the latest updates, it's hard to pinpoint the exact cause.

Reinstalling Edge and creating a new primary password resolved the issue for you, which suggests that there might have been a corruption or misconfiguration in the previous installation. Clearing the cache can sometimes help with various browser-related issues, but it may not directly resolve problems related to the password manager itself.

Since you mentioned that the issue does not occur on your laptop with a different version of Windows 11, it could be related to the specific configuration or updates on your desktop PC. Keeping both your browser and operating system updated is generally recommended, but if this issue persists, you may want to consider reaching out to Microsoft support for further assistance.

References: