[Libreoffice-bugs] [Bug 124522] Installation fails on Windows x86

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=124522

--- Comment #5 from Mike Kaganski <mikekaganski at hotmail.com> ---
(In reply to Dimitar Nanev from comment #3)
> KB2999226 seems to be source of the problem. LibreOffice installer triggers
> Windows Update to install KB2999226 which fails with error code 0x80070490.

Citing [1], "0x80070490 error means the Component-Based Servicing (CBS)
manifest is corrupted".

> Tried to repair (SFC /ScanNow and DISM /Online /Cleanup-Image /ScanHealth)
> and also to rebuild SoftwareDistribution folder without success. Manual
> installation of KB2999226 produces same error 0x80070490. Other Windows
> Updates work on this machine. All required updates were installed with no
> problems before coming to LibreOffice installation.
> 
> Obviously there is something broken with Windows Update on this machine.
> Tried to dig the installation problem of KB2999226 but I'm not fluent with
> WU process. In CBS log (log file attached) I see this error:
> Failed to resolve package
> 'Package_803_for_KB4480970~31bf3856ad364e35~x86~~6.1.1.6' [HRESULT =
> 0x80070490 - ERROR_NOT_FOUND].

[2] seems to mention exactly same scenario - so it looks like that update
failed somehow on this system, and is now preventing *some* other updates.

> I don't know what KB2999226 has to do with KB4480970. KB4480970 is not
> installed on this machine and I'm not going to install it anyway because I
> catch it earlier to break Windows File Sharing network (another machine,
> another installation). So I give up for now.
> 
> Btw, it's wise for LibreOffice not to depend on the notoriously broken
> Windows Update system for its own installation.

It's wise for LibreOffice to use OS-recommended ways to install external
components, especially when they are OS-related. And UCRT is such a component.
Unfortunately, MS *only* recommends installing it using Windows Update; an
app-local deployment, which is possible and used in version 5.4 is prone to
security problems (because in case of an identified vulnerability in UCRT,
which MS fixes and deploys using its update mechanism, app-local UCRT would
still be nulnerable).

My direct inquiry about this problem received a clear response (see answer by
Steve Wishnousky [MSFT] at [3]):

> The Universal C Runtime is only provided through an MSU and that
> technology is tied to wuauserv - unfortunately I cannot recommend a
> workaround or solution for customers who have deleted the service or
> otherwise prevented the service from operating properly

So - well, it's very easy to tell others what is wise to do; it's much more
difficult to find a silver bullet. And security-wise, it's wiser to do it this
way for now, until they do something as hinted at [4], where Mahmoud Saleh
[MSFT] wrote: "... we are definitely listening to the feedback regarding the
need for an alternative mechanism for including the VC++ Runtimes into
installers".

As to

> I'll look forward for version version 6.3.

- if you do not have KB2999226 installed, 6.3 would not do any good for you: it
still requires it to work. It only will show you a warning that installation of
KB2999226 failed, and then proceed - expecting you to take care of installing
UCRT manually. So you are likely to end up with successfully installed, but
non-functional, LibreOffice.

[1]
https://social.technet.microsoft.com/Forums/windows/en-US/54568594-1443-498e-aa52-5a55023375dd/windows-update-error-code-0x80070490
[2]
https://serverfault.com/questions/101685/windows-updates-fails-server-2008-0x80070490?rq=1
[3]
https://developercommunity.visualstudio.com/idea/412198/detect-a-windows-version-from-msi.html
[4]
https://developercommunity.visualstudio.com/content/problem/439217/deprecation-of-crt-redist-msms.html?childToView=498962#comment-498962

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20190405/bca05a37/attachment.html>