I've tried them and it's hit or miss. The problem is in the code and there really is no "tweak" that will fix this. MS has to on their end.

You're very welcome.. there has been discussions about this issue here and so far it's an issue that MS has to resolve.

That's a known error in build 10130.. MS has received some feed back on that.