Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Why does version 136.0 require my Primary Password whatever I'm browsing?

  • 7 回覆
  • 11 有這個問題
  • 296 次檢視
  • 最近回覆由 Bill Welland

According to Firefox Help, "After you have defined and set your Primary Password, you will be prompted to enter it once for each Firefox session, when Firefox needs access to your stored passwords." But since updating to version 136.0 I get asked for my Primary Password even to see my home page. Why is this?

According to Firefox Help, "After you have defined and set your Primary Password, you will be prompted to enter it once for each Firefox session, when Firefox needs access to your stored passwords." But since updating to version 136.0 I get asked for my Primary Password even to see my home page. Why is this?

被選擇的解決方法

For Windows 10 this was fixed some time ago. It's been fine in 137.0.2 and is still fine in 138.0

從原來的回覆中察看解決方案 👍 0

所有回覆 (7)

I see from the link that "The team won't be able to fix this regression for 136. We know what the issue is and are assessing how to address it, but we will need a bit of planning.", so now understand why I have the problem - I'm just puzzled that I didn't have it before the 136 update, even though it's been a known problem for a month.

Issue didn't exist in 135; it was reported in beta 136, a month ago. I hope you'll figure it out.

Many thanks for explaining. I find that if I click "Cancel" at that first demand for a password it doesn't ask me again until I go to a site that needs a password.

It's still broken in 137.0 on Mac OSx Sequoia 15.3.2.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1957959.

This is still broken in 138.0 on Mac OSx Sequoia 15.4.1.

I logged this bug 27 days ago, and no one seems to be addressing it:

https://bugzilla.mozilla.org/show_bug.cgi?id=1957959

選擇的解決方法

For Windows 10 this was fixed some time ago. It's been fine in 137.0.2 and is still fine in 138.0