Failed to locate Framework DLL Xojo 2025 r1

General
1

Hello everyone,

I have a desktop project build in Xojo 2025 r1 and in some windows 10 pcs it throws failed to locate framework dll. In some others it works fine. Windows are fully updated.
If I build the same project with Xojo 2024 r41 it work fine on windows pcs that xojo 2025 r1 has the problem.
Do you know what it might affect this?

Thank you

2

If all Windows 10 are fully updated then is strange.

There is an update to use OS ICU libraries that may cause problems with older Window 10 systems. Introduced with 2025r1

I hope someone can have another idea.

3

I’ve had some users who said they were fully up-to-date on Windows 10 that still reported this issue. Of course they could be incorrect (and this is likely in my mind) or have updates disabled for whatever reason, but I ended up running another build with 2024r4.2 to get them back up and running. The only commonality between them that I could discern is that all were non-US users.

1 Like
4

Hello and sorry for my late reply,

Thank you for your replies.
I asked ChatGPT and answered this. So I used Anthony’s method and used 2024r4.2 for them.

Supported Windows 10 Versions for Xojo 2025r1

  • IDE itself:
    • Windows 10 (build 1903 or newer), 64-bit only
    • Windows 11 (any supported build)
  • Desktop apps you build:
    • They run on Windows 10 (build 1903 or newer) – both 32- and 64-bit versions will work, provided the MSVC runtime is present.
    • Windows 11
    • (Windows Server 2019 build 1809+ also supported if you’re deploying to a server)
5

Maybe tied to paths with non-ascii chars and some bug in Xojo failed to consider it.

C:\Moja piękna aplikacja\XojoGUIFramework64.dll

I’ve seem in the past antivirus REMOVING files from Xojo installs too due to possible false positives.

Another point that came to my mind right now is the possibility that some paths having different codings and that causing issues (utf8 NFC or NFD). E.g. the word “ação” can have 2 different byte sequences: 0x61 0xC3 0xA7 0xC3 0xA3 0x6F (NFC) or 0x61 0x63 0xCC 0xA7 0x61 0xCC 0x83 0x6F (NFD)
I remember issues in the past due to mixing files created on Mac or Windows using accented letters and those systems encoding the names differently. If I do recall correctly, Mac was using NFD and Windows NFC, and the system wasn’t finding the file.

1 Like
6

This makes sense because we are in Greece for example. We informed our customers to move to Windows 11 until 14/10/2025 so we hope to solve it this way.

1 Like
7

Maybe from some version and up, Windows file system calls started to consider both NFC and NFD forms equivalent internally, I don’t know, and/or fixed some bug for some non Latin alike alphabets as Greek.

Be sure the users have a Windows 10 >= 10.0.18362 , preferably 10.0.19045 the last one.

1 Like