Description: [ES] Ya sucedía con una instalación de Windows 10 1803 que había sido actualizada durante más de 2 años (sin formatear el disco). Sucede lo mismo con la instalación limpia de Windows 10 1803. El problema es que no se puede borrar, renombrar, mover, etc. la carpeta e intentar reinstalar LibreOffice dará un fallo al no poder escribir en ella. [EN] It was already happening with a Windows 10 1803 installation that had been updated for more than 2 years (without formatting the disk). The same thing happens with the clean installation of Windows 10 1803. The problem is that it can not be deleted, renamed, moved, etc. the folder and try to reinstall LibreOffice will fail to write on it. Steps to Reproduce: 1. Uninstall LibreOffice. 2. Enter into installation folder -OR- 3. Right clic in folder -> Properties Actual Results: C:\Program Files\LibreOffice\program all user rights have been erased by any user (including the system itself) Expected Results: Can delete the folder or reinstallation can use this folder. Reproducible: Always User Profile Reset: Yes Additional Info: Versión: 6.1.2.1 (x64) Id. de compilación: 65905a128db06ba48db947242809d14d3f9a93fe Subprocs. CPU: 4; SO: Windows 10.0; Repres. IU: GL; Configuración regional: es-AR (es_AR); Calc: CL
Created attachment 145728 [details] Filder locked. Can't delete as Administrator User
Created attachment 145729 [details] Folder properties (wrong)
Created attachment 145730 [details] When LibO is installed
Created attachment 145732 [details] Il try to reinstall LibO without deleting the folder. It can not be installed while the folder is not deleted. [ES] Al intentar reinstalar LibO sin borrar la carpeta. No se puede instalar mientras la carpeta no sea eliminada. Para poder hacerlo hay que realizar un complejo sistema de reinicio en "Modo Seguro" de Windows 10 (imposible de entender para un usuario común) y allí se puede borrar porque se omiten los derechos de acceso. [EN] When trying to reinstall LibO without deleting the folder. It can not be installed while the folder is not deleted. To be able to do it, you have to perform a complex restart system in "Safe Mode" of Windows 10 (impossible to understand for a common user) and there you can delete it because the access rights are omitted.
Have you tried to reboot after uninstalling LO? I have a Win 10 installation where i have to reboot after uninstalling LO to get rid of the folder: - uninstall LO - folder "C:\Program Files\LibreOffice\" still exists and can't be removed - reboot - now "C:\Program Files\LibreOffice" has gone - install new version of LO i do not need to reboot in safe mode.
(In reply to Oliver Brinzing from comment #5) > Have you tried to reboot after uninstalling LO? > > I have a Win 10 installation where i have to reboot > after uninstalling LO to get rid of the folder: > > - uninstall LO > - folder "C:\Program Files\LibreOffice\" still exists and can't be removed > - reboot > - now "C:\Program Files\LibreOffice" has gone > - install new version of LO > > i do not need to reboot in safe mode. I have tried installing 6.1.2, 6.1.1 and 6.0.6. The problem is presented with the 6.1.x, and only on one occasion restarting the folder was deleted. The one that never disappeared is that of LibreOffice. But after restarting, the fault has been presented in most cases.
Created attachment 145747 [details] Locked file.
Created attachment 145767 [details] Win 10 LO upgrade (uninstall) problem
(In reply to Oliver Brinzing from comment #8) > Created attachment 145767 [details] > Win 10 LO upgrade (uninstall) problem Is this normal or not? What causes it Windows or LibO Unistall? Why only with LibO?
(In reply to Leandro Martín Drudi from comment #9) > Is this normal or not? What causes it Windows or LibO Unistall? > Why only with LibO? i don't know the cause, this happens only on my Win 10 Home (x64) computer. i will try to log install/uninstall next time, e.g: msiexec /qb /passive /i LibreOffice_6.0.7_Win_x64.msi /L*V install.log msiexec /qb /passive /uninstall {GUID} /L*V uninstall.log GUID can be found in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall search for "LibreOffice" -> UninstallString MsiExec.exe /I{GUID}
@Mike Kaganski, I thought you could be interested in this issue...
Created attachment 150153 [details] Error during update [ES] Estoy actualizando LibO de 6.2.1 a 6.2.2 y me aparece el error. Es sumamente molesto. [EN] I am updating LibrO from 6.2.1 to 6.2.2 and I get the error. It is extremely annoying.
Error 1303 is *really* common for any software MSI installers on Windows. It's enough to google for "MSI error 1303". It's common in the sense that it looks really independent of specific MSI packages, and affects just any installer at random; not that it's so frequent that it affects large proportion of users of any application. Inability to access the installation directory could happen in two patterns: first is when something (some not closed handle in some process?) has prevented the directory from being removed, so the directory is in "almost removed" state - and in this case it would be completely removed upon all handles closed (so reboot eliminates the directory; see comments by Oliver, and also "Reboot" section in our FAQ [1]). This pattern is specific to the Windows generic handling of low-level modifications of resources that are still in use. But there's the other - when the directory does not get removed, but has some incorrect permissions. I don't know if that is related to first scenario; but it's this pattern about which e.g. Microsoft suggests to take ownership - see [2] which mentions their KB for MS Office installation (now inaccessible). There seems to be no identified causes for the problem; but given that the second scenario tends to repeat on some systems again and again, I wonder if that could be at least partly connected to specific antiviruses, or to some system hardening patches; aren't the root directory and/or Program Files directory permissions modified from factory settings?... I'd love to hear about some specific things that allow to reliably reproduce the problem in lab; that could allow to find at least some possible reasons and maybe fix/workaround them. If you find something substantial, please mention it here. [1] https://wiki.documentfoundation.org/Faq/General/General_Installation_Issues_(Windows)#Reboot [2] https://answers.microsoft.com/en-us/windows/forum/windows_7-security/error-1303-account-with-full-administrator-rights/d9141f1a-1ea0-4121-b7fb-e2b9659e31e3
As a user of LibreOffice since its launch and of Windows from the Win98 version, it is with the only software (LibO) with which I have this problem. I install software by MSI every week and I never had any problem in all these years. It was only from LibreOffice 6.1.2.1 Now, would not it be optimal for the installer to offer a restart? The strange thing is that now it happened with the update on the previous installed version (without untarning it first) and it has also happened with the uninstallation / installation of the new one.
Reproducible: Versión: 6.2.6.2 (x64) Id. de compilación: 684e730861356e74889dfe6dbddd3562aae2e6ad Subprocs. CPU: 8; SO: Windows 10.0; Repres. IU: predet.; VCL: win; Configuración regional: es-AR (es_AR); Idioma de IU: es-ES Calc: CL Versión: 6.3.0.4 (x64) Id. de compilación: 057fc023c990d676a43019934386b85b21a9ee99 Subprocs. CPU: 8; SO: Windows 10.0; Repres. IU: predet.; VCL: win; Configuración regional: es-AR (es_AR); Idioma de IU: es-ES Calc: CL
The problem continues to occur in all versions released so far. If it was a system problem, I think it would fail with all the software but this only happens with LibreOffice.
No reproducible: Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: es-AR (es_AR); UI: es-ES Calc: CL Fixed may be?
Dear Leandro Martín Drudi, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
No reproducible: Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: es-AR (es_AR); UI: es-ES Calc: CL threaded