Description: If I try to open a file using a shortcut I cut "Access Denied" but if I try to open a file from inside Libre Office I get "Need Permission." Both of which can be eliminated "IF" I disable my AVAST Firewall first. Now, those folks can't tell me why this just started nor how to fix it so I'm grasping straws and asking you folks. HELP!!! Steps to Reproduce: 1.Running Windows 10 2.Avast Premium Security - Firewall Enabled 3.Attempt to Open Libre Office file (docx or xlsx) Actual Results: File will deny you access until firewall is disabled Expected Results: File Opens as requested Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: StartModule [Information guessed from browser] OS: Windows (All) OS is 64bit: no
Indeed, Avast / AVG started to block newer LibreOffice releases recently: https://ask.libreoffice.org/t/when-trying-to-open-some-files-i-get-error-access-denied-or-this-file-has-been-locked-by-another-user/97072/ https://ask.libreoffice.org/t/unable-to-open-7-4-docs-with-7-6-version-loaded/96917 https://ask.libreoffice.org/t/problem-opening-saved-docs-following-recent-upgrade/96972 https://ask.libreoffice.org/t/can-no-longer-use-desktop-shortcuts-for-individual-files/96980 This is not a bug in LibreOffice, and we can do nothing about their behavior. The only thing you can try is finding the correct procedure to add Program Files\LibreOffice\program\soffice.bin into the antivirus' exception list (there is a similar procedure for Windows Defender's folder access control, explained in the FAQ [1]). And of course, filing bugs/issues/support tickets against Avast is the correct way of resolving this, finally. Closing NOTOURBUG. [1] https://wiki.documentfoundation.org/Faq/General/Defender_Controlled_folder_access_exception
https://ask.libreoffice.org/t/can-only-open-calc-in-read-mode/97299 https://ask.libreoffice.org/t/fyi-avast-blocked-2-ods-files/97305
Let's consolidate into bug 157497. *** This bug has been marked as a duplicate of bug 157497 ***