Thunderbird 140 ESR is out now with new features, bug fixes and critical security patches by David Uzondu Thunderbird 140 Extended Support Release (ESR) is now available for download. This comes just days after the release of the regular Thunderbird 140. The difference, if you're wondering, is that the ESR version is built for stability, made for businesses and schools that can't have frequent changes. It receives security patches for a year, while the main version gets new features every four weeks. This yearly update schedule helps avoid breaking how things work in large offices. As for what's new, Thunderbird 140 ESR packs in many of the changes from past monthly releases. A nice addition is better dark mode support, which now changes the look of messages on its own and gives you a quick toggle button. Notifications have been improved with new buttons to "Mark as Read", "Delete", and "Mark as Spam" right in the alert. When it comes to folder management, you can finally sort folders manually and control threading or sorting globally from a new dedicated "Appearance" settings section. This section now combines appearance controls that were previously scattered in the General settings. Here's the full list of what's new: Implemented enterprise policy to allow granular in-app notification control. New mail alert now includes message disposition buttons. Added 'Mark as Read' and 'Delete' actions to mail notifications. Added 'Mark as Spam' and 'Mark as Starred' actions to mail notifications. Support dark reader for the message pane. Messages are automatically adapted to dark mode with a quick toggle in the header. Message filters are now available in the Folder Pane context menu. Added horizontal threadpane scrolling (mail.threadpane.table.horizontal_scroll). Implemented customizable row count for Cards View in 'Appearance' settings. Implemented the ability to manually sort folders in the folder pane. New "Appearance" Settings UI to globally control message threading/sorting order. Added a checkbox to select/unselect all calendars in the calendar setup wizard. Account Hub enabled by default for second email setup. Add-ons: Added support for specifying a cookieStoreId when creating a space. Added Thunderbird-specific loading symbol. The collection of bug fixes is huge. It tackles frustrating issues, like how deleting an attachment from a saved .eml file would only seem to work, failing in the background without any warning. Deeper fixes include patching a race condition during folder compaction that could cause instability, and putting a stop to the strange bug that made empty emails dated 1970-01-01 appear in some POP3 inboxes. Feed subscriptions, which were completely broken, have also been repaired. Of course, a release would not be complete without some security fixes. The update addresses the vulnerabilities detailed in Mozilla's high-impact security advisory MFSA 2025-54. A key vulnerability patched is CVE-2025-6424, a use-after-free memory flaw with the potential to crash the application. Another fix specific to macOS closes a loophole where the application failed to trigger a safety warning when opening ".terminal" files, a mistake that could permit malicious code to execute. Other fixes stop info from leaking and prevent websites from getting around security rules. Updating is definitely recommended. Thunderbird 140 ESR is available for download on Windows 10/11, Windows 7/8.1, macOS, and Linux. You can also grab the regular release from our Software page. Full release notes for 140 ESR can be found here.

AMD finally clarifies Windows TPM & BitLocker bug that still affects Ryzen CPUs by Sayan Sen Back in 2023, Neowin reported on TPM attestation failures on AMD Ryzen PCs that had been known since December 2022 but were still around at the time, even several months later. We came to know of the bug after some of our forum members alerted us. On the issue notes, Microsoft wrote, "TPM attestation for AMD platforms with ASP firmware TPM might fail with error code 0x80070490 on Windows systems. This issue is resolved on later versions of AMD firmware. Consult with device manufacturers and firmware release notes for which firmware versions contain the update." So while Microsoft stated that a future (post-2022) AMD firmware had supposedly already resolved the issue, we were a bit surprised to see that the issue still persisted, and as such, mostly blamed AMD for the problem. TPM 2.0 mechanism |Image via Microsoft However, it turns out we were not quite right in doing so. While browsing, Neowin spotted a new support article today regarding the TPM attestation failure that is still probably happening, AMD has clarified that the company had released the firmware patch already in 2022 but some of the motherboard vendors did not release that update for users. The issue affects Ryzen 1000 (Zen1) up to Ryzen 5000 (Zen 3) processors, so it mainly affects AM4 motherboards. AMD further clarifies that "motherboards with AMD fTPM 3.*.0" are affected. If you are not sure the company says: Correctly functioning TPM attestation on my Ryzen 5700G PC The company has explained the situation and its implications and how it can lead systems into BitLocker recovery: We are not sure why the board makers chose not to do so, perhaps they noticed some major issue elsewhere; and so AMD now recommends contacting your board's manufacturer directly if you are still having TPM attestation failures and related BitLocker issues or encountering other problems. For example, AMD notes that gamers may be unable to compete in online cash tournaments. The company writes: BitLocker lockout can be a massive problem if you are not careful and so it is recommended that you bookmark this official guide from Microsoft. You can find the support article regarding TPM attestation here on AMD's official website.

Now, honestly. Are these benchmarks justify a need for a clean install? I would opt for it if the performance was dramatically better, but for just a few digits up, I don't think it is worth the fuss. Also, I have my doubts for this test. Before a "dirty" install, I cleanup all OS garbage. I also do this after the installation. I haven't noticed the slightest difference between the two.

I say good

After updating to One UI 7 I'm facing fingerprint issues. The phone is having hard times in detecting my fingerprints. I have already tried deleting the fingerprints and re-registering them. I have also tried to register the same finger for all 4 fingerprint slots.