Alright! As mentioned in my previous blog post, we heard back from Microsoft about the fix for this issue and it looks like Microsoft will be rolling out the fix for this in October 2016 CU for SharePoint Server 2013. So, if you’re facing this issue in your environment, please wait for the October 2016 CU as that should include the fix for this.
Happy SharePointing!!!
![error]()