Bug 84331 - Cannot start LO, msvcr100.dll not found, after 4.3.2 installation
Summary: Cannot start LO, msvcr100.dll not found, after 4.3.2 installation
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.3.2.2 release
Hardware: Other Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-25 17:39 UTC by Chris
Modified: 2014-09-26 10:41 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2014-09-25 17:39:28 UTC 
Unable to start Libreoffice after clean installation of 4.3.2. Get a 'soffice.exe - System Error: The Program can't start because MSVCR110.dll is missing from your computer. Try reinstalling the program to fix this error'. I've tried twice, now returned to LO 4.2.6.3 which works. OS is Win 7, 64 bit.
Comment 1 tommy27 2014-09-25 18:29:05 UTC 
looks similar to Bug 84244 - Missing MSVCR100.dll
Comment 2 contracode 2014-09-25 21:05:16 UTC 
Installed LibreOffice 4.3.2.2 (x86) on Windows 7 Enterprise 64-bit. No issues. Perhaps a fresh profile should be used. See: https://wiki.documentfoundation.org/UserProfile
Comment 3 Robinson Tryon (qubit) 2014-09-25 21:10:16 UTC 
Hi Chris,
If clearing your UserProfile doesn't fix the problem, please feel free to change the status of this bug back to 'UNCONFIRMED'.

Thanks
Comment 4 Chris 2014-09-26 09:33:05 UTC 
Hi All,
Thanks for comments, resetting user profile worked, but I don't know why. I saved the previous profile to a different location prior to installing this release.

Chris
Comment 5 tommy27 2014-09-26 10:41:46 UTC 
@Chris
nice to hear that.

anyway we use the status FIXED when a bug is resolved by a specific committ by a developers.

in cases like yours where the issue is fixed by resetting the user profile we usually use the status WORKSFORME.

so I'm changing the status here.