Hi Tobias,
we can only investigate such issues if a customer raises a support case.
That means: no support case -> no fix.
I double checked and found that the issue you mentioned was reported by a customer in December through a support case.
The fix is currently planned for March 2016 CU.
Cheers,
Stefan
↧
Comment on January 2016 CU for SharePoint 2013 product family is available for download by Stefan Goßner
↧