This is an automated email from the ASF dual-hosted git repository. leginee pushed a commit to branch win10-msvc-trunk in repository https://gitbox.apache.org/repos/asf/openoffice.git
commit 78c9e3c8b64f48972ff0f4b0bfd78754af55c315 Author: Peter Kovacs <[email protected]> AuthorDate: Tue Aug 25 15:13:18 2026 +0200 external: point the vcredist README at the v14 runtime The README told builders to fetch the redistributable from https://www.microsoft.com/en-us/download/details.aspx?id=26368, which Microsoft's own page lists as the Visual Studio 2008 SP1 download -- and 9.0.30729.5677 is exactly what was sitting in external/vcredist/ and shipping in the install set. Binaries built with a modern toolset import VCRUNTIME140.dll, VCRUNTIME140_1.dll, MSVCP140.dll and the UCRT. None of those are in the 2008 package, and the MSI ships no CRT of its own -- there are no vcruntime*/msvcp*/api-ms-win-crt-* rows in File.idt for either architecture. So the installer has been installing a runtime the office cannot use, and only machines that happened to already carry the v14 runtime could start it. A clean machine could not. Now pinned to the v14 permalinks, which always resolve to the current release: x86 https://aka.ms/vc14/vc_redist.x86.exe x64 https://aka.ms/vc14/vc_redist.x64.exe with a note that they have to be renamed to vcredist_*.exe, since configure, external/prj/d.lst, scp2 and desktop/win32/source/setup/setup.cpp all spell them that way. This also settles the minimum Windows version, which is not an independent choice: the current v14 redistributable "supports only the following operating systems: Windows 10 and 11, Windows Server 2016, 2019, 2022, and 2025". Shipping the runtime the binaries need sets the floor at Windows 10. The .exe files themselves stay out of git (.gitignore:71); only this instruction to builders is tracked, which is why it was able to be wrong for so long. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01VrM7EMKgiuyVcCUe9nSbZR --- main/external/vcredist/README | 47 ++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 44 insertions(+), 3 deletions(-) diff --git a/main/external/vcredist/README b/main/external/vcredist/README index a067f7f83d..1c81afe604 100644 --- a/main/external/vcredist/README +++ b/main/external/vcredist/README @@ -1,3 +1,44 @@ -For windows we need the VC redistributables. -Copy vcredist_x86.exe and vcredist_x64.exe in this directory. -You can download them from https://www.microsoft.com/en-us/download/details.aspx?id=26368 +For Windows we need the Visual C++ Redistributables. + +Copy them into this directory as: + + vcredist_x86.exe + vcredist_x64.exe + +Note the names: Microsoft ships these as vc_redist.x86.exe / vc_redist.x64.exe, +so they have to be renamed. configure, external/prj/d.lst, scp2 and +desktop/win32/source/setup/setup.cpp all refer to the vcredist_* spelling. + +Which ones +---------- +The Visual C++ v14 Redistributable (Visual Studio 2015-2022), latest version: + + x86 https://aka.ms/vc14/vc_redist.x86.exe + x64 https://aka.ms/vc14/vc_redist.x64.exe + +These are permalinks that always resolve to the current v14 release. + +The rule is that the redistributable must be the same version as, or newer +than, the MSVC build tools used to compile the office. A v14 redistributable +covers anything built with the toolsets in Visual Studio 2017, 2019, 2022 or +2026, because they all share one runtime. + +Do NOT use the Visual C++ 2008 redistributable. This file used to point at +https://www.microsoft.com/en-us/download/details.aspx?id=26368, which is the +Visual Studio 2008 SP1 download (version 9.0.30729). Binaries built with a +modern toolset import VCRUNTIME140.dll, VCRUNTIME140_1.dll, MSVCP140.dll and +the UCRT; none of those are in the 2008 package, and the MSI ships no CRT of +its own. Installing with the 2008 redistributable produces an office that +cannot start on a machine which does not already happen to have the v14 +runtime. + +Supported Windows versions +-------------------------- +The current v14 redistributable supports Windows 10 and 11, and Windows Server +2016 / 2019 / 2022 / 2025 -- it does not install on anything older. That is +what sets the minimum Windows version for a build made with a modern toolset; +it is not an independent choice. + +If an older floor is ever needed, an older v14 servicing release has to be +pinned here explicitly, and its own supported-OS list checked -- the v14 line +has raised its floor over time.
