Description: there haven't been win versions in 'daily' for some time, now there are two in 'https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF-nomerge/' but both complain about missing vcruntime140_1.dll when trying to start Steps to Reproduce: 1. load and install LO 7.0 x64 in windows 7 from abovementioned location, 2. try to start, 3. 'Das Programm kann nicht gestartet werden, da VCRUNTIME140_1.dll auf dem Computer fehlt. Installieren Sie das Programm erneut, um das Problem zu beheben.' 4. new install same result, Actual Results: now actual win ver. avaiable, Expected Results: actual win ver. available Reproducible: Always User Profile Reset: No Additional Info: affects 2020-03-07_00.57.40/ and 2020-03-07_05.05.22/
Known infra issue with Tinderbox build system. Being worked on. Meanwhile the 'no-merge' builds are functional, but you'll need to have installed the MS Visual Studio C++ 64-bit runtime (merged VS 2015, 2017, 2019) to system. Pick it up here: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
@V Stuart Foote: works, thanks,
looks as if actual ver. from /daily/master/Win-x86_64@tb77-TDF/ ... not the 'nomerge' version ... still requires vcruntime / vcruntime140_1.dll ... ver. tested: Version: 7.0.0.0.alpha0+ (x64) Build ID: 9ed75e2c65544b4f71c73e1c51a68d74e31d544b CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc:
reopening, it's 'notabug', but a problem for the validity of tests with the alpha version for a later release, as well as for a release that would be compiled with these settings and would inhibit the installability on 'normal' systems, or would produce many questions from users. 6.2.8.2 did not have these requirements. looks as if actual ver. from /daily/master/Win-x86_64@tb77-TDF/ ... not the 'nomerge' version ... still requires vcruntime / vcruntime140_1.dll ... ver. tested: Version: 7.0.0.0.alpha0+ (x64) Build ID: 6ac2d66c78d6c080aabfa46157113684c2f3a3b0 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI-Language: en-US Calc: CL
For alpha/beta versions, it's normal and expected that system components (vcredist) are not installed, and registry is not modified (by default). They are effectively unpacked. So installation of vcredist is the responsibility of the tester. The "6.2.8.2 did not have these requirements" is just a misconception. When any alpha/beta version is installed on a clean system not having vcredist, it will complain the same way. Of course, if any other software had already installed a vcredist on the system that satisfies an older LO version, it will not complain; if that pre-existing vcredist is too old for a newer alpha, this problem will happen. Possibly QA team needs to update some its wikis.