Created attachment 201461 [details] updating.log On my main machine the MAR-Update shows up on every boot and fails. I checked the logfiles but can't see where the root cause is. I attach the logfiles and will wait for a week before I do a manual upgrade from 24.87 to 25.2.4. If one wants me to try some things, I can do that in this one week.
Created attachment 201462 [details] update.log
Created attachment 201463 [details] update.status
Happened to me as well with 24.8 and 25.2. Had to manually update to 25.2.4
(In reply to Maverick from comment #3) > Happened to me as well with 24.8 and 25.2. > Had to manually update to 25.2.4 Due to the other issues with the MAR-Updater (version numbers not updated), I will have to do a manual upgrade anyway. But having this reproducible issue could help improving the MAR-updater for average users, thats why I won't update for some time, in case someone wants me to do tests :D On an other machine the MAR Update from 24.8.7 to 25.2.4 worked, so it's not a general issue with main-version-updates.
interesting - obviously not reproducible in a test install of an older 24.8 in windows sandbox.. 2025-06-25 10:44:03+0200: rename_file: failed to rename file - src: X:\Path\LibreOffice\Stable/program/types/oovbaapi.rdb, dst:X:\Path\LibreOffice\Stable/program/types/oovbaapi.rdb.moz-backup, err: 13 2025-06-25 10:44:03+0200: ### execution failed is the relevant line in the log - it fails to update that file / create a backup file for that file and then the further lines are for rolling back the update (and lots of the errors further down aren't errors - no backup files to remove if the process didn't go as far as to create them in the first place... So X:\Path is kinda unusual/stands out here (also at the top of the log), and the other log lists P:\… which is also unusual. Having this reproducible would indeed help, but having it reproducible on your system only without the steps to get to this state are less likely to help :-) So do you remember anything special about your installation – apart obviously not using the standard installation path? Did you at some point move the installation? Did you select/deselect components during installation? Do you maybe have a overzealous antivirus running that did block creating the backup file for the oovbaapi.rdb file? Was another instance of LibreOffice still running maybe?
Created attachment 201469 [details] zip of the MAR update 24.8.7.2 -> 25.2.4.3 Win11, non-priv account, normal C:\ system install It has been normal to get repeated failed logged update checks, but when the MAR incremental has been prepared by TDF infra should actually get the matching partial.mar downloaded as "update.mar" TDF infra has recently built and posted the 24.8.7.2 --> 25.2.4.3 incremental: LibreOffice_25.2.4.3_Windows_X86_64_33e196637044ead23f5c3226cde09b47731f7e27_from_e07d0a63a46349d29051da79b1fde8160bab2a89_partial.mar The 'updating.log' posted (attachment 201461 [details]) shows it downloaded. But looking at the posted 'update.log' (attachment 201462 [details]) shows multiple apparent file path errors, and failed rollback. Could not reproduce. Win11 (24H2) non-admin priv account. I did a full removal and clean install of the 24.8.7.2 MSI, and it applied the MAR update to 25.2.4.3 on first launch (no priv user, so used the update service). Completed with no errors in the corresponding update.log (attaching). Of course still issue of bug 164043 in that the Windows registry remains loaded with the 24.8.7 GUIDs, and of bug 164937 message during update being a bit too terse.
(In reply to Christian Lohmaier from comment #5) > 2025-06-25 10:44:03+0200: rename_file: failed to rename file - src: > X:\Path\LibreOffice\Stable/program/types/oovbaapi.rdb, > dst:X:\Path\LibreOffice\Stable/program/types/oovbaapi.rdb.moz-backup, err: 13 > 2025-06-25 10:44:03+0200: ### execution failed The File "oovbaapi.rdb" is not write-protected and Administrators/System has full Access. I can also rename the file manually if soffice.exe is terminated. So thats not the issue why the file couldn't be renamed. But the soffice.exe has a handle on this file. And those lines, make me believe that the MAR-Updater tries to shutdown soffice.exe but fails: NS_main: callback app file open attempt 10 failed. File: X:\Path\LibreOffice\Stable\program\soffice.exe. Last error: 32 NS_main: callback app file in use, continuing without exclusive access for executable file: X:\Path\LibreOffice\Stable\program\soffice.exe If I am right, that the soffice-process should be terminated but fails to do, then its logical that files that are in use can't be renamed. Anti-Virus is the same then on the other machine were the update worked, so I don't think its an AV-Issue. Also disabling the AV doesn't improve situation. I also fired up Sysinternals Process Monitor, to see any reasons why "oovbaapi.rdb" can't be renamed, but it doesn't show any errors in conjunction with that file. In "PM" it looks like there isn't even a try to rename the file, because on "uno.exe" which was renamed before, I can see a "SetRenameInformationFile"-operation, but for "oovbaapi.rdb" I can't see that event in the PM-Log. Maybe a timing-issue, with not all handles being closed before updater.exe starts its job? But I'd expect to see that in process monitor... > So X:\Path is kinda unusual/stands out here (also at the top of the log), > and the other log lists P:\… which is also unusual. Yes, its a custom-Install path. X is for anonymous reasons and the "other" letter is evidence that I wasn't successful in fully "anonymizing" the logs :( It should be "X" everywhere.. > So do you remember anything special about your installation – apart > obviously not using the standard installation path? > > Did you at some point move the installation? No > Did you select/deselect > components during installation Yes. LibreLogo is usually deselected on my installs. But that applies to both computers the same way. > Do you maybe have a overzealous antivirus > running that did block creating the backup file for the oovbaapi.rdb file? As said, same AV on both machine and also disabling it doesn't solve the issue. > Was another instance of LibreOffice still running maybe? No. All instances of soffice.exe and soffice.bin were terminated before the test. But for testing I open up a ODS-File, so in that moment one instance of soffice.exe fires up. In process monitor log I can see, that soffice.exe is terminated when I would expect the MAR to rename the file.