On an elevated CMD to disable:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
To check what are the current settings run bcdedit on an elevated cmd
Be aware that although I had installed the drivers when the driver signature enforcement was off, as soon as I enabled it once again the drivers where back to not working with code 52.
Despite many guides which will advice you to follow the GUI approach to achieve a one off startup with the driver signature enforcement, this seems to be a quicker and more permanent solution.
This is certainly not an ideal solution but a good enough workaround.
Mikroelektronika has now released new drivers which fix the problem. They can be found at this link