Electron 44.8.0

Electron 44.8.0 arrived on October 16, 2026, a patch release on the 44 line with exactly one new feature and four fixes. Let's not get carried away: this is maintenance, not a milestone. But two of the fixes address bugs that leave a running app in a broken state until restart, and those are worth the upgrade on their own.

The One New Feature Is Linux Only

Notification action buttons now work on Linux. Windows and macOS have supported notification actions for a while, so this closes a platform gap for apps that rely on reply or dismiss buttons. If you do not ship on Linux, nothing changes for you here.

The Fixes That Actually Matter

• Network fetches no longer die permanently. net.fetch and session.fetch used to fail with net::ERR_FAILED and stay failed after the Network Service process restarted. The failure was sticky, so long-running apps could lose all outbound requests until relaunch. The fix is backported to 42, 43, and 45.
• Utility process messages stop disappearing. Messages posted through process.parentPort.postMessage() just before the child exited were dropped. That is the exact window shutdown handshakes run in, so the bug showed up as missing completion events. Backported to 42, 43, and 45.
• Fullscreen state on Windows is current again. win.isFullScreen() could return a stale value inside fullscreen events, which broke layout decisions that read the flag during the event.
• The Windows cursor is back over native dialogs. The mouse pointer disappeared over native dialogs in certain scenarios.

The Part With Real Risk

Under "Other Changes," the release moves Chromium to 152.0.7977.167 and Node.js to v24.22.0, alongside backported Chromium and V8 fixes. Those embeds are where regressions usually hide in an Electron patch. A Chromium point release can change rendering, media decoding, or network stack behavior in ways the release notes never enumerate. If your app does anything unusual with custom protocol handlers, service workers, or media pipelines, retest before shipping.

There are no API removals or deprecations in this build, and no breaking changes are listed. The version is a drop-in for anyone already on 44.x.

Upgrade Advice

If you are on 44.4.x or earlier, take 44.8.0. The sticky network failure alone justifies it, since a single Network Service crash currently takes out fetch for the rest of the session. If you are pinned to 42 or 43 and cannot move, the fetch and utility process fixes were backported to both lines, so take the next patch there instead of jumping majors. Run your smoke tests after the Chromium bump, then ship.