Exactly and why are only some of us getting this problem and not others? This has to be answered.
Time to collate - is everyone who is having this problem have a new mac? I got mine in Feb 16. Apple can't be ruled out of this if being objective about potential sources of the problem. All stats count.
When is MS going to send out a formal communication addressing this issue? As it is not fit for purpose their responsibiity is to communicate and address issues of compensation for tangible negative impacts - like loss of dissertations, client presentations
etc
I don't believe that a software bug takes this long to fix. It is simply not being prioritised and I believe this will go into next year. There are no negative financial implications for MS and we are a minority, albeit significant, for us (only).
I am fed up waiting on a response and want to know legally what can be done to pressure MS into taking responsibility.
As said, it does not take this long to fix - there will be a tiny team working on this and being channelled off into other priority areas as they arise with more direct financial benefit - like new products, different updates etc - as all teams are likely
overloaded with work and as all IT middle managers and independant software co's do - say yes to everything even when they know they can't deliver.
I just know this will be taking a 5 minute AOB slot in a weekly/fortnightly update and barely cited in reports with a 'keep on it lads' dismissal by tech leads.
So what are the options to get MS to move on getting this fixed -as clearly the current approach will not resolve the matter.