Re: BUG #18572: Crash during postgresql-16.3-2-windows-x64.exe installation
От | Sandeep Thakkar |
---|---|
Тема | Re: BUG #18572: Crash during postgresql-16.3-2-windows-x64.exe installation |
Дата | |
Msg-id | CANFyU94p5AGkOqY1YLN_QKEz1pmsj85FOKvNHB1PDXOPpsFwdA@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #18572: Crash during postgresql-16.3-2-windows-x64.exe installation (PG Bug reporting form <noreply@postgresql.org>) |
Список | pgsql-bugs |
Hi Paul,
I've shared a test installer with the fix with you. Can you please check the inbox for the ShareFile location of the test installer postgresql-16.3-0.0snapshot10215430698.828.1.2cb8f3d.2-windows-x64.exe
I've shared a test installer with the fix with you. Can you please check the inbox for the ShareFile location of the test installer postgresql-16.3-0.0snapshot10215430698.828.1.2cb8f3d.2-windows-x64.exe
On Wed, Aug 7, 2024 at 2:00 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:
Bug reference: 18572
Logged by: Paul Tobey
Email address: ptobey@rainbird.com
PostgreSQL version: 16.3
Operating system: Windows 10
Description:
When installing on Windows 10 I've hit this error, displayed in a dialog
during unattended mode installation:
"Error copying file from packed archive [location] to [temp
folder]/prerun_checks.vbs: Destination not writable" with Abort, Retry,
Ignore
If I Abort, the follow up message is:
"system's temp folder is not writable by the current user"
The folder *is* writable by the user running the exe (who is a member of the
Administrators group, BTW). I've captured the
installbuilder_installer_[number].log file, but there's nothing very
obviously useful there (I've obfuscated my domain and user names):
Log started 08/06/2024 at 12:49:31
Preferred installation mode : unattended
Trying to init installer in mode qt
Mode qt successfully initialized
Setting variable whoami from C:\WINDOWS\System32\whoami
Script exit code: 0
Script output:
[mydomain]\[myusername]
Script stderr:
As I recall, there was a similar issue in Windows Server for a time, fixed
in 16.3-2. There still seems to be a problem in the Win 1x OSes.
Sandeep Thakkar
В списке pgsql-bugs по дате отправления: