Error code 2908 and 1935 installing Libreoffice on Win7(32bit)

I have been using LibreOffice during the time it has existed, both on my private PC (OS: OpenSuSE) and on my work PC (OS: MS WIndows). My company have changed their telephone system to be IP-telephones and we used to use Lyncs 2013 without problems. Lyncs 2013 has been upgraded to Skype for Business and since then I have not been able to open LibreOffice. It always crashed with an error in msvcr100.dll (it might have been msvcp100) as far as I remember. As I removed LibreOffice from the system to reinstall it and I no longer am able to install LibreOffice on the system (neither 4.4.5 or 5.0.0) with error code 2908 and 1935, I can not reproduce the problem.

Is it possible to compile LibreOffice on the Windows PC, and what would I have to install on the system to do so? Could such an approach remedy the problem?

Best Regards,

[edit: added win7 + lo5 tags]

*Error 2908: Could not register component*

(Some files required to install an application are not found on your system (but should be))

Error 1935: An error occurred during the installation of assembly component [2]. HRESULT: [3]. {{assembly interface: [4], function: [5], assembly name: [6]}}

So, files(s) that should be in your system are not, or are corrupted (or possibly the wrong version) and/or Registry values are missing and/or corrupted, or… hells bells. The most common fix advised for this is to reinstall your OS (yes, really).

Here are some sane steps that can be taken:-

  1. M$ has provided a “Microsoft Fix-It” website:-

"Automatically repair issues that block program installation or removal because of corrupted registry keys."

  1. Reinstall Visual C++
    This is directly relevant to win7 + msvcr100.dll and–as best as I recall–to LO/OO.
  2. .NET Framework remove + reinstall (web or standalone)
    This is the one commonly advised for M$ Office, but could easily also apply to LO/OO.
  3. Use the System File Checker:-

Windows 7 or Windows Vista:

A) click Start, type Command Prompt or cmd in the Search box, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.

B) At the command prompt, type the following command, and then press ENTER:

sfc /scannow

C) The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache.

The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows.

Note Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished.

SFC does require that your system is not already too corrupted.

Latest Supported Visual C++ Downloads
(all Windows versions - I cannot confirm which version is for which Windows)

If this helps then please tick the answer (:heavy_check_mark:)

thanks, for your reply and advice.
I followed your steps in a slightly obscure order.

  1. I tried the MS Fix-it but the program could not detect any traces of LO so that was not a possibility to search for.
    I then ran the windows update that I found on the site which installed 34 updates, even though windows updater said there were only 2 updates in queue.
  2. Before I tried my luck with Visual C++ or SFC, I removed the .NET Framework with the link provided, that led to me being able to install LO again. (yeah) But I only received the same fault as before with a crash in msvcr100.dll
  3. I wasn’t quite sure which Visual C++ i should remove there were 5 different VC++ Redistributables installed, I first ran SFC, but that did not find anything wrong in the system files.
  4. I removed all VC++ Redistributables except for the newest one i.e.2013 that has at least for now, solved the problem in parts, by opening an older file first and have LO open, I can now use LO again as my reader for files I get via e-mail etc.

Best regards

Glad you’ve got some use of your system back. By the sounds of it you need to steel yourself to the system falling over at some point in the near future. But hey! It’s working now.