+ Android: dark mode rework, thanks to cjee21
+ Android: modernize the backend, thanks to cjee21
+ More coherency/integrity checks, sponsored by Austrian Mediathek
+ MXF: fix crash with some 0 byte audio packets
+ MPEG-4: C2PA support
+ ID3v2: support of Olympus voice recorder metadata
+ Matroska: show block addition tracks
+ Matroska: add timecode label readout
+ Add default language string for ISO 639-2 special codes, thanks to cjee21
+ AVI/WAV: add support for WAVE_FORMAT_MPEG_HEAAC (0x1610)
+ AV1: Enable parsing raw OBU from network, thanks to cjee21
+ AV1: Indicate usage of Film Grain Synthesis, thanks to cjee21
+ Matroska/TimeCodeXML: add frame rate
+ Bindings: add C#/PowerShell (Windows/Linux) support, thanks to cjee21
x Matroska: fix incoherent readout of unordered tag elements
x TimeCodeXml output: fix lack of frame number with some MXF SDTI timecodes
x AVI/WAV: fix crash with some invalid FourCC
x SDP: fix false-positive detection
x I2469, CDP: fix handling of 708 streams caught in the middle
Imagine knowing how a smart device will actually perform in your home before you buy itβ¦ not from a spec sheet, but from anonymized data that people running setups just like yours have opted to share. Having answers to questions like: will this sensor work without the cloud? Is that smart plug actually being reported by users as reliable? Does βlocal controlβ mean local always, or just sometimes? Will these devices work well across protocols? What this device looks like in other usersβ homes?
Thatβs the idea behind the Open Home Foundation Device Database: a community-powered resource built from anonymized data shared voluntarily by Home Assistant users around the world. The aim: to give people the information they need to benefit from privacy, choice, and sustainability in their smart homes.
Having easy access to this wealth of data changes everything. With the device database at your fingertips, youβll know upfront that there are 1000+ Home Assistant users running that smart plug fully locally, and it includes those voltage and wattage sensors you were looking for. Or if you see a sensor everyoneβs raving about requires Bluetooth when your protocol of choice is Zigbee, the database could save you the hassle of buying it in the first place.
Of course, there are some excellent device databases and compatibility lists already available. Our own Works with Home Assistant (WWHA) program puts products through their paces in home settings, which has taught us how vital real-world testing is. But to really understand how devices perform across the incredibly diverse range of setups out there (different integrations, hardware combinations, network connections, and protocols) we need data at a much larger scale. Thatβs what makes the device database different: itβs thousands of real homes opting in to contribute real anonymized data. And thatβs only possible with your help.
Building together
Creating the device database is a big job, and weβre going to need your help to do it. Before we build a shiny new website or complex search engine, the first step is to make sure the data you opt to share with us is accurate, anonymized, and meaningful, so weβre prioritizing:
Privacy first: The information we collect strictly follows our privacy principles: we donβt collect any personal data, period. Instead, we only share aggregated versions of device data, ensuring our community gets the insights they need without compromising anyoneβs privacy. Check out our Data Use Statement for details.
Real-world context: Our device database is centered around anonymized device data from Home Assistant instances of users who choose to participate through this new Labs feature.
Laying the groundwork: To prepare the first stage of this initiative, we invited members of the Open Home Foundation, our commercial partners, and a range of Home Assistant users, to opt into sharing their device data with us. This collaborative start has helped us aggregate more than 2,000 unique devices across more than 160 integrations, with lots more to come.
Transparency: Weβve launched an initial public dashboard for aggregated statistics and data downloads, giving you a first look at the insights as they grow. Of course, we wonβt stop there, as weβre approaching this step-by-stepβ¦
Nothing happens overnight
Like everything we do, the Device database initiative follows a steady, iterative approach, which takes time. We want to be honest: nothing happens overnight. We donβt believe in hiding away for years behind closed doors just to launch our vision of a βperfectβ finished product (spoiler: thereβs no such thing as perfect!). Instead, in the true open source fashion, we build in the open, release early experiments, and refine them based on how our community actually uses them.
Right now, in these early stages, our focus is on planting the seeds and gathering the first shoots of real-world information, as well as your feedback. This way, the tools we build later can grow and evolve alongside your needs.
The next steps
Following our iterative philosophy, we have a roadmap of small, manageable milestones designed to gather feedback at every step:
1. Launching in Home Assistant Labs
We are introducing the Open Home Foundation device database as a Labs feature in the 2026.2 release of Home Assistant. The idea is to broaden visibility and reach a wider audience (hello, that means you π) willing to contribute by opting in to share their device data and providing valuable feedback.
2. Putting the data in your hands
Building on the further insights and feedback we gather, weβre planning to launch the first public device database web interface in the first half of 2026. The plan is to make it easier for you to explore and interact with the information, beyond simple statistical dashboards.
While this initial version will be far from the final version (if there ever is one!). By getting it into your hands as early as possible, we can better understand where to go next, and make sure our future work is focused on the most valuable features for you.
3. Encouraging community contributions
Right from the start, weβre establishing simple flows to enable you to contribute more easily, allowing you to enrich the device database by adding real-world insights, all under the watch of our community. The result: an authentic and unbiased source of truth that helps everyone make informed decisions when it comes to privacy, choice, and sustainability in the smart home.
Now itβs over to you!
Because this project belongs to the community, we need your perspective early and often to help shape what comes next.
This is a marathon, not a sprint. The device database will only become a definitive resource through consistent, collective effort over the coming months and years, but bit by bit, device by device, we can make something great together! Hereβs how you can be part of it:
Enable Device Analytics: If you use Home Assistant, opting into Device Analytics in the Labs menu is the direct way to contribute to the device database.
Provide feedback: Weβve created a simple survey form so you can let us know what you think of the initiative, and why youβd like to contribute (or not!).
Join the discussion: We also have a dedicated Discord channel and want to hear what matters most to you: how can we make the device database a flourishing resource the community can trust for years to come?
Together weβll build a transparent, open, and community-driven map of the real-world smart home ecosystem: one that gets better with every contribution. We hope youβll be part of it.
Fixed a potential crash when clearing helper surfaces (#530)
Fixed a regression in v0.7.0 causing corrupted mipmaps on NVIDIA GPUs (#530)
Fixed a deadlock in Lunar: Silver Star Story on Windows 7 (#531)
Fixed several issues with depth buffer CPU access (#489, #529, #534, #542)
Games that use depth buffer CPU access now support antialiasing on all GPUs (#160, #524)
Fixed a bug related to shader constants that could cause various display glitches on AMD GPUs
Fixed the gamma ramp resetting to default after alt-tabbing in some cases (e.g. in Revenant)
Points and lines rendered by Direct3D now preserve their relative thickness when using resolution scaling (currently not supported with hardware vertex processing (T&L) or video memory vertex buffers) (#339)
Fixed a potential crash when using ResolutionScaleFilter=bilinear
Fixed blank loading screen in Heavy Gear 2 when in-game color depth is set to 32 bits (#398)
Fixed the configuration overlay's Reset/Import/Export buttons not applying to settings outside the current view
Fixed a bug in the runtime's handling of point primitives in execute buffers, which was causing crashes in Terracide (#433)
Gamma ramps are now also emulated in exclusive fullscreen mode, to work around missing native support on NVIDIA drivers
Fixed the configuration/stats overlays sometimes automatically hiding when they shouldn't
Fixed lower than expected presentation rate when using variable refresh rate technologies
Fixed Jane's F-15 sometimes switching to windowed mode in the menus
Fixed ResolutionScale and RenderColorDepth settings sometimes not applying to some frames
Added an experimental workaround for freezes on Windows 11 24H2 when using NVIDIA GPUs with single processor affinity (#387)
Fixed various stability issues (crashes and deadlocks)
Mouse sensitivity has been changed to be consistent with the desktop by default, use the new MouseSensitivity setting if experiencing problems (the native option reverts to the previous behavior)
Improved the fix for inaccurate cursor clipping in DPI unaware mode (#319)
Fixed missing ground textures in Carnivores on some GPUs (#320)
Fixed stuttering fullscreen presentation in some cases (#298)
Fixed a window clipping issue when moving dialog boxes in Close Combat 4
Fixed a performance issue with windowed fullscreen GDI presentation on some systems (#273)
Fixed oversized dialog windows (except non-client area) in some fullscreen games in DPI aware mode
Fixed mispositioned trackbar sliders in Red Alert 2 in DPI aware mode
Fixed ColorKeyMethod=alphatest not working on some textures in Carnivores
Fixed broken presentation after switching from fullscreen to windowed mode in some games
Fixed a deadlock when alt-tabbing in Star Trek: Armada with the config overlay open
Fixed hotkeys not working in some games that use DirectInput 8
Fixed presentation in some palettized fullscreen games, e.g. Carmen Sandiego's Great Chase Through Time
Fixed incorrect texture filtering applied in some cases, e.g. to trees in Carnivores
Fixed invisble network detection window in Empire Earth NeoEE (#251)
Updated configuration settings:
StatsRows: ddiusage was removed from the default value to improve performance
New configuration settings:
GdiStretchBltMode
VertexFixup
Update (October 6, 2024): The v0.5.2-17-g291e50ac and older builds in the DDrawCompat-v0.5.3-debug-previous-builds.7z asset were broken by the Windows 11 24H2 update. Patched builds have been added with the DDrawCompat-v0.5.3-debug-previous-builds-win11-24h2.7z asset to resolve the issue by backporting the following commit: 89b2a63. See diff.txt in the new builds for the exact changes. v0.5.2-18-g89b2a631 and newer builds are also included for completeness' sake. These were simply recompiled without source code changes.
Fixed inaccurate cursor clipping in DPI unaware mode
Fixed some display issues when using D3D9On12 with a RenderColorDepth setting not matching the application's color depth
When ForceD3D9On12 is off, Intel GPUs that use D3D9On12 by default will now try to use igd9trinity32.dll instead
Available surface formats now include all DX9 formats (#259)
Added support for Steam overlay in fullscreen mode
Updated configuration settings:
AltTabFix: merged keepwithmemnp into keepvidmem as a parameter, added noactivateapp option
RenderColorDepth: default value changed to 32
New configuration settings:
SurfacePatches
Update (October 6, 2024): This release was broken by the Windows 11 24H2 update. Patched builds have been added with the win11-24h2 suffix to resolve the issue by backporting the following commit: 89b2a63. See diff.txt in the new builds for the exact changes.
This release fixes some issues introduced in v0.5.0:
Fixed an issue that made DDrawCompat unusable with Intel GPU drivers (#255, #256)
Fixed the DisplayFilter=point setting not working as expected (#252)
Reverted a small fix that could cause a crash (#256)
Update (October 6, 2024): This release was broken by the Windows 11 24H2 update. Patched builds have been added with the win11-24h2 suffix to resolve the issue by backporting the following commit: 89b2a63. See diff.txt in the new builds for the exact changes.
Improved support for DPI unaware mode on high DPI displays
DirectDraw no longer forces the high DPI aware compatibility setting on the executable when it enters fullscreen mode
Broken tooltip fade animations are now replaced with the classic slide animations
DPI scaling no longer affects emulated hardware cursors, which resulted in oversized cursors
Fixed FlipToGDISurface result code when the GDI surface is already active (#204)
Maximum reported disk space is limited to 2GB to fix some applications getting a "not enough free disk space" error
Fixed an occasional crash caused by resolution scaling when alt-tabbing in Need for Speed III
Added support for depth fill blits on NVIDIA GPUs
Depth fills now work correctly with antialiased and resolution scaled depth buffers
Fixed hotkeys not working in some cases
Added a configuration file with default settings (commented out) in the Tools directory of the source code
Added a stats overlay (see new settings starting with the Stats prefix below)
Updated configuration settings:
AltTabFix: added keepvidmemnp option
ConfigHotKey: added alt and ctrl as synonyms for menu and control respectively
DisplayFilter: added bicubic, lanczos and spline options
PalettizedTextures: default value changed to off
RenderColorDepth: added appd8, appd10, 16d8, 16d10 and 32d10 options
New configuration settings:
ColorKeyMethod
ConfigRows
ConfigTransparency
CpuAffinityRotation
CrashDump
DepthFormat
DesktopResolution
DisplayAspectRatio
StatsColumns
StatsAggregateTime
StatsHotKey
StatsPosX
StatsPosY
StatsRows
StatsTransparency
StatsUpdateRate
SupportedDepthFormats
SupportedTextureFormats
TerminateHotKey
VertexBufferMemoryType
Update (October 6, 2024): This release was broken by the Windows 11 24H2 update. Patched builds have been added with the win11-24h2 suffix to resolve the issue by backporting the following commit: 89b2a63. See diff.txt in the new builds for the exact changes.
GDI redirection is now restricted to the main monitor in fullscreen mode, which fixes display issues with games not respecting surface pitch (#110)
Fixed conflicts with outdated versions of DbgHelp.dll shipping with some games
Fixed performance issues caused by D3DKMTWaitForVerticalBlankEvent on Windows 7 (#120)
Prevent Windows 7 from dynamically disabling desktop composition, which fixes main menu flickering in Rogue Spear (#126)
Added a partial workaround for a bug affecting NVIDIA drivers, where black texels were treated as transparent even when color keying was disabled for the texture stage
Fixed an issue with the application taskbar button sometimes remaining in the taskbar after exiting the application
Added a file-based configuration system and an in-game config overlay (see the wiki for details)
Removed the ReleaseWithDebugLogs build type, since LogLevel is now configurable
New configuration options:
AlignSysMemSurfaces
AlternatePixelCenter
AltTabFix
Antialiasing
BltFilter
ConfigHotkey
CpuAffinity
DesktopColorDepth
DisplayFilter
DisplayRefreshRate
DisplayResolution
DpiAwareness
FontSmoothing
ForceD3D9On12
FpsLimiter
FullscreenMode
LogLevel
PalettizedTextures
RemoveBorders
RenderColorDepth
ResolutionScale
ResolutionScaleFilter
SoftwareDevice
SpriteDetection
SpriteFilter
SpriteTexCoord
SupportedResolutions
TextureFilter
ThreadPriorityBoost
VSync
WinVersionLie
Update (October 6, 2024): This release was broken by the Windows 11 24H2 update. Patched builds have been added with the win11-24h2 suffix to resolve the issue by backporting the following commit: 89b2a63. See diff.txt in the new builds for the exact changes.
Fixed a deadlock when loading DDrawCompat on Windows 11 22H2
Update (October 6, 2024): This release was broken by the Windows 11 24H2 update. Patched builds have been added with the win11-24h2 suffix to resolve the issue by backporting the following commit: 89b2a63. See diff.txt in the new builds for the exact changes.
a safeguard (24141b4) added in v1.20.5 was too strict and would block requests from certain reverseproxies, specifically anything that adds X-Forwarded-HTTP-Version72224d2
replaced the connection:close band-aid added in v1.20.4 with a proper fix that doesn't make things slower behind reverseproxies
I've tried everything I can think of (with nginx as reverseproxy) and can't notice any difference in behavior, but please let me know if this breaks anything for you π
Make grid-highlight-same-text-color part of the predefined color schemes - (7854157)
Switch color scheme from Tools main menu - (c8c3b23)
Introduce global AppColorSchemes for managing SQL and grid colors, and sync both with the app's dark mode (still only on Windows) - (d313a59)
Sync active line color and brace highlight with the app's dark or light mode - (3510728)
Auto-switch to dark or light SQL colors in sync with the app's dark mode - (8a08e77)
Support dark mode, using MetaDarkStyle from OPM, and provide the 3 known custom settings: automatic, light and dark - (3f9e867)
Re-enable dropping files from file manager to "insert files to BLOB" dialog - (23fc9c0)
Upgrade DPI awareness to Per-Monitor v2, add TMainForm.FormChangeBounds as a replacement for the missing OnAfter/OnBeforeMonitorDpiChanged events - (9eab28e)
Re-enable menu item on list header context menu: "Toggle visibility of all columns" - (41169f7)
Support European umlauts/accents as \w (word char) in some regular expression areas - (304cd26)
Auto-uppercase keywords, data types and functions - (62cda84)
Recreate previous state of trigger after realizing the user edited code has errors - (e7e5e11)
Create a TSynEditMarkup descendant and use it for highlighting selected text occurrences - (8a667f2)
Create custom setting so the user may define a terminal app himself, and auto-detect terminal app if the setting is yet empty - (613e207)
Enable InnoSetup script for creating Windows installer - (317edcd)
Re-enable codepage => charset mapping using GetACP from DelphiCompat unit - (79e4654)
Re-enable ValidFilename function with platform specific lists of disallowed characters - (f3a0594)
Re-enable support for hyperlinks in message dialogues, and use TTaskDialog again for simple messages on Windows - (15eb52b)
Support portable mode with a portable.lock file in the app folder - (c528c5d)
ERangeError when editing text grid values which allow more than 2^31 chars, e.g. LONGTEXT - (42b5d52)
Set default value for ThemeIsDark for cases where AppleInterfaceStyle does not exist (= light mode) - (26ca75e)
Reload color scheme after auto-apply, reintroduce ThemeIsDark with a detection for Windows and macOS, use MetaDarkStyle units only on Windows - (b4afc3a)
Invalid typecast in List.Add(BaseForm.Components[i]), when running debug builds - (38faf57)
Wrong length of text detected (always 0) - (930a815)
Crash in data grid when switching to an empty table on ArchLinux - (e9b6835)
Next attempt to fix ERangeError crash in TBaseVirtualTree.UpdateVerticalRange - (c8e8bed)
Wrong ModalResult on "Replace all" button - (2367ac6)
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
Highlights in OpenWrt 25.12
OpenWrt 25.12.0-rc4 incorporates over 4300 commits since branching the previous OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0-rc4 for the full changelog.
General changes
The hardware requirements did not change significantly, most devices supported by OpenWrt 24.10 should also work with OpenWrt 25.12.
Switch package manager from opkg to apk
OpenWrt has transitioned from the traditional opkg package manager to apk (Alpine Package Keeper).
This change brings several advantages:
apk is still maintained, the OpenWrt opkg fork was not maintained any more.
apk supports most features of opkg. Only very few package names changed. The command line arguments of apk are different from the command line arguments of opkg.
For users migrating existing systems, an official opkg to apk cheatsheet is available to ease the transition and map common workflows.
Automatically rebuild firmware images with all currently installed packages
Preserve system configuration during upgrades
This dramatically simplifies upgrades: with just a few clicks in LuCI and a short wait, a custom firmware image is built and installed without manual intervention.
Shell history is preserved
Shell command history is now preserved across sessions by storing it in a RAM-backed filesystem.
Benefits:
Command history is no longer lost between logins
No unnecessary writes to flash storage by default
For users who prefer persistent history storage, this behavior can be changed by editing: /etc/profile.d/busybox-history-file.sh
β οΈ Note: Storing history on flash will increase write cycles and may impact flash endurance over time.
Integration of video feed
The OpenWrt video feed with Qt5 and UI applications is integrated by default.
Wi-Fi scripts in ucode
The wifi scripts were rewritten in ucode.
Target changes
Extend realtek target with support for more switch SoCs like 10G Ethernet switches.
Extend qualcommax target with support for ipq50xx and ipq60xx SoCs.
Added siflower target for Siflower SF21A6826/SF21H8898 SoCs
Added sunxi/arm926ejs subtarget for Allwinner F1C100/200s SoCs
Many new devices added
OpenWrt 25.12 supports over 2180 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 24.10.
Core components update
Core components have the following versions in 25.12.0-rc4:
Updated toolchain:
musl libc 1.2.5
glibc 2.41
gcc 14.3.0
binutils 2.44
Updated Linux kernel
6.12.66 for all targets
main packages:
cfg80211/mac80211 from kernel 6.18.7
hostapd master snapshot from August 2025
dnsmasq 2.91
dropbear 2025.89
busybox 1.37.0
In addition to the listed applications, many others were also updated.
Upgrading to 25.12
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
Sysupgrade from 23.05 to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed.
Bananapi BPI-R4: Interfaces eth1 was renamed to sfp-lan or lan4 and the interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration.
Scratch installs/upgrades
If you wish to start from scratch (always the safest, but also the most work), simply download the pre-built image from the downloads site or from the Firmware Selector to your device. Make sure to create and save a backup, then install the image using sysupgrade -n /tmp/firmware.bin or the LuCI Backup/Flash Firmware, being sure to set "Keep settings and retain the current configuration" to its off position. Restore or reconstruct your configuration using the contents of the backup as a template.
Attended Sysupgrade options
Attended Sysupgrade (ASU) allows you to build a custom image that retains all of your installed packages and their configuration transparently. You need to use one of the three ASU clients that interface with the ASU server to produce this custom image:
Firmware Selector - an online builder that requires you to manually supply it with the packages you wish to have installed. This package list is sent to the ASU server, and a new custom device image is created containing those packages. You may then download and install the image in LuCI Backup/Flash Firmware, but for this you would enable "Keep settings..."
Luci Attended Sysupgrade - the web interface to the ASU server. This tool allows you to choose a new OpenWrt version, then collects the names of the packages on your device and sends them up to the ASU server. LuCI ASU then downloads the created image directly to your device and allows you to install it, without having to do any of the bookkeeping tasks involved with using the Firmware Selector.
owut - a command line package that does the same job as LuCI ASU, but provides more diagnostics and better visibility into what's happening at the various steps before and during the build process.
Both the LuCI ASU app and owut are optional packages in 24.10, so if you have not installed them, they won't be there by default. Use either the LuCI Package Manager to install them, or you can do it from the command line with opkg:
Note that you can install one or the other, or both together, they are completely independent packages.
Upgrades with Firmware Selector
The Firmware Selector does an excellent job of searching through the thousands of available device configurations and getting you to the right place. But, some devices have several variants and possibly different image formats, so if you're unsure about which one you need or which device you're dealing with or anything else, go to the |Firmware Selector support thread and ask away.
Upgrades with LuCI Attended Sysupgrade
The LuCI web interface should be fairly self explanatory. Since you have fairly limited options there that should be pretty obvious, but if anything is unclear or you're unsure about something, go to the LuCI Attended Sysupgrade support thread and ask.
Upgrades with owut
If you choose to use owut, the fact that it's a command line program means you'll need a little more explanation regarding best practices. In any situation, it's always safe to do a check to see what's going on.
$ owut check --verbose --version-to 25.12
... a lot of output ...
This check should show you all the details of what this upgrade entails with regards to the packages available, and will point out any issues with package versions and so on.
Assuming the results of the check look good, you can simply do an upgrade next.
$ owut upgrade --verbose --version-to 25.12
... even more output ...
If you are unsure of anything you see in the check, during the upgrade, or simply have questions, jump on over to the owut support thread on the forum and ask.
Known issues
Users of Zyxel EX5601-T0 devices need to check their WAN interfaces as port was renamed from eth1 to wan.
The rockchip target does not build. rockchip will be included in the next release candidate again.
[p]Damage from HE grenades that explode mid-air near the ground will no longer be calculated as if they exploded on the ground.[/p][/*]
[p][/p][p]\[ SOUND ][/p]
[p]Various knife sound adjustments.[/p][/*]
[p][/p][p]\[ MISC ][/p]
[p]Performance optimizations for exploding chickens.[/p][/*]
[p]Fixed a map scripting bug where Entity.SetOwner wasn't accepting undefined.[/p][/*]
[p]Added a method for community maps to save modified user settings. Running 'host_writeconfig_with_prompt' will prompt the user for permission to save. If accepted, some of the modified settings (radar, viewmodel, safezones, etc) will be kept after the map exits.Β [/p][/*]
[p]Community maps are now restricted to a smaller list of allowed console commands. Use -disable_workshop_command_filtering to disable this filtering.[/p][/*]
[p][/p][p]\[ MAPS ][/p][p]Stronghold[/p]
[p]Updated to the latest version from the Community Workshop (Update Notes)[/p][/*]
This is a security release to address a vulnerability where form elements in page content could be used to trick more privileged users into making API requests.
We strongly advise that you update your instance if you allow untrusted users to create or edit pages.
Thanks to Joud Zakharia of zentrust partners GmbH for the discovery of this vulnerability, and thanks to Sven FaΓbender of zentrust partners GmbH for their responsible disclosure and great communication of this issue.
Additional Update Notices
Page Content - As of this release, most types of form content are now removed from page content on render. If you applied customizations which made use of in-page form content, you may now need to find alternative methods.
Full List of Changes
Updated application PHP dependencies.
Updated session-based API authentication to only be active for GET requests.
Updated page content filtering to remove many common form elements & attributes.
Updated translations with latest Crowdin changes. (#5997)
Release Highlights: Although GeForce Game Ready Drivers and NVIDIA Studio Drivers can be installed on supported notebook GPUs, the original equipment manufacturer (OEM) provides certified drivers for your specific notebook on their website. NVIDIA recommends that you check with your notebook OEM for recommended software updates for your notebook.
Game Ready for ARC Raiders: Headwind Update
This new Game Ready Driver provides the best gaming experience for the latest new games supporting DLSS 4 technology including ARC Raiders: Headwind Update and Arknights: Endfield. In addition, there is Game Ready support for Highguard which features DLSS Super Resolution.
Fixed Gaming Bugs
Total War: Three Kingdoms: Artifacts may be observed during gameplay when Screen Space Reflections is enabled [5745647]
Fixed General Bugs
Color banding observed with SDR content when Windows Automatic Color Management enabled [5754551]
Asus G14 may freeze on startup when Asus Ultimate Mode is enabled [5754849]
Β The Stable channel has been updated to 145.0.7632.26/.27 for Windows andMac as part of our early stable release to a small percentage of users. A full list of changes in this build is available in thelog.
You can find more details about early Stable releases here.
Interested in switching release channels? Β Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
The Stable channel has been updated to 144.0.7559.109/.110 for Windows/MacΒ andΒ 144.0.7559.109 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in theΒ Log.
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but havenβt yet fixed.
This update includes 1 security fix. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$3000][474435504] High CVE-2026-1504: Inappropriate implementation in Background Fetch API. Reported by Luan Herrera (@lbherrera_) on 2026-01-09
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
Interested in switching release channels? Find out howΒ here. If you find a new issue, please let us know byΒ filing a bug. TheΒ community help forumΒ is also a great place to reach out for help or learn about common issues.
26.1 Snapshot 5 (known as 26.1-snapshot-5 in the launcher) is the fifth snapshot for Java Edition 26.1, released on January 27, 2026.
Full changelog: https://minecraft.wiki/Java_Edition_26.1-snapshot-5
Firefox now allows you to customize your keyboard shortcuts to replace hard-to-type or hard-to-remember hotkeys, eliminate conflicts with other software, and create your preferred set. Access this experimental new feature by typing about:keyboard in the address bar and please share your feedback with us on Mozilla Connect!
Fixed
Resolved various issues with missing or impaired browser functionality when using XDG Base Directories on Linux. (Bug 2011300)
Fixed an issue causing excess passkey prompts to appear when logging into some sites. (Bug 2010919)
Fixed an issue that could lead to sites being incorrectly flagged as malicious by SafeBrowsing. (Bug 2010956)
Fixed an issue where player could get stuck on "Opening" when the graph worker thread malfunctioned. This happened on a few Windows 11 systems when opening files from Windows Search. We were unable to reproduce it, so root cause is unknown, likely an obscure Windows bug.