[MDEV-30561] MSI Installer does not create shortcuts Created: 2023-02-03  Updated: 2023-08-01  Resolved: 2023-08-01

Status: Closed
Project: MariaDB Server
Component/s: Platform Windows
Affects Version/s: 10.11.1
Fix Version/s: 10.11.5

Type: Bug Priority: Major
Reporter: Leo Hendry Assignee: Oleg Smirnov
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Windows 10


Attachments: PNG File screenshot-1.png     PNG File screenshot-2.png    

 Description   

The installer appeared to complete, but no shortcuts in the Start menu were created nor was the PATH environment variable update, contrary to instructions here:
https://www.mariadbtutorial.com/getting-started/install-mariadb/
https://www.mariadbtutorial.com/getting-started/connect-to-mariadb/

I have been unable to locate any installation log, nor documentation on this discoverable by internet search. I will provide any logs if advised the location.



 Comments   
Comment by Vladislav Vaintroub [ 2023-02-03 ]

There are shortcuts.

You have to find them. Back in Vista and Win7 they used to be in a nicely organized folder, now only search tool knows where those folders are gone. They are not gone for MariaDB specifically, but for everything else. Installation logic did not change. PATH is not set, but there is a "command prompt (MariaDB..)" with the correct PATH.

The installation log is something that you have to create yourself, using standard procedure which is valid for any MSI package.

(from the elevated command window)
msiexec /i C:\path\to\package.msi /l*v C:\path\to\dir\install.log

Comment by Oleg Smirnov [ 2023-07-03 ]

I agree with wlad, Windows sometimes displays items in the Start Menu in a weird manner. However, I have tried to install few different versions of MariaDB on Windows 10 and haven't had problems with the shortcuts in the Start Menu:

leoleo, can you check your folder

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\MariaDB 10.11 (x64) 

after installation? If there are no shortcuts or no such folder we can investigate this further. Otherwise it looks like the installer has done everything it could.

Generated at Thu Feb 08 10:17:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.