The issue was solved by opening a ticket at MS support.

After a week or so they replied that it was identified as a bug within SQL Server and that it would be fixed in future versions.