Thank you very much! That helps a lot.
The missing MSVCP140D.dll is expected - because that’s a build with debug version, which depends on debug libraries missing on your system. But since we tested installation, this is unimprotant.
You may now remove the alpha installs, and re-install a current version. When “hung”, please kill running wusa.exe, and it should continue. If you would be so kind to also log that process, I’d owe you much!
The saga continues…
Cleaned up by uninstalling. 1st attempted install of LO6.2.2.2_32bit fails, 2nd fails. Both rollback.
Did DiskClean including system files, blew away registry and loaded the copy made after Win 8.1. Full-off reboot.
3rd attempt of install succeeds! Waited for hang and killed the wusa process as suggested. Instal now continues
BUT the system cannot run LO as “The program can’t start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer.”
logs at: logs link
And what if you manually install the update from https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows? Will it also hang? You may run the update manually using wusa.exe and view its own log using instructions from https://support.microsoft.com/en-us/help/934307/description-of-the-windows-update-standalone-installer-in-windows. Also running wusa.exe without parameters shows you its /log switch with examples; the generated logfile is something which should be viewed with event viewer, not a normal text file.
Finally got everything to work.
The manual install of KB2999226 starts a detect process for necessary other update DL’s which involves discovering what this PC needs and installing them (zero) which happens before the requested manual install. So, when starting KB2999226 by hand the detect and install job runs first and WU never completes.
How to manually install then? I had to:
From this I learn that starting Windows Update, by itself, can hang the PC forever. Any KB2999226 installer needs to not go via WU service as, alas, it is cursed.
Unfortunately, this didn’t clarify things
The “manual KB2999226 installer” is MSU file, which is associated with that wusa.exe - see relevant registry entries at HKEY_CLASSES_ROOT\.msu and HKEY_CLASSES_ROOT\Microsoft.System.Update.1\shell\open\command. If you launch it again, you may see a message box telling “it is already installed”, and in the task manager, the running wusa.exe; you even can see full command line used to launch it, if add relevant column to task manager. And that is exactly the same command line used by LO installer.
wusa.exe is “Windows Update Standalone Installer”; it internally uses Windows Update service anyway. If Windows Update is disabled, so that wusa cannot enable it even temporarily, it will fail. That is why LibreOffice installer makes sure to temporary enable WU service (but not start) if it’s disabled. Setting the service to “never start” is not disabling it; so wusa is free to start it when required… and it’s still unclear what happens.
Might it be that what is needed is simply stop the WU service (but keep it enabled) prior to installing the update? So that wusa would start it as required, and in this process, would behave somehow differently?
I cannot test, but I’ll change the patch now to also do that.