https://bugs.documentfoundation.org/show_bug.cgi?id=163159
--- Comment #2 from V Stuart Foote <[email protected]> --- When I msiexec admin install without a TARGETDIR= option, on my system the install goes to root of my D: drive. I'd grabbed a /L*v log, and see: MSI (c) (04:50) [10:51:51:233]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'D:\'. with subsequent: MSI (c) (04:50) [10:51:51:253]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'D:\'. MSI (c) (04:50) [10:51:51:253]: PROPERTY CHANGE: Modifying ProgramMenuFolder property. Its current value is 'C:\Users\vsfoote\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\'. Its new value: 'D:\'. MSI (c) (04:50) [10:51:51:253]: PROPERTY CHANGE: Modifying DesktopFolder property. Its current value is 'C:\Users\vsfoote\Desktop\'. Its new value: 'D:\Desktop\'. MSI (c) (04:50) [10:51:51:253]: PROPERTY CHANGE: Adding ApplicationProgramsFolder property. Its value is 'D:\LibreOfficeDev\'. MSI (c) (04:50) [10:51:51:253]: PROPERTY CHANGE: Modifying ProgramFiles64Folder property. Its current value is 'C:\Program Files\'. Its new value: 'D:\'. MSI (c) (04:50) [10:51:51:253]: PROPERTY CHANGE: Adding INSTALLDIR property. Its value is 'D:\LibreOffice Test\'. and the entire install following into that location. But the resulting administrative install is fully functional. And if I perform my typical parallel install with the TARGETDIR= property specified, I get a functional administrative install into that exact directory. Looking at the log the ROOTDRIVE property is still D: but the rest of the paths used follow what was set as TARGETDIR property. I've set aside both install logs should they be needed. -- You are receiving this mail because: You are the assignee for the bug.
