= Introduction = Historically, there have been many, many client GUIs for OpenVPN. Practically all are work of a one person, and many of them are completely unmaintained. Here's a snapshot (12th May 2011) of native Windows GUIs from our [RelatedProjects related project] list: * [http://sourceforge.net/projects/openvpn-gui/ OpenVPN-GUI]. Based on [http://openvpn.se/ old OpenVPN GUI for Windows]. * [http://openvpn-mi-gui.inside-security.de/ OpenVPN MI GUI]. Based on [http://openvpn.se/ old OpenVPN GUI for Windows]. * [http://openvpn.jowisoftware.de/ OpenVPN Manager]. Latest changes ~4 months old. * [http://sourceforge.net/projects/securepoint/ OpenVPN Client Windows]. Latest changes ~12 months old. There are also tons of [https://community.openvpn.net/openvpn/wiki/RelatedProjects#Inactiveprojects inactive client GUI projects] and probably dozens of in-house client GUI implementations. This fragmentation of development effort hurts both users (who never get to use a really good GUI) and developers (who have to reinvent the wheel over and over again). OpenVPN project has distributed a [http://openvpn.se/ Windows GUI] with it's Windows installers for years, but core OpenVPN developers have put very little emphasis on developing the GUI; this is understandable, as it's outside the scope of the project. However, bundling an obsolete (released 2005) WindowS GUI gives people the wrong impression of OpenVPN's capabilities and limitations. So, a Windows GUI overhaul is definitely needed.