Description: I have a strict rule: no application and/or non-system programs in my (Win10) system volume. In attempting to install Libre Office via the 'Custom' branch, I was able to configure the program's features to my requirements, but the 'Install to:' are was blank and the 'Change' option greyed out. I was, therefore, unable to install. Actual Results: Try it. Expected Results: An installation other than to C: Reproducible: Always User Profile Reset: No Additional Info: Custom install should be just that...
Do you have admin rights on this computer, and have you tried running the installer with admin right? I am wondering if this is related to bug 94193.
I have administrator rights. Howeer, on attempting to run the installer 'as adminsrator' I found that the option isn't there: just 'Install' (bold), 'Uninstall' and 'Repair' (both greyed) I've deleted, downloaded again and tried from Desktop, but it was the same.
[Automated Action] NeedInfo-To-Unconfirmed
I can't reproduce with the 7.4.3 64bit MSI from https://www.libreoffice.org/donate/dl/win-x86_64/7.4.3/en-US/LibreOffice_7.4.3_Win_x64.msi The "Install to:" path is displayed normally, and the Change button does work. I was able to change the install location to my USB drive (D:). - Do you have any component selected in the frame above? Or are both "Optional Components" and "User interface languages" completely turned off? (Both with a red cross). You need at least one language selected to install. - What happens when you click "Next"? Maybe a screenshot of the dialog would help.
I have just attempted the install with a newly downloaded file. To the best of my recollection, I made the same adjustments to the selective lists as I did on previous occasions (leaving only English(UK)) selected in languages, but this time the default location appeared in the lower space. I am completely unable to account for this, though I know computing well enough to be almost certain that I've committed 'finger trouble', for which I tender all necessary apologies.
No problem at all, Ted! Thanks for reporting issues and for coming back to test them further, we appreciate it :) Marking as "not a bug" for now.