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

--- Comment #21 from ady <[email protected]> ---
The following side note might be related to the origin of the problem.

Context:
* VBox VM with *no network connection*.
* Guest OS (plus VBox Guest Additions): Win 7 SP1 x32 (build 7601) from 2018-08
(aka August 2018 "refresh").
* Installed on the Guest OS: Current MS Visual C++ Redistributable x86 version
14.38.33135.0.
* Installed on the Guest OS: LibreOffice 24.8 alpha 32 bits Win-x86 downloaded
from:
 dev-builds.libreoffice.org/daily/master/Win-x86@39/2024-02-17_00.08.15

NAME: master~2024-02-17_00.08.15_LibreOfficeDev_24.8.0.0.alpha0_Win_x86.msi
SIZE: 217'223'168 bytes
MD5:  41344864ef938f290037ad93fd8fdb78


Note:
I attempted to install KB3063858 (x86) mentioned in the System Requirements for
Windows 7 SP1, but the procedure resulted in a message that says "The update is
not applicable to your computer". I don't know whether this is because the Win
7 SP1 "refresh" is dated later than KB3063858 (which, AFAIU, it is), or because
some other reason.


RESULT:

After installation, when trying to run LibreOffice, the following message is
shown on screen (and LO does _not_ start):


soffice.bin - Entry Point Not Found
The procedure entry point BCCryptKeyDerivation could not be located in the
dynamic link library bcrypt.dll.


This suggests that LO (at least 24.8 alpha, and possibly other versions too)
requires a specific version (or versions) of bcrypt.dll that is (are) not
necessarily installed on every Windows 7 (SP1) system.

Maybe an updated (after 2018-08) bcrypt.dll for Windows 7 might not have these
problems; that is yet to be tested (by knowledgeable devs).

There might be some MS's patch (whether after 2018-08, or rolling back to some
older point) that might solve the bcrypt.dll problem.

Or, there might be some legal way for users to obtain and install a valid
bcrypt.dll file for Windows 7 SP1 that would not generate this (compatibility?)
problem(s) for LO.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to