OpenVPN Install and the Windows Path Environment variable
On Windows XP (and possibly newer Windows operating systems), the OpenVPN installation process creates a Path variable in the User section of Environmental variables by default; for deployment purposes, I would suggest this to be unwise. OpenVPN has been flawless for me with the USER Path addition, but adding a variable named "Path" in the user section will cause some other applications to loose their ability to look up the SYSTEM Path for needed files such as dynamic library links and executives. The Path variable in the User section overrides the System Path for some applications, including the Windows Security Center. If OpenVPN should have a Path entry, it should be appended to the SYSTEM Path and not the USER Path. The issue is not a bug to the OpenVPN software itself, but only to the Install package.
The average Windows user probably will not understand why some of their other software is not behaving well due to a simple Path addition of the Users section, which could cause blame to OpenVPN affecting other installed software (but is not the case).
Change History (9)
Component: |
Generic / unclassified →
Installation
|
Priority: |
major →
minor
|
Owner: |
set to Samuli Seppänen
|
Status: |
new →
assigned
|
Status: |
assigned →
accepted
|
Milestone: |
beta 2.3 →
release 2.4
|
Keywords: |
windows installer nsis added
|
Status: |
accepted →
assigned
|
Resolution: |
→ fixed
|
Status: |
assigned →
closed
|
This was posted to the SF.net bug tracker by somebody (anonymous).