NEWS: Windows 7/8/8.1 are no longer supported from v2.12.7

[Nuubie]

Okay this was big roundabout waste of time.I just updated 2.11.11 to 2.12.15 considering I only installed this application last week initially and I received the following error.

Joplin.exe - Entry Point Not Found
The procedure entry point DiscardVirtualMemory could not be located in the dynamic link library KERNEL32.dll

Obviously I Checked here, Nothing! I Check the web site, Nothing, I Check for supported versions of windows and the only information provided is "Windows (32 and 64)". I go to Github and look for this issue, Nothing!

I try reinstall and you have me running chkdsk and sfc /scannow to be sure my kernel32.dll is okay.

I go to the effort of setting up discord and look in #DEV #Main, Nothing.
I post the Issue there thinking something might be wrong with my computer or the application.

I continue looking at the problem and finally seen the procedure ' DiscardVirtualMemory' from Microsoft and that it's only available in:

Minimum supported client Windows 8.1 Update [desktop apps | UWP apps]

I revert to older version and I'm looking all over to see which OS is supported?? and you made this extremely easy to find among all the 300 revisions.

v2.12.7 (Pre-release) - 2023-07-13T12:55:31Z🔗
Improved: Updated packages css-loader (v6.8.1)
Improved: Upgrade to Electron 25. Note that it means that Windows 7/8/8.1 are no longer supported (#8451) (#8258 by Henry Heino)
Fixed: Fix issue with Apple Silicon version (#8452) (#6052 by Noah Nash).

Back to Discord to inform you that.

Please don't offer updates not supported or post information in News otherwise I would not have come here and wasted everyone's time. Improved: Upgrade to Electron 25 doesn't mean anything to anybody that isn't a developer or doesn't know what it is and as you can see why some people might skip this in the effort to save themselves some TIME.

Unpopular but I'm still on windows 7.

[tomasz86]

It would indeed be nice to be more specific about the supported OS. For example, in addition to no Windows version being specified, the official website still claims compatibility with "Windows (32 and 64-bit)" (see https://joplinapp.org/help/#desktop-applications) even though 32-bit releases have been broken for years (and require a cumbersome manual fix buried inside https://github.com/laurent22/joplin/issues/4649 to even run).

[Marph]

@Nuubie

Joplin.exe - Entry Point Not Found
The procedure entry point DiscardVirtualMemory could not be located in the dynamic link library KERNEL32.dll

Obviously I Checked here, Nothing!

A search for the error message should have yielded this comment and an explanation in the next comment:

What's new in Joplin 2.11

Upon seeing this post, I started up Joplin desktop on Windows 7 64-bit to see what version I was running. Upon startup, it prompted me to download a new update, so I told it to go ahead. It retrieved 2.12.7. After it finished installing, I clicked the start option, and now Joplin will not start: "The procedure entry point DiscardVirtualMemory could not be located in the dynamic link library KERNEL32.dll." I looked at the release notes, and I don't see anything that says Joplin is no longer…

[guy-rouillier]

I use Joplin on Windows, Linux and Android. My main system is Windows 7, so I'm stuck on version 2.11.11. (I see some posts that suggest I could move up to 2.12.5, but nothing later.) I'm concerned that my Android phone may upgrade to a version of Joplin that will be incompatible with what I'm using on Windows 7. We've already encountered an instance of incompatible sync versions here:

ATTENTION: Sync version has been changed in 2.3

I have a problem with the update. I am using windows version and a webdav personal server to sync my notes. I am receiving this message: Error The sync target could not be upgraded due to an error. For support, please copy the complete content of this page and paste it in the forum: https://discourse.joplinapp.org/ The full error was: PUT locks/exclusive_desktop_86845757cb4a43808ee1af2fd4f7e3c2.json: Unknown error 2 (412): <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//…

I have some degree of control over the Joplin version on Linux and Windows, but Android updates itself. Is there anything I can do to prevent Android from updating Joplin to a version with incompatible sync? I suppose I need to lock it down to a particular version.

[tomasz86]

@guy-rouillier

Is there anything I can do to prevent Android from updating Joplin to a version with incompatible sync?

If installed through Play Store, there is a per-app option to disable auto-updates in the top-right 3-dot menu. The same is true for F-Droid.

[guy-rouillier]

@tomasz86

per-app option to disable auto-updates in the top-right 3-dot menu

Thank you! I'm going to bookmark this so I can use it once the Joplin Android release becomes incompatible with Windows 7. I'm holding off for now so I can capture as many Joplin updates as possible before then.