You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 25, 2026. It is now read-only.
I don't see any errors logged to Windows Event Viewer
Outcome
Windows 11
Element Version: v1.11.94
Operating system
No response
Application version
No response
How did you install the app?
No response
Homeserver
No response
Will you send logs?
Yes
Reacted by Rikard Teodorsson, Marco Jakobs, kongo09, André Rückbeil, Flandre5carlet, srn271, AnarcoPunkRJ, Conor Barry, RayManD, Alexander Votteler and 32 more
Same here, it kills Desktop apps which never can be restarted.
Have filed an issue in Element-Web 5 minutes ago : element-hq/element-web#29379
That version should be pulled immediately.
Reacted by MeIchthys, AnarcoPunkRJ, Conor Barry, ywh-jmorillo, Jordan Mills, Melisande Morel, plotpoint, srn271, Christian Woltering, Iceflower and 4 more
We pulled the .94 update. There is no need to patch given broken installs won't self fix as Node is crashing before our code gets to run the auto updater.
Hello cli-ish It IS patched already… just download it from https://element.io/
download
Von: Vincent Schneider ***@***.***>
Gesendet: Freitag, 28. Februar 2025 00:39
An: element-hq/element-desktop ***@***.***>
Cc: Rudolfo1967 ***@***.***>; Comment ***@***.***>
Betreff: Re: [element-hq/element-desktop] Crash after updating to v1.11.94 on
Windows (Issue element-hq/element-desktop#2161)
Same issue here, used the workaround by manual starting the old version.
When will this be patched?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.*Message ID: <element-hq/
***@***.***>
cli-ishcli-ish left a comment (element-hq/element-desktop#2161)
Same issue here, used the workaround by manual starting the old version.
When will this be patched?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.*Message ID: <element-hq/
***@***.***>
We pulled the .94 update. There is no need to patch given broken installs won't self fix as Node is crashing before our code gets to run the auto updater.
It wasn't caught by Nightlies because the Node update rollout was slow and only affected the nightly built just a handful of hours earlier - on which no one reported any issues.
We have made some remediations:
Pulled .94 installer & update nupkg
Announcement and a blog post detailing how to recover (reinstall .93 - no data loss)
Pinned the Node version to one which works 22.13.1
Switched from keytar to keytar-forked - maintained by a github staffer (and unpinned node)
Hoping to get #1947 on the agenda such that we can get away from unmaintained code but just ditching keytar would result in all existing sessions being thrown away, as it secures your session on disk at rest.
We also have a backburner project coined Saner Releases which aims to flip how we do releases, including running smoke tests on the release artifacts before publishing them to catch exactly this sort of stuff.
We do not have a QA team. The Web team is small (4 engineers most of the time and we often get pulled away to help other teams). Running manual tests on every update would be impossible given the vast amount of hardware and time one would need, automating it is difficult as many things lack test orchestration, like there's no test harness around Apple Keychain where we can mock things out to test keytar. So we do rely on users reporting from Nightlies in a wide range of environments to catch issues such as this.
Reacted by kosmos, Seth Milliken, Valentin Rieß, bblacher, Dudley, Murad "Gness Erquint" Beybalaev, Tomasz Wilczyński, Jean-Luc GARNIER, Davy Landman, Toine Hartman-Rijksen and 1 more
Unfortunately seems like Node doesn't care that a try-catch is useless to catch broken dependencies if the N-API is involved. We have done all that we can remediate against this issue.
Closing in favour of
element-hq/element-web#32278 which would give us more control by moving away from Node to something which lets us trap & recover from issues of this sort. #1947 which moves away from archived code.
The saner releases project which adds release artifact testing as much as possible.
The next Element Desktop release will go out on schedule.
Activity
jacotec commentedon Feb 27, 2025
Same here, it kills Desktop apps which never can be restarted.
Have filed an issue in Element-Web 5 minutes ago : element-hq/element-web#29379
That version should be pulled immediately.
arueckbeil commentedon Feb 27, 2025
Can confirm, the app no longer starts after the update, crashed immediately. I'm on Windows 11 24H2 (26100.3323)
FSG-Cat commentedon Feb 27, 2025
latest nightly on Windows 10 is also broken.
AnarcoPunkRJ commentedon Feb 27, 2025
Same, I cant open.
What should I do to be able to open it without losing my settings? Install the old version on top?
linuxmail commentedon Feb 27, 2025
Hi,
same for all Windows users at office.
jacotec commentedon Feb 27, 2025
Download the app again: https://element.io/download
All settings, rooms and (if there) the own config.json is still there. The download fortunately is 1.11.93.
But then refuse to say "update" when the popup occurs ;-)
linuxmail commentedon Feb 27, 2025
You can also use: https://packages.element.io/desktop/install/win32/x64/index.html
AnarcoPunkRJ commentedon Feb 27, 2025
Worked, thanks ^^
33 remaining items
t3chguy commentedon Feb 28, 2025
We pulled the
.94update. There is no need to patch given broken installs won't self fix as Node is crashing before our code gets to run the auto updater.https://element.io/blog/element-desktop-update-for-windows/
sascha-wi commentedon Feb 28, 2025
What a tremendous blunder...way to go.
Rudolfo1967 commentedon Feb 28, 2025
cli-ish commentedon Feb 28, 2025
It worked, thanks for the quick fix i am now on the version
1.11.93like thehttps://packages.element.io/desktop/update/win32/x64/ lists.
t3chguy commentedon Feb 28, 2025
Ultimately this bug was a horrible combination of things happening all at once.
22.14.022.14.0due to a Github runner-images update which we have no way of opting out ofWe have made some remediations:
.94installer & update nupkg.93- no data loss)22.13.1Hoping to get #1947 on the agenda such that we can get away from unmaintained code but just ditching keytar would result in all existing sessions being thrown away, as it secures your session on disk at rest.
We also have a backburner project coined Saner Releases which aims to flip how we do releases, including running smoke tests on the release artifacts before publishing them to catch exactly this sort of stuff.
We do not have a QA team. The Web team is small (4 engineers most of the time and we often get pulled away to help other teams). Running manual tests on every update would be impossible given the vast amount of hardware and time one would need, automating it is difficult as many things lack test orchestration, like there's no test harness around Apple Keychain where we can mock things out to test keytar. So we do rely on users reporting from Nightlies in a wide range of environments to catch issues such as this.
MichaMican commentedon Mar 3, 2025
@t3chguy You might also want to pull this version from the GitHub Releases
bblacher commentedon Mar 3, 2025
@MichaMican The GitHub releases don't include binaries, as this is a bug in the build system the GitHub releases don't need to be pulled.
t3chguy commentedon Mar 3, 2025
Yeah, only the windows version was pulled. Mac and Linux are still on 94
t3chguy commentedon Mar 3, 2025
Unfortunately seems like Node doesn't care that a try-catch is useless to catch broken dependencies if the N-API is involved. We have done all that we can remediate against this issue.
Closing in favour of
element-hq/element-web#32278 which would give us more control by moving away from Node to something which lets us trap & recover from issues of this sort.
#1947 which moves away from archived code.
The saner releases project which adds release artifact testing as much as possible.
The next Element Desktop release will go out on schedule.