Bug 166947 - Windows Arm64 (Aarch64) MSI installer for 25.2.4 seems invalid
Summary: Windows Arm64 (Aarch64) MSI installer for 25.2.4 seems invalid
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
25.2.4.3 release
Hardware: ARM Windows (All)
: high normal
Assignee: Christian Lohmaier
URL:
Whiteboard: target:26.2.0 target:25.8.1 target:25...
Keywords:
: 167256 167595 167776 (view as bug list)
Depends on:
Blocks: Installer-Windows
  Show dependency treegraph
 
Reported: 2025-06-10 20:27 UTC by cybermonktitan
Modified: 2025-09-11 14:26 UTC (History)
12 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cybermonktitan 2025-06-10 20:27:30 UTC
Description:
I downloaded the Windows (Aarch64) build of LO 25.2.4. The downloaded MSI file matches the SHA256 listed in the online info. When I doubleclick the MSI, Windows Installer pops up in its initializing stage ("Preparing to install..."), then gives a big warning: "This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package."

The Windows (Aarch64) build for LO 24.8.7 does install correctly and I can start Writer without issues]

This is on a Microsoft Surface with a Snapdragon X Plus CPU, running Windows 11.

Additional testing showed that LO 25.2.3 was not affected (I successfully upgraded), but the current alpha (25.8.0.0alpha1 dated 2025-05-19T17:15:30Z) also fails with the same error.

Steps to Reproduce:
1. Download installer for 25.2.4 on a Windows 11 Arm64 machine
2. Start the installer

Actual Results:
Installer can't be started (beyond standard Windows Installer initialization).

Expected Results:
Installation proceeds as normal.


Reproducible: Always


User Profile Reset: No

Additional Info:
-
Comment 1 SML 2025-06-12 11:31:18 UTC
The same is true for me - that's why I created an account here to report this bug.
Comment 2 Tim 2025-06-17 13:15:17 UTC
I have exactly the same issue.
Comment 3 Roman Kuznetsov 2025-06-19 18:18:17 UTC
Cloph, any ideas here?
Comment 4 V Stuart Foote 2025-06-27 01:25:55 UTC
*** Bug 167256 has been marked as a duplicate of this bug. ***
Comment 5 V Stuart Foote 2025-06-27 01:30:13 UTC
Confirmed with multiple duplicate reports, Package could not be opened. 
MSI error 1620.
Comment 6 Mike Kaganski 2025-06-27 05:06:51 UTC Comment hidden (off-topic)
Comment 7 V Stuart Foote 2025-06-30 14:50:12 UTC
Given related bug 166803 is there an issue on the ARM Windows builds with the Vulkan test fallback.  Folks with existing configs get a working result (but missing icon) while folks doing a new install get squat. 

Needs more testing, but issue is probably not the MSI, but with our rendering testing and fallback?

@Mike, sorry to bump you with this again.
Comment 8 Kihan 2025-07-01 07:08:56 UTC
My Samsung Galaxy book Go with Sanpdragon gen7 shows same message. It is not working on installation.
Comment 9 Gabriel Jones 2025-07-12 01:14:47 UTC
Lenovo X13s, Microsoft Windows 11 Pro Insider Preview 10.0.27898 N/A Build 27898, same issue on preview msis also.
Comment 10 V Stuart Foote 2025-07-20 03:00:54 UTC
*** Bug 167595 has been marked as a duplicate of this bug. ***
Comment 11 Nico 2025-07-26 19:40:25 UTC
I can confirm as of now that the error persists when trying to launch the installer version 25.2.5.2 in a Windows 11 Pro ARM (latest update as of now) VM in Parallels Desktop on an M1 Mac.
Comment 12 Saburo 2025-08-02 09:17:29 UTC
*** Bug 167776 has been marked as a duplicate of this bug. ***
Comment 13 JT 2025-08-02 10:49:44 UTC Comment hidden (me-too)
Comment 14 radek.reif 2025-08-03 07:02:11 UTC Comment hidden (me-too)
Comment 15 MarcusBond 2025-08-13 03:06:45 UTC Comment hidden (spam)
Comment 16 Christian Lohmaier 2025-08-14 13:01:42 UTC
found the problem, specifying that the installation set is an ARM64 one makes windows unhappy, no idea why that fails, so the workaround for now is to just claim it is a x86_64 installation set...

I'll do rebuilds of 25.2.5 with that change...
Comment 17 alex 2025-08-15 05:30:46 UTC
(In reply to Christian Lohmaier from comment #16)
> found the problem, specifying that the installation set is an ARM64 one
> makes windows unhappy, no idea why that fails, so the workaround for now is
> to just claim it is a x86_64 installation set...
> 
> I'll do rebuilds of 25.2.5 with that change...

Good work finding - if you can advise where/when rebuilds will be, happpy to help with testing to confirm.
Comment 18 Mike Kaganski 2025-08-15 05:49:44 UTC
Do we have a full installation log of the failure? I don't see it neither here, nor in the three duplicates so far. And it could be possible, that we have some component in the package, that conflicts with the target platform, not some generic MS bug.
Comment 19 Guido Walter 2025-08-15 10:10:14 UTC
You mean something like this? 

=== Verbose logging started: 15/08/2025  12:07:57  Build type: SHIP UNICODE 5.00.10011.00  Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (88:8C) [12:07:57:584]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (88:8C) [12:07:57:584]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (88:AC) [12:07:57:613]: Resetting cached policy values
MSI (c) (88:AC) [12:07:57:613]: Machine policy value 'Debug' is 0
MSI (c) (88:AC) [12:07:57:613]: ******* RunEngine:
           ******* Product: LibreOffice_25.2.5_Win_aarch64.msi
           ******* Action: 
           ******* CommandLine: **********
MSI (c) (88:AC) [12:07:57:614]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (88:AC) [12:07:57:643]: Access database with Impersonation
MSI (c) (88:AC) [12:07:57:643]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi' against software restriction policy
MSI (c) (88:AC) [12:07:57:643]: SOFTWARE RESTRICTION POLICY: C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi has a digital signature
MSI (c) (88:AC) [12:07:57:939]: SOFTWARE RESTRICTION POLICY: C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (88:AC) [12:07:57:953]: Cloaking enabled.
MSI (c) (88:AC) [12:07:57:953]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (88:AC) [12:07:57:956]: End dialog not enabled
MSI (c) (88:AC) [12:07:57:956]: Original package ==> C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi
MSI (c) (88:AC) [12:07:57:956]: Package we're running from ==> C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi
MSI (c) (88:AC) [12:07:57:966]: APPCOMPAT: Compatibility mode property overrides found.
MSI (c) (88:AC) [12:07:57:968]: APPCOMPAT: looking for appcompat database entry with ProductCode '{B5250BF5-6BE3-415A-8924-2B11FD0CC494}'.
MSI (c) (88:AC) [12:07:57:969]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (88:AC) [12:07:57:973]: MSCOREE not loaded loading copy from system32
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi
MSI (c) (88:AC) [12:07:57:978]: Note: 1: 1708 
MSI (c) (88:AC) [12:07:57:978]: Product: LibreOffice 25.2.5.2 -- Installation failed.

MSI (c) (88:AC) [12:07:57:978]: Windows Installer installed the product. Product Name: LibreOffice 25.2.5.2. Product Version: 25.2.5.2. Product Language: 1033. Manufacturer: The Document Foundation. Installation success or error status: 1620.

MSI (c) (88:AC) [12:07:57:984]: MainEngineThread is returning 1620
=== Verbose logging stopped: 15/08/2025  12:07:58 ===
Comment 20 Mike Kaganski 2025-08-15 10:28:29 UTC
(In reply to Guido Walter from comment #19)

Yes, thanks; just called with /l*vx to enable extra-verbose logging:

> msiexec /i "c:\path\to\LibreOffice.msi" /l*vx c:\libreoffice-install.log
Comment 21 Guido Walter 2025-08-15 10:33:55 UTC
(In reply to Mike Kaganski from comment #20)
> (In reply to Guido Walter from comment #19)
> 
> Yes, thanks; just called with /l*vx to enable extra-verbose logging:
> 
> > msiexec /i "c:\path\to\LibreOffice.msi" /l*vx c:\libreoffice-install.log

It outputs the same...

=== Verbose logging started: 15/08/2025  12:33:04  Build type: SHIP UNICODE 5.00.10011.00  Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (E0:28) [12:33:04:741]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (E0:28) [12:33:04:741]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (E0:58) [12:33:04:763]: Resetting cached policy values
MSI (c) (E0:58) [12:33:04:763]: Machine policy value 'Debug' is 0
MSI (c) (E0:58) [12:33:04:763]: ******* RunEngine:
           ******* Product: LibreOffice_25.2.5_Win_aarch64.msi
           ******* Action: 
           ******* CommandLine: **********
MSI (c) (E0:58) [12:33:04:765]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (E0:58) [12:33:04:788]: Access database with Impersonation
MSI (c) (E0:58) [12:33:04:788]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi' against software restriction policy
MSI (c) (E0:58) [12:33:04:791]: SOFTWARE RESTRICTION POLICY: C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi has a digital signature
MSI (c) (E0:58) [12:33:05:066]: SOFTWARE RESTRICTION POLICY: C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (E0:58) [12:33:05:079]: Cloaking enabled.
MSI (c) (E0:58) [12:33:05:083]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (E0:58) [12:33:05:086]: End dialog not enabled
MSI (c) (E0:58) [12:33:05:089]: Original package ==> C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi
MSI (c) (E0:58) [12:33:05:090]: Package we're running from ==> C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi
MSI (c) (E0:58) [12:33:05:100]: APPCOMPAT: Compatibility mode property overrides found.
MSI (c) (E0:58) [12:33:05:102]: APPCOMPAT: looking for appcompat database entry with ProductCode '{B5250BF5-6BE3-415A-8924-2B11FD0CC494}'.
MSI (c) (E0:58) [12:33:05:103]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (E0:58) [12:33:05:110]: MSCOREE not loaded loading copy from system32
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
C:\Users\GuidoWalter\Downloads\LibreOffice_25.2.5_Win_aarch64.msi
MSI (c) (E0:58) [12:33:05:115]: Note: 1: 1708 
MSI (c) (E0:58) [12:33:05:115]: Product: LibreOffice 25.2.5.2 -- Installation failed.

MSI (c) (E0:58) [12:33:05:119]: Windows Installer installed the product. Product Name: LibreOffice 25.2.5.2. Product Version: 25.2.5.2. Product Language: 1033. Manufacturer: The Document Foundation. Installation success or error status: 1620.

MSI (c) (E0:58) [12:33:05:124]: MainEngineThread is returning 1620
=== Verbose logging stopped: 15/08/2025  12:33:05 ===
Comment 22 Mike Kaganski 2025-08-15 11:19:46 UTC
https://learn.microsoft.com/en-us/windows/win32/msi/using-64-bit-windows-installer-packages

> For 64-bit packages on the Arm64 platform, the Windows Installer database schema
> must be 500 or higher.


We have it 200:
https://opengrok.libreoffice.org/xref/core/solenv/bin/modules/installer/windows/msiglobal.pm?r=25d62325f320ba75a2b64584fe1d5d98c18275f1#553
Comment 23 Mike Kaganski 2025-08-15 11:47:42 UTC
Since I don't have an Arm box to test.

Two ways to test if fixing MSI version is the correct thing to do:

1. Use free version of InstEd! app http://www.instedit.com/ (it is old, but that shouldn't matter) to open and edit the MSI - in the application, the place to change is Tables->Summary Info->Schema (200 should be replaces with 500);

or if you have Visual studio installed:

2. Open Visual Studio Developer command prompt, and run

> msiinfo C:\Downloads\LibreOffice_25.2.5_Win_aarch64.msi -g 500

===

Hopefully, after that, the installer should work.
Comment 24 Guido Walter 2025-08-15 11:57:50 UTC
(In reply to Mike Kaganski from comment #23)
> Since I don't have an Arm box to test.
> 
> Two ways to test if fixing MSI version is the correct thing to do:
> 
> 1. Use free version of InstEd! app http://www.instedit.com/ (it is old, but
> that shouldn't matter) to open and edit the MSI - in the application, the
> place to change is Tables->Summary Info->Schema (200 should be replaces with
> 500);
> 
> or if you have Visual studio installed:
> 
> 2. Open Visual Studio Developer command prompt, and run
> 
> > msiinfo C:\Downloads\LibreOffice_25.2.5_Win_aarch64.msi -g 500
> 
> ===
> 
> Hopefully, after that, the installer should work.

Correct, after changing the Schema to 500 the installer works again.
As I'm new here and don't know who is who, can someone in charge of the build pipeline just change that and I think we all would be happy :-)
Comment 25 Mike Kaganski 2025-08-15 12:12:47 UTC
Note that it is safe to just set it to 500 unconditionally. Windows Installer 5.0 was released with (and became part of) Windows 7. We have now dropped support for anything below Windows 10.
Comment 26 Commit Notification 2025-08-18 10:31:20 UTC
Christian Lohmaier committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/918c409e63e72447a351344e9bca394275fe7508

tdf#166947 fix windows installation sets for aarch64

It will be available in 26.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 27 Christian Lohmaier 2025-08-18 10:56:22 UTC
Thanks for the additional findings re the scheme version bump - will have bandaid fixes for the rebuild, and try to do a proper one for master/future releases.
Comment 28 Guido Walter 2025-08-18 14:16:49 UTC
(In reply to Commit Notification from comment #26)
> Christian Lohmaier committed a patch related to this issue.
> It has been pushed to "master":
> 
> https://git.libreoffice.org/core/commit/
> 918c409e63e72447a351344e9bca394275fe7508
> 
> tdf#166947 fix windows installation sets for aarch64
> 
> It will be available in 26.2.0.
> 
> The patch should be included in the daily builds available at
> https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
> information about daily builds can be found at:
> https://wiki.documentfoundation.org/Testing_Daily_Builds
> 
> Affected users are encouraged to test the fix and report feedback.

Just to clarify things: If you set architecture of the installer to Arm64 and Schema to 500 it works. As Microsoft states in https://learn.microsoft.com/en-us/windows/win32/msi/using-64-bit-windows-installer-packages:

For 64-bit packages on the Arm64 platform, the Windows Installer database schema must be 500 or higher.

So setting the architecture to x64 might work now, but could bite back later, as we might an up with incorrect reg entries or wrong path for files. I Don't say this will happen, but it could.

As schema 500 uses windows installer version 5 which was introduced with Windows 7 (as Mike Kaganski already stated), this is still safe - at least from an ARM64 point of view as this covers only Windows 10 / 11. 

So just to leave my opinion on this and not to be pain in the ***, I would suggest to change the schema version and leave the architecture as ist was on Arm64.
Comment 29 Commit Notification 2025-08-18 14:25:52 UTC
Christian Lohmaier committed a patch related to this issue.
It has been pushed to "libreoffice-25-8":

https://git.libreoffice.org/core/commit/342ecfbd79e8b371f4ab8b3f58ec6c04b1a0c589

tdf#166947 properly fix windows installation sets for aarch64

It will be available in 25.8.1.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 30 Commit Notification 2025-08-18 14:25:57 UTC
Christian Lohmaier committed a patch related to this issue.
It has been pushed to "libreoffice-25-2":

https://git.libreoffice.org/core/commit/f782b13a271c127c84799829b6a32fcf28a5cd35

tdf#166947 properly fix windows installation sets for aarch64

It will be available in 25.2.6.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 31 Christian Lohmaier 2025-08-18 14:45:44 UTC
(In reply to Guido Walter from comment #28)
> […]
> So setting the architecture to x64 might work now, but could bite back
> later, as we might an up with incorrect reg entries or wrong path for files.
> I Don't say this will happen, but it could.

Just FYI: that is what the packages up until 25.2.4 did use/until I changed it to Arm64 while fixing the overall installset creation on a native windows arm machine, so the replaced 25.2.5 and the upcoming 25.8.0 / 25.2.6 will be the first ones that properly identify as Arm64 packages.
 
> […]
> So just to leave my opinion on this and not to be pain in the ***, I would
> suggest to change the schema version and leave the architecture as ist was
> on Arm64.

No worries, that's what I ended up doing in the end - I already had the packages rebuilt with the old x86_64 identifier (since that was known to work for 25.2.4 and earlier) – but thanks to it being possible to rewrite the installation info without doing full rebuilds once more I did just that for 25.2.5 (rc2/final) and 25.8.0 (rc4/to-be-final). That also simplifies other unrelated stuff since the buildID/git-hash can stay the same as with the other platforms/architectures.

https://downloadarchive.documentfoundation.org/libreoffice/old/25.2.5.2/win/
https://downloadarchive.documentfoundation.org/libreoffice/old/25.8.0.4/win/

the aarch64_broken dir contains the originally uploaded file (that had old schema, but use Arm64) - the aarch64 dir contains the fixed versions (note that it is possible that some mirrors that sync very infrequently still carry the broken file, so if doubt compare with the checksum by using the "Details" link, e.g. https://downloadarchive.documentfoundation.org/libreoffice/old/25.8.0.4/win/aarch64/LibreOffice_25.8.0.4_Win_aarch64.msi.mirrorlist 
or manually pick a mirror that's current (see e.g. https://download.documentfoundation.org/mirmon/ )
Comment 32 Commit Notification 2025-08-18 14:54:03 UTC
Christian Lohmaier committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/816bd7171742163911986a77812a3e8151f6fe10

tdf#166947 properly fix windows installation sets for aarch64

It will be available in 26.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 33 Buovjaga 2025-09-11 12:55:19 UTC
Can this be closed as fixed?
Comment 34 cybermonktitan 2025-09-11 14:26:44 UTC
Just tested the latest installer (25.8.1.1). It runs as native Arm64, and the installed LO Writer binaries also run as native Arm64. Looks all good!

Thanks for finding and fixing!