Windows Client 2.4.2 TAP gets APIPA after restart

[trico]

Hi,

To whoever it helps :

running the latest client 2.4.2 on Windows2008R2 and 2012R2
After installation and first start as service the TAP interface get the pushed IP
After service restart TAP get APIPA IP and stay in this status
Deactivate TAP interface and Reactivate it
Restart service and the interface get the right IP.

Deinstall client 2.4.2
Reinstall Client 2.3.15 in the same configuration : no more problem

Workarround :
Reinstall 2.4.2 and use a script to deactivate/reactivate the TAP NIC

Looks like this problem already occured in the past : regression ?

Best regards