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

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기
해결된 질문 보존

My personal folders with contents don't show after Thunderbird updates to 128.4.3esr (64-bit)

Mega Mike

Yesterday TB did an update and when I started the app today it was like I was using the program for the very first time. I had to re-enter my e-mail account settings, change the window layout (that took one hour) and now find a way to get my personal folders back. There are folders that I myself created and they contain saved e-mails.

Using my ISP's webmail service I can see that these folders still exist on their server. But despite all my one line research, I haven't been able to solve this problem. I did run trouble shoot, but that didn't help.

If anyone has any tips, tricks or other solutions, please let me know.

Yesterday TB did an update and when I started the app today it was like I was using the program for the very first time. I had to re-enter my e-mail account settings, change the window layout (that took one hour) and now find a way to get my personal folders back. There are folders that I myself created and they contain saved e-mails. Using my ISP's webmail service I can see that these folders still exist on their server. But despite all my one line research, I haven't been able to solve this problem. I did run trouble shoot, but that didn't help. If anyone has any tips, tricks or other solutions, please let me know.

모든 댓글 (3)

선택된 해결법

This sometimes happens when Thunderbird is updated. Other software (antivirus? VPN?) interrupts the process, causing thunderbird's update of the prefs.js file to fail. When this happens, the updates appear in prefs-1.js. On a restart, Thunderbird starts fresh, causing you to reenter email info. exiting thunderbird, locating the prefs-1.js and renaming to prefs.js generally restores everything.

Hello David,

Thank you for your response. I have been able to use your information to apparently solve my problem. But in my case, I actually had seven prefs.js files, the original plus numbers 1 through 6. So instead of renaming prefs-1.js, I renamed prefs-6.js because it seemed like the newest file from the bunch.

I think that this has solved the problem. We'll see in the days and weeks ahead.

Thank you for your intervention and advice!

You're welcome. :)