Why is running openvpn so DIFFICULT on Windows compared to Linux?

Why is successfully running openvpn so DIFFICULT on Windows compared to Linux?

On Linux, here is all you do:
1. You install openvpn
2. You download an ovpn config file from vpngate.net
3. You run the openvpn command as root: $ sudo openvpn --config filename.ovpn

That's it. It just works.

On Windows 10, I've been trying to get OpenVPN to work for an hour.
I'm ready to break the machine in half.
What is so difficult about these three steps?

1. You install openvpn
2. You download an ovpn config file from vpngate.net
3. You run the openvpn command as Administrator.

The Windows installer seems to create 3 files:
a. openvpngui.exe
b. openvpnserver.exe
c. openvpn.exe

I right clicked on each of them to check properties and then to set
the "Compatibility" tab to run as Administrator for all users.

Then I right click on the openvpn config file downloaded from
vpngate.net (which works just fine on Linux so I know the ovpn
configuration file is good!) and try to run with the openvpn
daemon, but it fails to connect every time.

I put a dozen ovpn files from vpngate.net into the directory:
C:\Program Files\OpenVPN\config\*.ovpn

And then I run the OpenVPNGui.exe shortcut, but again, a terminal
window pops up and the openvpn file is processed, and it says it
ran successfully - but I don't get a new IP address when I go to
http://whatismyipaddress.com

Why is running openvpn with a config file so dead simple with
Linux yet so dastardly complicated in Windows 10?

What the heck am I doing wrong?

On 2015-12-24, Mark Bannon wrote:
Why is successfully running openvpn so DIFFICULT on Windows compared to Linux?

On Linux, here is all you do:
1. You install openvpn
2. You download an ovpn config file from vpngate.net
3. You run the openvpn command as root: $ sudo openvpn --config filename.ovpn

That's it. It just works.

On Windows 10, I've been trying to get OpenVPN to work for an hour.
I'm ready to break the machine in half.
What is so difficult about these three steps?

1. You install openvpn
2. You download an ovpn config file from vpngate.net
3. You run the openvpn command as Administrator.

The Windows installer seems to create 3 files:
a. openvpngui.exe
b. openvpnserver.exe
c. openvpn.exe

I right clicked on each of them to check properties and then to set
the "Compatibility" tab to run as Administrator for all users.

Then I right click on the openvpn config file downloaded from
vpngate.net (which works just fine on Linux so I know the ovpn
configuration file is good!) and try to run with the openvpn
daemon, but it fails to connect every time.

I put a dozen ovpn files from vpngate.net into the directory:
C:\Program Files\OpenVPN\config\*.ovpn

And then I run the OpenVPNGui.exe shortcut, but again, a terminal
window pops up and the openvpn file is processed, and it says it
ran successfully - but I don't get a new IP address when I go to
http://whatismyipaddress.com

Why is running openvpn with a config file so dead simple with
Linux yet so dastardly complicated in Windows 10?

What the heck am I doing wrong?


Probably be best to ask in a Windows group, rather than a Linux group.
More likely to get the approriate expertise there.

Mark Bannon wrote:
Why is successfully running openvpn so DIFFICULT on Windows compared to Linux?

I put a dozen ovpn files from vpngate.net into the directory:
C:\Program Files\OpenVPN\config\*.ovpn

What the heck am I doing wrong?

You're not supposed to be putting configuration
files into C:\Program Files folder. Windows has
a compatibility feature, where it actually stores
the files you place there, in a Roaming location,
and only makes it "look" like you were successful.

C:\Program Files is owned by TrustedInstaller. When you
use an installer program, Windows uses the TrustedInstaller
account, to work on the Program Files folder. And that
isn't even a full account - it is a token used by a
service, that does the work. TrustedInstaller permissions
are a security feature. You can't "log in" as TrustedInstaller
and "fake it".

There are other places where you put config files,
and that isn't one of them.

The success of your project, is a function of
the developers working on it. Why should the
OS automagically repair a stupid design ?

It's up to the developers to design good software.
Find their bug tracking list or forum, and ask them.

People who are not Windows developers seem to have
a hard time with this. And you can usually tell,
what kind of developers you're dealing with, just
by the nature of how you're expected to install stuff.

If you want to see how to write an installer, watch
how VirtualBox installs in Windows. It has a program
installer, but it also installs a series of filter drivers,
it interacts with the networking stack. And other
than clicking "OK" to each driver install, the
process is automated. The software even knows
how to upgrade an existing package, if it exists.

*******

Even if you are successful at what you're currently
doing, you should be aware that Win10 is subject to
frequent "service pack level" updates, and these
move C:\Windows to C:\Windows.old. If you have
a program that messes around with low level stuff
(like the TAP/TUN component of your software),
on an upgrade install, those can be "kicked out"
of the OS. Even antivirus programs are subject to
this indignity - they can get kicked out on
an upgrade. As a user, you should be aware of
this possibility and be prepared to re-install.
The installer package should be prepared for the
eventuality, that it will need to "repair" an
existing installation (i.e. put the EXE or DLL back
that is getting removed). Many other things on a
repair, won't need to be touched or corrected.

This *is* a deficiency of Windows 10.

On previous OSes, the Upgrade Advisor would make a
list of software not compatible with the migration
to be done, so the user would be warned in advance.
In Windows 10, you only find out later, when your
**** is busted.

Paul

On Thu, 24 Dec 2015 00:09:38 -0500, Paul wrote:

You're not supposed to be putting configuration
files into C:\Program Files folder. Windows has
a compatibility feature, where it actually stores
the files you place there, in a Roaming location,
and only makes it "look" like you were successful.

All my systems are single-user, so, on Windows XP, I *never* used
the "C:\Program Files\" folder. I left it alone so it was only polluted
by programs that "I" didn't install. Likewise, the Documents folder
and all the idiotically named "My whatever" folders were also only
polluted by programs that I never touched.

This way, I kept all the data I actually *cared* about in only two
places.

I just created two folders and used them exclusively for *everything*.
c:\data\{subfolders}\== for *all* manually added user data!
c:\apps\{subfolders}\ == for *all* applications "I" installed!

An example for data subfolders would be:
c:\data\audio\{songs,books,recording,etc.}\
And an example for app subfolders would be:
c:\apps\editors\{picture,movie,audio,etc.}\

On Windows 10, I tried to replicate this, so, I first installed OpenVPN
into c:\apps\network\openvpn\ and I first put the configuration files in
c:\data\network\openvpn\*.conf

That seemed logical to me, given the absolute and utter mess that is
windows (of all incarnations). It's odd, but, I have lived for the past
twenty years needing only *two* folders on Windows, so, I don't see why
Windows 10 should ruin that.

But, openvpn would *not* work with putting the configuration files into
"c:\data\network\openvpn\*.conf".

So I uninstalled openvpn using ccleaner, and then re-installed it, this
time doing the horrid thing of letting it default to wherever it wanted
to pollute. Once I did that, it *expected* the ovpn files to be in
its own config folder.

So, the horrid location, by default, for openvpn, is the horridly polluted
and idiotically disorganized "Program Files" folder.
C:\Program Files\OpenVPN\bin\openvpngui.exe
And the just as idiotic location it expected for the config files was:
C:\Program Files\OpenVPN\config\filename.ovpn

But, even *that* didn't work.

1. So, using a rational organizational system didn't work, and,
2. Using the absolutely idiotic Windows un-organized system didn't work.

Hence my frustration.

What is the *correct* way to install openvpn, given that all it needs
is the executable and a configuration file run as Administrator?
openvpn --config filename.ovpn

On 24.12.15 6:37, Mark Bannon wrote:
On Thu, 24 Dec 2015 00:09:38 -0500, Paul wrote:

You're not supposed to be putting configuration
files into C:\Program Files folder. Windows has
a compatibility feature, where it actually stores
the files you place there, in a Roaming location,
and only makes it "look" like you were successful.

All my systems are single-user, so, on Windows XP, I *never* used
the "C:\Program Files\" folder. I left it alone so it was only polluted
by programs that "I" didn't install. Likewise, the Documents folder
and all the idiotically named "My whatever" folders were also only
polluted by programs that I never touched.

This way, I kept all the data I actually *cared* about in only two
places.

I just created two folders and used them exclusively for *everything*.
c:\data\{subfolders}\== for *all* manually added user data!
c:\apps\{subfolders}\ == for *all* applications "I" installed!

An example for data subfolders would be:
c:\data\audio\{songs,books,recording,etc.}\
And an example for app subfolders would be:
c:\apps\editors\{picture,movie,audio,etc.}\

On Windows 10, I tried to replicate this, so, I first installed OpenVPN
into c:\apps\network\openvpn\ and I first put the configuration files in
c:\data\network\openvpn\*.conf

That seemed logical to me, given the absolute and utter mess that is
windows (of all incarnations). It's odd, but, I have lived for the past
twenty years needing only *two* folders on Windows, so, I don't see why
Windows 10 should ruin that.

But, openvpn would *not* work with putting the configuration files into
"c:\data\network\openvpn\*.conf".

So I uninstalled openvpn using ccleaner, and then re-installed it, this
time doing the horrid thing of letting it default to wherever it wanted
to pollute. Once I did that, it *expected* the ovpn files to be in
its own config folder.

So, the horrid location, by default, for openvpn, is the horridly polluted
and idiotically disorganized "Program Files" folder.
C:\Program Files\OpenVPN\bin\openvpngui.exe
And the just as idiotic location it expected for the config files was:
C:\Program Files\OpenVPN\config\filename.ovpn

But, even *that* didn't work.

1. So, using a rational organizational system didn't work, and,
2. Using the absolutely idiotic Windows un-organized system didn't work.

Hence my frustration.

What is the *correct* way to install openvpn, given that all it needs
is the executable and a configuration file run as Administrator?
openvpn --config filename.ovpn


Try openvpn --config put the complete filefath herefilename.ovpn

Mark Bannon wrote:


So, the horrid location, by default, for openvpn, is the horridly polluted
and idiotically disorganized "Program Files" folder.
C:\Program Files\OpenVPN\bin\openvpngui.exe
And the just as idiotic location it expected for the config files was:
C:\Program Files\OpenVPN\config\filename.ovpn

But, even *that* didn't work.

The package uses NSIS (Nullsoft) installer.

Most of the installer is just an "unzipping into Program Files"
routine. They're taking advantage of the ability to get
Windows to use TrustedInstaller, to allow files to be
unpacked into Program Files.

But this process does *not* vet the correctness of
what the developers are doing. The following folder,
is a violation of Windows best practice. It's deprecated.
A mechanism is present in Windows, to allow old installers
to continue doing this. but when you edit a file in
there and save it again, it's going to end up in
Roaming. Everything still works. But, you are effectively
prevented from writing (and committing exploits)
of the Program Files folder. In effect, Microsoft
corrects the mistaken design, by keeping the files
in Roaming. It takes a bit of effort on the users
part, to figure out exactly what has been done.

C:\Program Files\OpenVPN\config

The NSIS installer has two major components.

tap-windows.exe (installs TAP driver using an INF)
OpenVPN (deposits files in Program Files area)

The package then has "Easy-RSA" folder, containing
a series of .bat (script) files. The user is expected
to execute these in a particular sequence, in a
Command Prompt ("terminal") window, to effect a setup
and configuration.

To use Command Prompt, you can "cd" to the bin and
rely on "dot" being in %path% to find executables.
But a person new to using Command Prompt is not
going to know about this. And I regularly get chewed
out, if I answer a question, invoke Command Prompt,
and I don't give the user a mini-tutorial on using
Command Prompt.

In your case, at the moment, I don't know how familiar
you are with Command Prompt.

https://community.openvpn.net/openvp...ateDirectories

The "cd" command they suggest, could use a /d in it.
This protects users who happen to be on the wrong
partition when they start the process.

cd /d "C:\Program Files\OpenVPN\easy-rsa"

The Windows shell has environment variables, accessible
deep within the System control panel. The construction
of vars.bat, is an attempt to script the setting
of these things. Presumably they're going to end up
in the environment variable section. You could
also add them to the environment yourself. For
example, %path% is used on Windows, to help the
shell locate executables. And includes "." as well.


1. So, using a rational organizational system didn't work, and,
2. Using the absolutely idiotic Windows un-organized system didn't work.

The organization the developers used is not rational.
It is deprecated for starters.


Hence my frustration.

What is the *correct* way to install openvpn, given that all it needs
is the executable and a configuration file run as Administrator?
openvpn --config filename.ovpn

If you were expecting to run that on a regular basis
(i.e. not from that Command Prompt with the preparatory
"cd" command), you would want to make the path
absolute or something.

"C:\Program Files\OpenVPN\bin\openvpn.exe" --config "C:\Program Files\OpenVPN\config\filename.ovpn"

Using the double-quotes, prevents mis-interpretation
of a path with a space character in it. And is frequently
used in Shortcut icon setup.

I don't plan on installing this software, as there
might easily be significant changes I have to make
to my environment to get it working. For example, if
running a networking server, there might need to be
some means of resolving an IP address to find it.

The above web page, explains how to do it, and does
a better job of explaining it than the file I found
inside the actual installer.

Also, while the NSIS installer is running, and unpacking
things, it's going to run "tap-windows.exe" for you.
A dialog box will appear, asking for permission
to install TAP 0901. Windows has a bad habit of
placing this dialog behind the current dialog,
so you have to move stuff out of the way to make
sure a prompt is not waiting for you. And this
is actually considered to be a "feature" by some
people at Microsoft. I think this was introduced
around Vista timeframe or so.

*******

If you right-click Start in Windows 10, there
is an "Administrator" cmd.exe (Command Prompt)
window listed. This would allow all your
commands to be elevated. The elevation is
probably not necessary, except when perhaps the
server process starts. But it is available
if you're having trouble, and run out of
other things to try.

On Windows 7, you go to Start and type "cmd" in
the run box there. The first item the search
finds at the top of the resulting window,
you can right-click that item and select
"Run as Administrator" from the right-click menu,
That's how you get an administrator Command Prompt
in Windows 7.

Permissions in Windows are bizarre.

Administrator cannot modify any old thing it wants.
It's not "root".

TrustedInstaller owns Program Files. You should
not normally need to override this kind of ownership,
but there are a few corner cases where it is necessary.
If you use Task Scheduler, and schedule a task to run
a minute from now, that task will run with SYSTEM
account privileges. And you can then do stuff. I've
removed TrustedInstaller registry entries, using
a .bat file and Task Scheduler.

The SYSTEM account, if you check permissions on files,
it owns a lot of stuff, and is about as effective as
using (or trying to use) the Administrator account.
You cannot use Task Scheduler to launch an interactive
task, so you cannot run Command Prompt as SYSTEM, which
would greatly speed up hack jobs. That stopped working
after WinXP or so.

So everything can be modified, but it requires a lot
of trickery, and is mostly security theater. I'm not
convinced it is keeping a determine exploit out of the
computer.

*******

Carry out the procedure on the web page. If you get
stuck, there is an "error 5" or "error 0x80001234"
type of error, post back and someone can answer
your questions. Describe what step broke, what you
were trying to do, and maybe we can help.

But I don't really want to attempt to do all
the steps in that procedure, as what I'm doing
is highly likely to diverge from how you
interpret the instructions, and I won't learn
anything from it.

Steps I took:

1) Scanned the download EXE file with virustotal.com .
It was clean.
2) Run the NSIS installer in a VM. Not in my main OS.
Denied tap-windows.exe from finishing its install.
3) Stopped, and looked at the files installed.

Paul

On 2015-12-24, Mark Bannon wrote:
Why is successfully running openvpn so DIFFICULT on Windows compared to Linux?

It shouldn't be. I just installed OpenVPN on a Windows 10 system a few
days ago and did not run into any problems using the default installation
and locations for the config files. (I've installed it on numerous
Windows systems over the years, starting with XP.)

Possibly you have a configuration problem? OpenVPN configuration can be
complex. (For the most part I continue to use permutations of a working
configuration that I worked up in OpenVPN's early days.) Maybe a firewall
problem?

You may need to run the OpenVPN GUI with admin privileges. Though you do
not need to use the OpenVPN GUI at all if you don't want to. You can run
openvpn from the command line, or enable the OpenVPN service which will,
at boot time, automagically start up connections for configurations
found in the default location.

--
-----------------------------------------------------------------------------
Roger Blake (Posts from Google Groups killfiled due to excess spam.)

NSA sedition and treason -- http://www.DeathToNSAthugs.com
-----------------------------------------------------------------------------

On Thu, 24 Dec 2015 07:45:41 +0100, Sjouke Burry wrote:

Try openvpn --config put the complete filefath herefilename.ovpn

That works *if* "openvpn.exe" is in the path, and, if I can easily get to a
command line in Windows 10 (which I'm new to, and which is a disaster in
terms of organization - at least the way "I" want things organized).

In previous Windows I could get to the command line by "Start Run cmd",
but, in Windows 10, I can only accidentally click about until the "Run"
shows up.

Is there a quicker way, in Windows 10, to just get to the command line?
Is there still that "open command here" addon to the right-click folder menu?

NOTE: I used that right-click open-to-terminal-here before, but I really
haven't needed it much since "Start Run cmd" used to be so simple.

On Thu, 24 Dec 2015 15:05:17 +0000, Mark Bannon wrote:

In previous Windows I could get to the command line by "Start Run cmd",
but, in Windows 10, I can only accidentally click about until the "Run"
shows up.

Here's what I'm trying to get to the Win10 command line:

1. Start (MS symbol) (there's nothing there for "Run")

2. Start All Apps (what a ridiculous way to organize apps!)

3. Start Power (nope, "Run" is not there either)

4. Start Settings (this seems to simply be the control panel)

5. Start File Explorer (this default to the idiotic "Frequent Folders")

6. Start click like crazy eventually I get Run

So, what is the correct way to simply get to a command line in Windows 10?

On Thu, 24 Dec 2015 02:30:05 -0500, Paul wrote:

The package uses NSIS (Nullsoft) installer.

Paul,
You seem to know what you're talking about.
Which newsgroup are you on?
I'll remove the rest from the reply list.

Most of the installer is just an "unzipping into Program Files"
routine. They're taking advantage of the ability to get
Windows to use TrustedInstaller, to allow files to be
unpacked into Program Files.

Rest assured, I don't have *any* need to put things in the idiotically
named and hideously disorganized "Program Files" directory, let alone
the triply hideously disorganized set that Windows 10 seems to have:
C:\Program Files\{horrid disorganization, idiotically by brand name}
C:\Program Files (x86}\{more of the same}
C:\ProgramData\{same garbage as was in "Common Files" in the past}
etc.

For 20 years, I've been installing my programs into "C:\apps\"
using a simple and logical system organized by *function*:
c:\apps\archivers\{winzip,izarc,winrar,etc}
c:\apps\browsers\{firefox,ie,chrome,etc.}
c:\apps\cleaners\{ccleaner,avast,filedup,etc.}
etc.

For 20 years, my cascaded menu was the *same* functional sequence:
Start Menu archivers {winzip,izarc,winrar,etc}
Start Menu browsers {firefox,ie,chrome,etc.}
Start Menu cleanes {ccleaner,avast,filedup,etc.}
etc.

That is, you organize things by what you want to *do* - not by
idiotic methods such as alphabetically by brand name.

So, I didn't, at first, put *anything* into C:\Program Files\
when I first installed OpenVPN using the downloaded executable:
C:\data\software\network\openvpn\openvpn-install-2.3.9.I001-x86_64.exe

So, I will install *again*, after uninstalling both:
OpenVPN 2.3.9.I001
TAP-Windows 9.9.2

BTW, as an aside, you can't uninstall the "TAP-Windows 9.9.2" using
Ccleaner for some odd reason.

The error is "Error: 2 - The system cannot find the file specified."
In fact, you can't even delete the *entry* nor *rename* it using
CCleaner. So, yet again, Win10 is screwed up beyond understanding.

Anyway, now that I uninstalled what I could, I will reboot and
start fresh.

Please Paul, let me know what ng you are coming from and I
will remove the other two.

Mark Bannon wrote on 12/24/2015 10:51 AM:
On Thu, 24 Dec 2015 15:05:17 +0000, Mark Bannon wrote:

In previous Windows I could get to the command line by "Start Run cmd",
but, in Windows 10, I can only accidentally click about until the "Run"
shows up.

Here's what I'm trying to get to the Win10 command line:

1. Start (MS symbol) (there's nothing there for "Run")

2. Start All Apps (what a ridiculous way to organize apps!)

3. Start Power (nope, "Run" is not there either)

4. Start Settings (this seems to simply be the control panel)

5. Start File Explorer (this default to the idiotic "Frequent Folders")

6. Start click like crazy eventually I get Run

So, what is the correct way to simply get to a command line in Windows 10?


Click Start. The cursor is in the "Search programs and files" box.
Type cmd, click to open a command prompt.

But the easiest way is put a shortcut on your desktop. Right-click an
empty area of the desktop. Choose New - Shortcut. When asked for the
location enter: %windir%\system32\cmd.exe

In the next step name the shortcut whatever you like.


--
Ed Mullen
http://edmullen.net/
Tell a man that there are 400 billion stars and he'll believe you. Say a
bench has wet paint and he has to touch it.

On Thu, 24 Dec 2015 15:00:46 +0000, Roger Blake wrote:

It shouldn't be. I just installed OpenVPN on a Windows 10 system a few
days ago and did not run into any problems using the default installation
and locations for the config files. (I've installed it on numerous
Windows systems over the years, starting with XP.)

Hi Roger,
Let me know what ng you're on and I'll drop the rest in future replies.
You seem to know *how* to install it, so, that's great.
I just realized I didn't install the right version (I installed the WinXP
64-bit version but I didn't know there was a WinVista & later version!).

What I installed on 64-bit Win10: openvpn-install-2.3.9-I001-x86_64.exe
What I should have installed: openvpn-install-2.3.9-I601-x86_64.exe

Here's what I *want* to do (and will try, in a moment):

1. Download the standard OpenVPN Windows installer:
http://openvpn.net/index.php/open-source/downloads.html

2. Select the "Installer (64-bit) Windows Vista and later" link
http://swupdate.openvpn.org/communit...601-x86_64.exe

3. Run that installer (but) put the files where *I* want them!
Executable: c:\apps\network\openvpn\*.exe
Config files: c:\data\network\vpnconfig\*.ovpn

4. Download a few dozen ovpn config files from http://vpngate.net
(Given the max allowed by openVPN is 50 ovpn files per directory.)

5. Run openvpn pointing (somehow) to one of those config files!

The trick will be to actually run openvpn the easiest way that
Windows 10 allows, so, that's where I'll need your advice
(being mostly a Linux & WinXP user).

On Thu, 24 Dec 2015 11:07:47 -0500, Ed Mullen wrote:

But the easiest way is put a shortcut on your desktop. Right-click an
empty area of the desktop. Choose New - Shortcut. When asked for the
location enter: %windir%\system32\cmd.exe

In the next step name the shortcut whatever you like.

1. Since I have a cascade menu in Win10, I tried this trick in the folder:
Menu Browser {firefox,chrome,ie,etc.}

2. Unfortunately, there is only "New Folder" available; however, as you
noted, it works fine elsewhere (like on the desktop).

3. Then I simply moved the shortcut from the desktop to the cascaded menu
Menu Browser {cmd,firefox,chrome,ie,etc.}

Kewl!
Thank you for the great idea!

I noticed it started up in C:\WINDOWS\, which is a really dumb place to
start, by default.

Is there a way to make it default to the openvpn config file directory?
C:\data\network\openvpn\config\.

On Thu, 24 Dec 2015 11:07:47 -0500, Ed Mullen wrote:

Click Start. The cursor is in the "Search programs and files" box.
Type cmd, click to open a command prompt.

When I click "Start", I don't see any "search programs and files" box,
but I do see that "Life at a glance", "File Explorer", "Settings",
"Power", and "All Apps".

Anyway, it's crazy that it's this difficult to get to a simple
command line, so, I'll stick with the other method you showed me,
which was to put a shortcut to 'cmd.exe' in the cascaded menu
(which is all that I use anyway).

Menu Browser cmd.{lnk}

The only thing to add is for the cmd.lnk to open up in the VPN data
directory:
C:\data\network\openvpn\config\{file1.ovpn,file2.o vpn,file3.ovpn,etc.}

On 12/24/2015 12:07 PM, Mark Bannon wrote:
On Thu, 24 Dec 2015 11:07:47 -0500, Ed Mullen wrote:

Click Start. The cursor is in the "Search programs and files" box.
Type cmd, click to open a command prompt.

When I click "Start", I don't see any "search programs and files" box,
but I do see that "Life at a glance", "File Explorer", "Settings",
"Power", and "All Apps".

Anyway, it's crazy that it's this difficult to get to a simple
command line, so, I'll stick with the other method you showed me,
which was to put a shortcut to 'cmd.exe' in the cascaded menu
(which is all that I use anyway).

Menu Browser cmd.{lnk}

The only thing to add is for the cmd.lnk to open up in the VPN data
directory:
C:\data\network\openvpn\config\{file1.ovpn,file2.o vpn,file3.ovpn,etc.}



RIGHT click start