Vladislav Vaintroub added a comment - 2025-01-31 16:21 - edited Jelkelueschen , to analyze such kind of errors, MSI log is necessary. Generic instructions are these : start MSI from the elevated command line, as msiexec /i Example.msi /quiet /L*v "C:\tmp\mariadb-install-log.txt" Replace Example.msi with the real MSI name, and make sure C:\tmp exists. After that, please attach mariadb-install-log.txt to the ticket.

Vladislav Vaintroub added a comment - 2025-01-31 16:28 Also, if you're not into very latest experimental features, an LTS release such as 11.4 is preferrable, with the latest patch. 11.6 is not supported over long term, in fact, there won't be any new releases for it.

Jelke Lüschen added a comment - 2025-02-03 07:43 - edited Hey, I followed your advice and logged the installation. I tried it with the 11.4.4 version but the same error occured. Here is the log: === Verbose logging started: 03.02.2025 08:40:46 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\system32\msiexec.exe === MSI (c) (44:40) [08:40:46:289]: Resetting cached policy values MSI (c) (44:40) [08:40:46:289]: Machine policy value 'Debug' is 0 MSI (c) (44:40) [08:40:46:289]: ******* RunEngine: ******* Product: mariadb-11.4.4-winx64 (1).msi ******* Action: ******* CommandLine: ********** MSI (c) (44:40) [08:40:46:289]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (44:40) [08:40:46:289]: Grabbed execution mutex. MSI (c) (44:40) [08:40:46:305]: Cloaking enabled. MSI (c) (44:40) [08:40:46:305]: Attempting to enable all disabled privileges before calling Install on Server MSI (c) (44:40) [08:40:46:305]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (CC:28) [08:40:46:337]: Running installation inside multi-package transaction C:\Windows\system32\mariadb-11.4.4-winx64 (1).msi MSI (s) (CC:28) [08:40:46:337]: Grabbed execution mutex. MSI (s) (CC:D8) [08:40:46:337]: Resetting cached policy values MSI (s) (CC:D8) [08:40:46:337]: Machine policy value 'Debug' is 0 MSI (s) (CC:D8) [08:40:46:337]: ******* RunEngine: ******* Product: C:\Windows\system32\mariadb-11.4.4-winx64 (1).msi ******* Action: ******* CommandLine: ********** MSI (s) (CC:D8) [08:40:46:337]: Note: 1: 2203 2: C:\Windows\system32\mariadb-11.4.4-winx64 (1).msi 3: -2147287038 MSI (s) (CC:D8) [08:40:46:337]: MainEngineThread is returning 2 MSI (s) (CC:28) [08:40:46:337]: User policy value 'DisableRollback' is 0 MSI (s) (CC:28) [08:40:46:337]: Machine policy value 'DisableRollback' is 0 MSI (s) (CC:28) [08:40:46:337]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (CC:28) [08:40:46:337]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (CC:28) [08:40:46:337]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (CC:28) [08:40:46:337]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (44:40) [08:40:46:337]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (44:40) [08:40:46:337]: MainEngineThread is returning 2 === Verbose logging stopped: 03.02.2025 08:40:46 ===

Vladislav Vaintroub added a comment - 2025-02-03 08:39 - edited Jelkelueschen , something went wrong. The log refers to C:\Windows\system32\mariadb-11.4.4-winx64 (1).msi , which is not there. The result log file should be some 2MB in size, and contain much more Can you please retry once again, using full path (quoted) to your MSI file. something like that msiexec /i "C:\Users\user\Downloads\mariadb-11.4.4-winx64 (1).msi" /L*v C:\tmp\install.log This will the MSI with logging, and then you should get the usual MSI UI, and go through the same steps, as you do, when you'd just click on this MSI file in the explorer. The only difference is that this one writes the log. Thank you!

Jelke Lüschen added a comment - 2025-02-03 09:34 Oh, my mistake... here is the log file. mariadb-install-log.txt

Vladislav Vaintroub added a comment - 2025-02-03 13:45 - edited Ok, the error according to the log file is CAQuietExec64: Running bootstrap CAQuietExec64: Registering service 'MariaDB' CAQuietExec64: FATAL ERROR: Can't write to ini file key=datadir, val=C:/Program Files/MariaDB 11.4/data, section=mysqld, Windows error 5 CAQuietExec64: Creating my.ini file I think we have never seen anything like that . Error 5 is ERROR_ACCESS_DENIED I can imagine it happens if some 3rd party antivirus holds the file open, without sufficient sharing. Might this also apply in this case? Can you try to disable whatever antivirus runs on the box for the time of installation There is also something that MariaDB can do, as it defensively tries to anticipate buggy antivirus elsewhere in the code, with retry logic during file open/move/delete.

Jelke Lüschen added a comment - 2025-02-04 11:15 Hey @Vadislav Vaintroub, thank you for the quick and efficient support. There was indeed a antivirus tool running, Acronis Cyber Protect. As soon as we stopt Acronis the installation finished without any problems.

Vladislav Vaintroub added a comment - 2025-04-15 22:40 added some retry loops around affected APIs. It is still only the best effort, not much to do against antivirus if it appears buggy.