<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Failure to launch Libreoffice 6 after installation" href="https://bugs.documentfoundation.org/show_bug.cgi?id=115405#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Failure to launch Libreoffice 6 after installation" href="https://bugs.documentfoundation.org/show_bug.cgi?id=115405">bug 115405</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to Surya Sunder Dey from <a href="show_bug.cgi?id=115405#c15">comment #15</a>) The logs you provided tell that the redist installer detects the presence of Universal CRT (and various api-*.dlls are part of the Universal CRT (ucrt)), and doesn't try to install it: > [0898:13B8][2018-04-10T10:49:17]i100: Detect begin, 10 packages > [0898:13B8][2018-04-10T10:49:17]i000: Setting version variable 'windows_uCRT_DetectKey' to value '10.0.16299.15' > [0898:13B8][2018-04-10T10:49:17]i000: Setting numeric variable 'windows_uCRT_DetectKeyExists' to value 1 > ... > [0898:13B8][2018-04-10T10:49:19]i201: Planned package: Windows7_MSU_x64, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None The detection consists of finding the file "ucrtbase.dll" in %windir%\System32, and getting its version. As shown above, the present version is very high (10.0.16299.15), much higher than that of the bundled with LO (we use the redist from the link given in <a href="show_bug.cgi?id=115405#c10">comment 10</a>, and it contains "Update for Universal C Runtime in Windows" (KB2999226) [1] with ucrtbase version 10.0.10240.16390). I know of the other update (KB3118401 [2]), but it also contains a lower version: 10.0.10586.9. So, this must mean that you system has the updated ucrt, but it is broken for some reason, missing some components. This must have happened on the update; I suppose it was Windows Update that has updated *and broke* the component. Why I think so? Well: if the component was broken before the update, then proper update would repair it. So it must be the last operation on the component that was faulty. And since the version is higher than bundled with LO, it must mean that the component was either pre-installed before LO, or had been updated after. I don't know the KB article of the update that updates ucrt on Win7 to your version (I have created a VM with Win7x64 and am updating it ATM to find out), but my guess is that you should uninstall the update and reinstall it using command like > wusa /uninstall /kb:2999226 and then reinstalling the redist. [1] <a href="https://support.microsoft.com/en-us/help/2999226">https://support.microsoft.com/en-us/help/2999226</a> [2] <a href="https://support.microsoft.com/en-us/help/3118401">https://support.microsoft.com/en-us/help/3118401</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>