Problem description: I installed the new LibreOffice 3.5.4 release on Windows 7 Professional 32 bit. The installation completed. But when I try to run LibreOffice for the first time, the system reports that the program has stopped working. I have tried to run as user and as administrator. Steps to reproduce: 1. Install LibreOffice 3.5.4 release on Windows 7 Professional 32 bit. 2. Try to run LibreOffice. 3. Get error. Current behavior: Error message that the program has stopped working. Expected behavior: LibreOffice should work. Platform (if different from the browser): Windows 7 Professional 32 bit. Additional information: The installation works fine on Windows XP, but while XP still has a very large user base, it has been around since August 24, 2001. I would hope that the LibreOffice developers would be testing installation, operation, and performance on more recent Windows operating systems. Windows 7 is quite stable for a Microsoft OS, and Windows 8 is coming quickly. If the LibreOffice team desires to be widely accepted, Linux, Mac, and Windows, then testing must be more rigorous and include more than just certain builds of certain OSs.
Details?
Not much more in the way of details to provide. I tried deleting all the Microsoft C++ redistributable packages and reinstalling. Again, the installation completes just fine. The error occurs when LibreOffice is run for the first time. It is trying to configure dictionaries enabling and disabling and other configuration tasks that are performed on first run. I believe it may be a permissions or security issue, but that is not the error that is presented. I had to remove 3.4.4 in order to install 3.5.4 because the 3.5.4 installer kept complaining that 3.4.4 was open or the quick start was running. Neither was true. I removed 3.5.4 and reinstalled 3.4.4. Now I get the same error that the program has stopped working when first trying to run 3.4.4. So I uninstalled 3.4.4 too. Now there is no instance of LibreOffice on the system. Need to get this solved.
Created attachment 63386 [details] Screenshot of error
*** This bug has been marked as a duplicate of bug 38913 ***