PostgreSQL 9 install on Windows: “Unable to write inside TEMP environment path.”

Question

I am attempting to install PostgreSQL 9 (postgresql-9.0.3-1-windows.exe) on my WinXP machine and get the following error at the start:

Answer 1

I had the same problem in Windows 10 and the culprit was the OS's permission, or rather the lack thereof, on allowing the executable to write on the User dedicated Temp folder.

Solved it by following my gut and changing the User Temp folder to the same with the system's : Win + Pause/Break to have the Computer Properties window appear (you can do that manually by right-click on Computer icon on Desktop -> Properties) -> click on Advanced System Settings on the panel on the left -> click on Environment Variables and under "System variables" - Variables, find the TEMP and TMP ones and copy their paths. Then, under "User variables for Administrator" - Variables, find the TEMP and TMP ones and paste the paths. It's most always "C:\Windows\TEMP" anyways ;)

There's this site I read : https://www.askvg.com/where-does-windows-store-temporary-files-and-how-to-change-temp-folder-location/

Answer 2

it happens when Notepad++ associates .vbs file types. you can open notepad++ -> Preferences -> fileAssociation Remove the .vbs from the registered exts. Close the notepad++. Try installing Postgres again.

Answer 3

In the temp directory, my bitrock_installer.log file had the following:

Executing cscript //NoLogo "C:\Users\MyUser\Local 
Settings\postgresql_installer_1b4eec8be6\prerun_checks.vbs"
Script exit code: 1

Script output:
Input Error: Can not find script file "C:\Users\MyUser\Local 
Settings\postgresql_installer_1b4eec8be6\prerun_checks.vbs".

Turns out that Windows has a symlink between the following directories:

• C:\Users\cpetrie\Local Settings\Temp
• C:\Users\cpetrie\AppData\Local\Temp

For some reason my "TMP" and "TEMP" user variables were referencing the "Local Settings" path instead of the "AppData" path. Changing this fixed my install issue.

Answer 4

The answer in the following page helpped me. http://forums.enterprisedb.com/posts/list/3040.page

1. run-> regedit and take backup of registry using export
2. HKEY_LOCAL_MACHINE->SOFTWARE->Classes->CLSID->B54F3741-5B07-11cf-A4B0-00AA004A55E8} -> InprocServer32
3. Modify registry entry with new value as C:\Windows\System32\vbscript.dll

In fact, I found there are 3 entries of HKEY_LOCAL_MACHINE->SOFTWARE->Classes->CLSID->B54F3741-5B07-11cf-A4B0-00AA004A55E8}, and set the first one as above, it works.

Answer 5

This is a an old thread, but I just had the same problem on windows 10:

Unable to write inside TEMP environment path

Solve by the following steps

1. Check that the problem is related to Windows Script Host.
2. From cmd run wscript.exe
3. If you get an error Windows Script Host is not enabled and you can solved it by running from cmd

Fix for Current User

REG DELETE "HKCU\SOFTWARE\Microsoft\Windows Script Host\Settings" /v Enabled /f

Fix for Local Machine

REG DELETE "HKLM\SOFTWARE\Microsoft\Windows Script Host\Settings" /v Enabled /f

No you can install psql

Answer 6

In my case Changing the (Default) key in the HKEY_CLASSES_ROOT, .vbs section of the registry to VBSFile solved it. BlueFish is grab .vbs file association.