Created attachment 127236 [details] "Prop Res DLL not loaded" alert message box Using the latest version of Libre Office (and I just confirmned it on 5.1.5.2), when I FILEOPEN a spreadsheet, or try to change properties in a Text document, I get several errors (4 or 8, typically), each requiring a click to close the message box. (See attached file for a screen capture). The message is always "Prop Res DLL not loaded." Things seem to work Okay once I get past the 4 or 8 alerts, but it's a bad symptom.
For the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try?
(In reply to Julien Nabet from comment #1) > For the test, could you rename your LO directory profile (see > https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try? I did that, and it opened with no display of previous files. But, opening a simple spreadsheet file causes the Error. I made a brand new simple spreadsheet, repeated the user file rename, and opened it fresh. The Prop Res DLL error occurred 4 times, again. I will make a new comment and add the latest screen cap, plus the simple spreadsheet that causes the error.
Created attachment 127283 [details] Shows the error after deleting the User file. Shows the error after clearing out the User file/info as directed.
Created attachment 127284 [details] This simple spreadsheet triggers the Error. This is a simple spreadsheet, 4 cells with a simple match calculation. This gives me the "Prop Res Error DLL" error message upon opening, even after resetting the user data file.
Do you have some Lexmark or Dell printer? Perhaps this link may help: https://support.microsoft.com/en-us/kb/918730
I did have an installation of a Lexmark printer, which I wasn't even using (it wouldn't connect to the printer for some reason or another). So, I un-installed the Lexmark printer, and rebooted. Since then the Error has disappeared, no more "Prop Res DLL" messages. Jolly good show, I'll lay the blame for this bug on Lexmark.
Thank you for your feedback. Just nitpicking but there's no LO patch about this and since it's not LO bug, let's put NOTOURBUG status.