I would like to configure proxy settings in Notepad++ to allow downloads from the internet via a proxy. After searching how to do that from the net I understand that I need to do that in the Plugin Manager, via the Settings button. When I go to Plugins>Plugin Manager>Show Plugin Manager>Settings I get the dialog box below which does not give me any option for indicating the proxy settings. How do I get to the point that I need to indicate the proxy settings?
Open cmd and type:
cd /d C:\Program Files (x86)\Notepad++\updater
gup -options
A dialog comes up to set the proxy settings.
with version 7.6.6 (april 2019) (probably onwards), you can run notepad++ as admin, use menu '?' > Set Updater Proxy... close notepad++ and open it again as standard user.
From the command line we have to access to the \updater folder of Notepad ++
> cd /d C:\Program Files (x86)\Notepad++\updater
then :
> gup -options
The window for proxy configuration is displayed:
for 32 bit installation
create a file caleld gpupOptions.xml under updater folder where gpup.exe is present
file content
<GUPOptions>
<Proxy>
<server>proxy.com</server>
<port>8080</port>
</Proxy>
</GUPOptions>
If you want to set proxy for Plugin Manager, maybe you need to check this config file:
%AppData%\Notepad++\plugins\config\PluginManager.ini
There are proxy address and proxy port settings.
But in my personal experience, it's not working. Not sure what goes wrong.
I'm on Plugin Manager 1.4.9.0 with Notepad++ v7.5.6 (32-bit)
Related
I'm testing VSCode by first time and I configure my proxy in settings.json as recommended:
"http.proxy": "http://domain\user:pass#myproxy:port/"
But it doesn't work when I try to install new extensions I get a connected timeout error. I also try to configure the proxy as system environment variable with the same result.
Could you help me? Is it a bug or I'm doing something wrong?
Is there another way to download extensions?
Thank you very much!
start vscode with below command
code --proxy-server="xxx.xx.xx.xx:port"
add command in desktop for vscode
/usr/share/applications/code.desktop
Exec=/usr/share/code/code --proxy-server="xx.x.x.xx:xxx" --unity-launch %F
Setting Up VS code behind proxy (Proxy script pac file) in Windows 10 to install extensions and updates
Locate the Proxy script path from
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
From the proxy pac file locate the proxy server domain name/port details (chose one that allows internet connection if there are many)
In VS Code go to File > Preferences > Settings and search for "Proxy"
Enter the proxy server url in the Http: Proxy (http.proxy) setting field
Un-tick check box for Http: Proxy Strict SSL ( http.proxyStrictSSL)
Restart VS code
In VS code: File -> Preferences ->Settings.
{
"http.proxyStrictSSL":false,
"http.proxy":"http://USERID:PASSWORD#proxy.domain.com:3128"
}
It works for me. And will work for you too. It appears that in http.proxy you have added "domain" after "http://" which is not required.
I was having issues too. Try adding:
"http.proxyStrictSSL": false
to your settings.json file.
Here is a solution in Windows 7.
Change the system proxy to your proxy, like localhost:3128, in Internet Options => Connections => LAN Settings.
After a version (1.35.0 maybe), the proxy settings in the Settings of vscode seems not working.
My proxy is down as soon as I update.
Finally, I fixed the problem by changing the system proxy.
An official reference: https://code.visualstudio.com/docs/setup/network
As #Yan QiDonge mentioned you can do that.
But if you want to have a more generic solution, this is what I did.
What I did was, I went to Internet Options => Connections => LAN Settings, and then I checked the "Automatically detect setting" and un-checked all other boxes. and it worked like a charm!!!!!
If you are using yarn run this command it worked for me
"yarn config set strict-ssl false"
This worked for me
I want to run go install to install the tour, but I can't find the option to use a proxy for internet access. I don't need this just for the tour but for developing in Go in general.
How do I configure Go to use a proxy.
Go programs understand environment variables http_proxy and no_proxy, but that's not enough because go get uses source control managers for retrieving code. So you have to set HTTP proxy settings for your SCM too. Use this for Mercurial and this for Git.
http_proxy value can be like http://user:password#host:port/. User, password, and port parts are optional. no_proxy is a comma-separated list of servers that should not be connected through proxy. Its value can be like foo.com,bar.net:4000.
You can set these environment variables in your bash_profile, but if you want to limit their usage to go, you can run it like this:
$ http_proxy=127.0.0.1:8080 go get code.google.com/p/go.crypto/bcrypt
If that's what you always want, set this alias to avoid typing proxy part every time:
$ alias go='http_proxy=127.0.0.1:8080 go'
From now on you can use go normally, but it uses your HTTP proxy.
On Windows command line:
set http_proxy=http://[user]:[pass]#[proxy_ip]:[proxy_port]/
set https_proxy=http://[user]:[pass]#[proxy_ip]:[proxy_port]/
...then navigate to https://github.com/ and download the GitHub certificate (I set the name as goland_cert.cer)
...now execute the OpenSSL command to export this to PEM format
openssl x509 -inform der -in goland_cert.cer -out goland_cert.pem
...finally set the certificate in git global config
git config --global http.sslCAInfo C:/Users/[User]/certs/golang_cert.pem
This works for me:
alias go='http_proxy=http://127.0.0.1:1081/ https_proxy=http://127.0.0.1:1081/ no_proxy=localhost,127.0.0.0/8,::1 go'
Note: for someones, protocol may be different https_proxy=http://127.0.0.1:1081
you can also map http requests to socks5 traffic by using https://github.com/cyfdecyf/cow/
very handy if you are blocked by GFW
Add GOPROXY variable name and Variable value as your proxy in the System variable. This worked for me.
You may want check https://github.com/hmgle/graftcp,
$ graftcp-local/graftcp-local -h
Usage of graftcp-local/graftcp-local:
-config string
Path to the configuration file
-listen string
Listen address (default ":2233")
-logfile string
Write logs to file
-loglevel value
Log level (0-6) (default 1)
-pipepath string
Pipe path for graftcp to send address info (default "/tmp/graftcplocal.fifo")
-service string
Control the system service: ["start" "stop" "restart" "install" "uninstall"]
-socks5 string
SOCKS5 address (default "127.0.0.1:1080")
-syslog
Send logs to the local system logger (Eventlog on Windows, syslog on Unix)
If you already have shadowsocks listening on 1080, then you don't need provide any paramaters, just run graftcp-local, to proxy go get
$ ./graftcp go get -v golang.org/x/net/proxy
I solved this problem with the Go command setting some variables in the Win10 system.
Here ("Using the cf CLI with a Proxy Server") you can find the information described below, with images. Also you can read information about:
Format of https_proxy
Use SOCKS5 with cf v3-ssh
Set https_proxy in Mac OS or Linux
I included in this answer only information about W10 because is the one I tested.
Windows 10
Set the new path variable.
From the search box, type in path
Select and open "Edit the system environment variables (control panel)".
"System properties" window will open.
Select "Advanced" tab.
Press "Environment Variables" button, a window with the same name will open.
In "System Variables" section, press the "New" button. "New System Variable" window will open.
You'll now add the needed variable, fill the fields as follows:
Variable name: https_proxy
Variable value:http://yourUserName:userNamePassword#yourIPaddress:port
Lastly...
I tested the installation command line for go.
Open the console, and type in: go install github.com/isacikgoz/gitbatch/cmd/gitbatch#latest
That's an example from this project: https://github.com/isacikgoz/gitbatch
This worked on my particular W10 19043 system.
git config [--global] http.proxy http://proxy.example.com:port
git config [--global] https.proxy http://proxy.example.com:port
see https://github.com/golang/go/wiki/GoGetProxyConfig
I'm attempting to use PHPStorm's built-in VCS functionality on a windows machine. When I set it up to utilize svn+ssh, I get the following error:
Problems while loading file history: svn: E170012: Unable to connect to a repository at URL 'svn+ssh://user#svr/repo_path/trunk'
svn: E170012: Can't create tunnel
svn: E720087: Can't create tunnel: The parameter is incorrect.
The repository information is correct and I don't have any issues connecting via TortoiseSVN. I've attempted to configure it utilizing both TortoisePlink.exe and putty's plink.exe. I've used both Pageant and tried to provide the key at the command line.
I normally work with OS X and Linux environments, but that's not an option in this case and I'm not exactly sure what to check next and I'm not finding a lot online via google search. Any suggestions would be greatly appreciated.
I ran into the same issue and found this path to the solution: How to use svn+ssh with Tortoise SVN from the command line
In context of PhpStorm:
PhpStorm discontinued using SVNKit with svn >= 1.8 so it will not ask for your SSH credentials anymore as it did before but will depend on proper command-line clients to be available and configured.
Now, this works for me:
Load your private key with Putty pageant (double click on key and enter your password)
Add a SVN_SSH Windows environment variable with content: C:\\Program Files\\TortoiseSVN\\bin\\TortoisePlink.exe (Adjust to your path, but keep the double backslashes!)
Now, from the command line (restart command line window before trying)
echo %SVN_SSH% needs to give you the plink.exe path and you should be able to do a svn up on command line without entering your password.
Restart your PhpStorm and SVN should work.
I've spent quite time on the issue, yet still couldn't find the exact problem. One issue is about the 1.8 format of SVN with PhpStorm, it cannot handle the svn+ssh authentication. It is possible to use TortoiseSVN 1.8 but always sticking the 1.7 format in PhpStorm.
My final solution was to install TortoiseSVN 1.7, so that I can use it from the Windows menu as well and no formatting issues happen. Another setting necessary for me was unchecking the option under Version Control > Subversion.
[] Use command line client: svn
As the ssh executable, I use:
C:\Program Files (x86)\PuTTY\plink.exe
I want to run go install to install the tour, but I can't find the option to use a proxy for internet access. I don't need this just for the tour but for developing in Go in general.
How do I configure Go to use a proxy.
Go programs understand environment variables http_proxy and no_proxy, but that's not enough because go get uses source control managers for retrieving code. So you have to set HTTP proxy settings for your SCM too. Use this for Mercurial and this for Git.
http_proxy value can be like http://user:password#host:port/. User, password, and port parts are optional. no_proxy is a comma-separated list of servers that should not be connected through proxy. Its value can be like foo.com,bar.net:4000.
You can set these environment variables in your bash_profile, but if you want to limit their usage to go, you can run it like this:
$ http_proxy=127.0.0.1:8080 go get code.google.com/p/go.crypto/bcrypt
If that's what you always want, set this alias to avoid typing proxy part every time:
$ alias go='http_proxy=127.0.0.1:8080 go'
From now on you can use go normally, but it uses your HTTP proxy.
On Windows command line:
set http_proxy=http://[user]:[pass]#[proxy_ip]:[proxy_port]/
set https_proxy=http://[user]:[pass]#[proxy_ip]:[proxy_port]/
...then navigate to https://github.com/ and download the GitHub certificate (I set the name as goland_cert.cer)
...now execute the OpenSSL command to export this to PEM format
openssl x509 -inform der -in goland_cert.cer -out goland_cert.pem
...finally set the certificate in git global config
git config --global http.sslCAInfo C:/Users/[User]/certs/golang_cert.pem
This works for me:
alias go='http_proxy=http://127.0.0.1:1081/ https_proxy=http://127.0.0.1:1081/ no_proxy=localhost,127.0.0.0/8,::1 go'
Note: for someones, protocol may be different https_proxy=http://127.0.0.1:1081
you can also map http requests to socks5 traffic by using https://github.com/cyfdecyf/cow/
very handy if you are blocked by GFW
Add GOPROXY variable name and Variable value as your proxy in the System variable. This worked for me.
You may want check https://github.com/hmgle/graftcp,
$ graftcp-local/graftcp-local -h
Usage of graftcp-local/graftcp-local:
-config string
Path to the configuration file
-listen string
Listen address (default ":2233")
-logfile string
Write logs to file
-loglevel value
Log level (0-6) (default 1)
-pipepath string
Pipe path for graftcp to send address info (default "/tmp/graftcplocal.fifo")
-service string
Control the system service: ["start" "stop" "restart" "install" "uninstall"]
-socks5 string
SOCKS5 address (default "127.0.0.1:1080")
-syslog
Send logs to the local system logger (Eventlog on Windows, syslog on Unix)
If you already have shadowsocks listening on 1080, then you don't need provide any paramaters, just run graftcp-local, to proxy go get
$ ./graftcp go get -v golang.org/x/net/proxy
I solved this problem with the Go command setting some variables in the Win10 system.
Here ("Using the cf CLI with a Proxy Server") you can find the information described below, with images. Also you can read information about:
Format of https_proxy
Use SOCKS5 with cf v3-ssh
Set https_proxy in Mac OS or Linux
I included in this answer only information about W10 because is the one I tested.
Windows 10
Set the new path variable.
From the search box, type in path
Select and open "Edit the system environment variables (control panel)".
"System properties" window will open.
Select "Advanced" tab.
Press "Environment Variables" button, a window with the same name will open.
In "System Variables" section, press the "New" button. "New System Variable" window will open.
You'll now add the needed variable, fill the fields as follows:
Variable name: https_proxy
Variable value:http://yourUserName:userNamePassword#yourIPaddress:port
Lastly...
I tested the installation command line for go.
Open the console, and type in: go install github.com/isacikgoz/gitbatch/cmd/gitbatch#latest
That's an example from this project: https://github.com/isacikgoz/gitbatch
This worked on my particular W10 19043 system.
git config [--global] http.proxy http://proxy.example.com:port
git config [--global] https.proxy http://proxy.example.com:port
see https://github.com/golang/go/wiki/GoGetProxyConfig
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:
Some googling around yielded some advice that suggested Windows Scripting Host might be disabled. I've checked and WSH is definitely enabled, so it must be something else. Question is, what?
I can see a file called prerun_checks.vbs is created in %TEMP% and when I try to run this manually, I get the following:
Which looks like a permissions error. However, I am an Admin, and I've given myself full control of the temp folder and it's still not working.
Any help appreciated.
In my case the solution was related to NotePad++ being the default application for opening .vbs files. If you have the same situation, here's an elaborate solution:
http://igordcard.blogspot.co.il/2012/03/unable-to-write-inside-temp-environment.html
In a nutshell, in the registry, you need to go to HKEY_CLASSES_ROOT\.vbs, and set the (Default) entry back to the string VBSFile.
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
Check that the problem is related to Windows Script Host.
From cmd run wscript.exe
If you get an error Windows Script Host is not enabled then you can solved it by running the following 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
Now you can install psql
As I was finishing off my question above, our IT chap turned up and knew what the problem was immediately: it's McAfee. It prevents anything from running in a TEMP folder, including Windows Scripting Host scripts. Disabling McAfee for the duration of the installation fixed the problem for me.
So if you see this problem, try disabling your anti-virus.
The answer in the following page helpped me.
http://forums.enterprisedb.com/posts/list/3040.page
run-> regedit and take backup of registry using export
HKEY_LOCAL_MACHINE->SOFTWARE->Classes->CLSID->B54F3741-5B07-11cf-A4B0-00AA004A55E8} -> InprocServer32
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.
If anyone else is searching for information on this and doesn't have any luck here, you might want to look at:
http://wiki.postgresql.org/wiki/Troubleshooting_Installation
For follow-ups to the mailing list please read:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
Well, in my case nothing worked, and disabling McAffee needed a special ticket with my company's security team to actually do... so I installed using the binaries, by following this guide Helpful Guide.
In summary, download the binary from here, unzip it, go inside the pgsql folder, create log and data directories in there, and then open a command prompt, navigate to where the pgsql\bin folder is, and run initdb -U postgres -A password -E utf8 -W -D POSTGRESQL_ROOT\data
You can start and stop the server by running
"POSTGRESQL_ROOT/bin/pg_ctl" -D "POSTGRESQL_ROOT/data" -l "POSTGRESQL_ROOT/log/pgsql.log" start
and
"POSTGRESQL_ROOT/bin/pg_ctl" -D "POSTGRESQL_ROOT/data" -l "POSTGRESQL_ROOT/log/pgsql.log" stop
where POSTGRESQL_ROOT is the full path to the pgsql folder.
All the above did not work for me. I was getting an error like:
Script output:
CScript Error: Windows Script Host access is disabled on this machine. Contact your administrator for details.
so after a couple of googling i found the solution:
Navigate to the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Script Host\Settings
In the right panel, you will see Enabled. If you see the entry 0, it means that the Windows Script Host access is disabled on your Windows machine.
Double Click on it and give it Value Data 1 to enable it.
A value of 1 will enable Windows Script Host
A value of 0 will disable Windows Script Host.
for windows 10 navigate to
HKEY_CURRENT_USER\Software\Microsoft\Windows Script Host\Settings
To prevent further problems you should also exclude the data directory (where Postgres puts its data) from being scanned by your virus-scanner
In my case it was another application that caused the problem. Not Notepad++. To others who encounter this problem, you can diagnose it by first deleting all files in C:\Documents and Settings\UserName\Local Settings\Temp so that you'll be able to find the bitrock_installer.log easily when you try installing postgresql again and view the instructions in it. Changing the (Default) key in the HKEY_CLASSES_ROOT, .vbs section of the registry to VBSFile solved it.
I had this issue when trying to install the 32 bit version on Windows 7 64 bit.
Trying the install kit for 64 bit presented no errors, but the solutions presented by others are also valid.
In my case I've downloded McAfee removal tool
MCPR (McAfee Consumer Product Removal)
which cleaned up some tailings after McAfee uninstallation.
Some registry entries which previously had InprocServer32 values like 'c:\program files\common files\mcafee\systemcore\...' changed back to its original values:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32\(default) = vbscript.dll
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32\(default) = C:\Windows\SysWow64\vbscript.dll
After that I successfully installed PostgreSQL 9.3
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.
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.
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.
My problem was Smad-Av which disables Windows Scripts from running,
Only after going through this thread i remembered.
I just right clicked the Smad-Av icon and selected Allow Windows-Script & Office-Macro (Permanent).
I had the same problem with installing PostgreSQL (Unable to write in TEMP environment variable path), the problem was in Windows Script Host which was disabled (check the log file to see if this is your problem). enable it with register editor (run-->regedit) at this location Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows Script Host\Settings by setting its value at 1
For more details check this web link: http://1stopit.blogspot.com/2011/01/postgresql-83-and-84-fails-to-install.html
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/
search for "Registery Editor" and run it.
choose HKEY_CURRENT_USER => SOFTWARE => Microsoft => Windows script host => Setting (Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows Script Host\Settings)
open "Enabled" and change value data to "1".(you will find it with a vlaue of 0).
Happy coding!
Check the log in the system's TEMP directory (provided the installer is able to write into it).
There's lot of information about the errors.
My issue was that VBS files were associated with a text editor (probably the anti virus software is the culprit) .
Here you can find some reg edit scripts to revert to the default behaviour:
http://www.nilpo.com/2009/07/windows-xp/restoring-vbs-vbscript-script-file-file-associations/#more-107
Cheers
My solution is similiar to #5, with an Explantion of how and why McAfee ruins your vbscript registration.
Apparently, when I had McAfee antivirus software on my computer, it bashed the vbscript.dll registration that Windows Scripting Host needs to run .VBS files.
In the exported .REG file:
[HKEY_CLASSES_ROOT\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
#="C:\Program Files\Common Files\McAfee\SystemCore\ScriptSn.20120327211246.dll"
That SHOULD be changed back to "C:\Windows\System32\vbscript.dll" now.
McAfee apparently installs a DLL that hijacks the vbscript.dll in order to try to protect bad scripts from running. When I uninstalled McAfee in favor of Microsoft
Security Essentials, McAfee did not restore the registry paths ("not
my problem"), and the McAfee DLL, of course, was removed from the location during uninstall, so the vbscript.dll registration in fact pointed to NOWHERE and NOTHING.
There has to be a better way to write Antivirus software so that it doesn't disable the user's operating system when it is uninstalled, or when features
are turned off, or replace registration. See the following:
https://kc.mcafee.com/corporate/index?page=content&id=KB71660
I have a 64-bit OS. The registry path was changed in a number of locations.
The regular class ID should point to the "C:\Windows\System32\vbscript.dll" 64-bit file.
The "Wow6432Node" registry paths should point to the "C:\Windows\SysWOW64\vbscript.dll" 32-bit file.
Yes, the 64-bits are in the "32" folder and the 32-bits are in the "SysWOW64" folder. Microsoft didn't want to change the name of the main "System32" execution folder when it migrated to 64-bits.
HKEY_CLASSES_ROOT\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
C:\Windows\System32\vbscript.dll
HKEY_CLASSES_ROOT\Wow6432Node\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
C:\Windows\SysWOW64\vbscript.dll
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
C:\Windows\System32\vbscript.dll
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
C:\Windows\SysWOW64\vbscript.dll
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
C:\Windows\SysWOW64\vbscript.dll
Before you start messing with the registry, check if WSH is actually disabled or not. To do that run wscript.exe in the DOS box.
If you see a dialog box called "Windows Script Host Settings", WSH is enabled, and your problem with PostgreSQL installation must be related to something else.
If you get an error box that says "Windows Script Host access is disabled on this machine. Contact your administrator for details", WSH is disabled, and your problem with PostgreSQL installation may be related to it (or may be not).
For me, my problem was related to Windows script. I resolved this by right-clicking on smadav icon in the hidden icons in the task bar and checked "Allow Windows-script and Office-Macro (Permanent)". Then double click on the PostgreSQL setup again.
First go to registry Editor then choose HKEY_CURRENT_USER > software > Microsoft > Windows script host > setting > default > add value data to 1 and click Ok. done!
After disabling Smad Av, it still did not work. So, I right clicked on the Smad Av tray icon and I selected 'Allow Windows-Script & Office-Macro (Permanent)' and it worked.