System Workbench for STM32

Installed Eclipse CDT and then The openSTM32 plugins.
It was working properly before the update.

Now it just fails with

Open On-Chip Debugger 0.9.0-dev-00418-g9afb8b4-dirty (2015-09-28-12:09)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 300 kHz
adapter_nsrst_delay: 100
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 300 kHz, using 240 kHz
Info : Unable to match requested speed 300 kHz, using 240 kHz
Info : clock speed 240 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : STLINK v2 JTAG v24 API v2 SWIM v11 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.237246
Error: init mode failed (unable to connect to the target)
in procedure 'init'
in procedure 'ocd_bouncer'

Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333

Error message from debugger back end:
localhost:3333: Le système a tenté de joindre un lecteur à un répertoire stocké sur un lecteur joint.
localhost:3333: Le système a tenté de joindre un lecteur à un répertoire stocké sur un lecteur joint.

I desinstalled and reinstalled STLlink drivers, both: STSW-LINK004 and STSW-LINK009 multiple times without success.
My card is a Nucleo L152RE. As I said, it was working before the update.

I can access my nucleo board properly using ST-Link Utility.

21:52:11 : ST-LINK SN : 0672FF495056805087185238
21:52:11 : ST-LINK Firmware version : V2J24M11
21:52:11 : Connected via SWD.
21:52:11 : SWD Frequency = 1,8 MHz.
21:52:11 : Connection mode : Connect Under Reset.
21:52:11 : Debug in Low Power mode enabled.
21:52:11 : Device ID:0x437
21:52:11 : Device flash Size : 512KBytes
21:52:11 : Device family 😕TM32L15xxE/L162xE

The Eclipse Debugging is also working properly with my Discovery STM32F407VG.
I use both the std script for the discovery or a custom script with STLink V2 and SWD

All my projects are generated with CubeMX.

Since it's working with the Discovery I really think problem is related to STLink V2.1..The discovery is using STLink V2 and Nucleo STLink V2.1.My Drivers Installation shouldn't be the problem since it's working with STLink utility and Eclipse with Discovery board.

Emblocks has the same kind of problems with Nucleo.