BUG #16341: Installation with EnterpriseDB Community installer in NT AUTHORITY\SYSTEM context not possible

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: pg(dot)dba(dot)iit(dot)team(at)gmail(dot)com
Subject: BUG #16341: Installation with EnterpriseDB Community installer in NT AUTHORITY\SYSTEM context not possible
Date: 2020-04-03 14:02:01
Message-ID: 16341-da91fcd90975c1a5@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16341
Logged by: Enrico La Torre
Email address: pg(dot)dba(dot)iit(dot)team(at)gmail(dot)com
PostgreSQL version: 9.6.17
Operating system: Windows Server 2016


it could be that the same bug was reported in
, but nobody answered until today.

It is impossible for me to install PostgreSQL 9.6.17 with the EnterpriseDB
installer (free Community Edition) on Windows Server 2016 in the security
context of NT AUTHORITY\SYSTEM. If I start the installer with a regular
domain admin account, which is also local administrator, the installer

I receive the error message:
"Error running icacls "C:\Windows\Temp/postgresql_installer_ca555e4059" /T
C:\Windows\Temp/postgresql_installer_ca555e4059\*: Access is denied"

I disclaimed The log file of the installer
'C:\Windows\Temp\install-postgresql.log' is never written.

SYSTEM has FULL CONTROL for 'C:\Windows\Temp'. Created directories in this
directory by SYSTEM inherit FULL CONTROL from the parent. But if I check the
temporary directory '.\postgresql_installer_ca555e4059' I see that the
inheritance is disabled for this particular directory. Only the principal

The same issue is also true for PostgreSQL 12.2. The last time this
procedure worked that I know is with the installer for PostgreSQL 9.6.12.

Kind regards


Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2020-04-03 14:40:13 Re: BUG #16340: lo_manage() crashs DB instance
Previous Message PG Bug reporting form 2020-04-03 13:46:15 BUG #16340: lo_manage() crashs DB instance