Bug 128915 - Installation error - GetTempFileNameW failed
Summary: Installation error - GetTempFileNameW failed
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
6.3.3.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Installer-Windows
  Show dependency treegraph
 
Reported: 2019-11-20 11:57 UTC by xarx
Modified: 2022-06-23 03:48 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Installation log (7.49 MB, application/octet-stream)
2019-11-20 11:59 UTC, xarx
Details

Note You need to log in before you can comment on or make changes to this bug.
Description xarx 2019-11-20 11:57:34 UTC
Description:
Unable to install LibreOffice. The installation fails when trying to create a *.tmp file due to insufficient privileges to the system TEMP folder.
Installation log attached.

The following users and groups have FullControl for the system TEMP folder (including subfolders and files): SYSTEM, Administrators. The folder is owned by SYSTEM. Other application installation (*.msi) packages install without problems with these TEMP folder settings.

When I allow everyone to write to this folder, LibreOffice installation succeeds.


Steps to Reproduce:
1. Set the system TEMP directory privileges so that only SYSTEM and Administrators can write it (Full control), the folder is owned by SYSTEM.
2.Run the LO installation


Actual Results:
The LO installation finishes, but LO is not installed.

Expected Results:
LO is installed successfully.


Reproducible: Always


User Profile Reset: No



Additional Info:
LibreOffice_6.3.3_Win_x64.msi
Windows 7 Pro, x64
Comment 1 xarx 2019-11-20 11:59:59 UTC
Created attachment 155971 [details]
Installation log

The log was generated with the command

msiexec /i E:\Downloads\Software\Office\LibreOffice_6.3.3_Win_x64.msi /l*vx E:\Downloads\Software\Office\libreoffice633.log
Comment 2 Mike Kaganski 2019-12-11 06:28:54 UTC
Could you please run the following command:

    rundll32.exe sysdm.cpl,EditEnvironmentVariables

and tell which are the TEMP paths in both user's and system's sections there?
Comment 3 xarx 2019-12-12 14:00:58 UTC
More info:

User temp: B:\Users\xarx\Temp
System temp: B:\Users\SYSTEM\Temp

I am starting the installation from an administration account (xarx), but from a *non-elevated* console. It this situation the .msi installation asks for elevation, after confirmation it copies most of the files, and almost at the end it fails with the described error. It fails when trying to write the system temp folder.

The system temp folder has the following privileges set:

    B:\Users\SYSTEM>icacls Temp
    Temp NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F)
         BUILTIN\Administrators:(I)(OI)(CI)(F)
         BUILTIN\Users:(I)(RX)
         BUILTIN\Users:(I)(OI)(CI)(IO)(GR,GE)
         Everyone:(I)(RX)
         Everyone:(I)(OI)(CI)(IO)(GR,GE)

When I start the installation from an *elevated* console, it succeeds. Hence I deduce that the installation error is caused by an operation at the end of the installation that is probably not executed under the elevated privileges.
Comment 4 Xisco Faulí 2020-06-18 10:32:26 UTC
Hello Mike Kaganski,
Is the comment 3 of any value or do we need more input from the reporter ?
Comment 5 Mike Kaganski 2020-06-18 11:04:01 UTC
(In reply to Xisco Faulí from comment #4)
> Hello Mike Kaganski,
> Is the comment 3 of any value or do we need more input from the reporter ?

No idea. The proper Temp permissions, as set by Windows installation by default (on my Win10 Home) are:

> icacls C:\Windows\Temp
> C:\Windows\Temp BUILTIN\Users:(CI)(S,WD,AD,X)
>                 BUILTIN\Administrators:(F)
>                 BUILTIN\Administrators:(OI)(CI)(IO)(F)
>                 NT AUTHORITY\SYSTEM:(F)
>                 NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
>                 CREATOR OWNER:(OI)(CI)(IO)(F)

The difference in permissions might be the problem, of course.
Comment 6 Xisco Faulí 2021-11-23 10:44:52 UTC
Hello xarx,
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 7 QA Administrators 2022-05-23 03:38:17 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2022-06-23 03:48:30 UTC
Dear xarx,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp