Good day everybody,
i have a problem to getting to run a x64 build on windows 7 x64.
I can’t start the app and the following 2 error messages do appear:
1st:
The procedure entry point CreateFile2 could not be located in the dll KERNEL32.dll.
2nd:
Failed to load plugin GZipx64.dll.
The specified procedure could not be found.
So, maybe better to build x32 for compability in future?
CreateFile2 requires Windows 8.
Please upgrade the Windows or use an older Xojo version.
The only weird thing my app does it’s creating a textfile on the users pc.
And i do not force gzip to work in my app.
I changed from xojo 2022 to 2024 recently, before all my apps worked on win 7.
I am not happy with this at all.
We were debating this for years now, but Xojo needed to make choices at one point. And Win7 is dead now. People running it are running a mummy computer. And yes, I have few clients using it and Win8.x too (also becoming affected). A minority, but they exist.
Desktop apps built with Xojo will run on any computer that meets the following requirements.
| OS | Requirements |
|---|---|
| macOS | 10.14 (Mojave) - 15 (Sequoia) |
| Windows | 10 (build 1903+) - 11 |
| Linux | Linux Mint 20 or later, CentOS 7.0 or later, Current LTS versions of Ubuntu, Debian 6.0 or later, OpenSUSE 11.3 or later, Fedora 13 Desktop or later |
| Raspberry Pi | Pi 2 or later running Raspberry Pi OS 11 (Bullseye) |
I think that the last Windows 7 capable more stable IDE (but also with issues) was 2022r3.2
Xojo 2022r3.2 ist the last version supporting Windows 7: System requirements for 2022r3 — Xojo documentation
Starting with Xojo 2023r1 built Desktop Apps require Windows 8.1: System requirements for 2023r1 — Xojo documentation
Thank you a lot , Jürg,
and to Rick too.
Not easy to bear…i still can run vb6 apps on win 11.. 
Because they use old APIs and capabilities. They are not supposed to be prepared to handle Unicode and use UTF-8 to say the minimum, for example.
You know, so many things changed since 1998.
Xojo also is suffering of the same VB6 old GUI design syndrome, because it still uses old UI APIs for their very small set of UI controls, but newer than VB6 for sure, probably all Wide and VB6 probably is Ansi, but they have plans to update it at some point as there is an entry on the roadmap for that.