FaderPort.dll registration in Windows 10 post 1511 builds

I'm astonished (and disappointed) after purchasing the Presonus FaderPort today that a simple issue of registering the driver DLL for Sonar support is an issue. Wow - can't you simple create a Windows installation package that properly handles the security signing requirements for this dll? You are a software company. Is this a huge challenge or is this product just to far down on the priority list to assign resources to perform this task?