Hi- Another frustrated user here (UK), but I am prepared to try solutions should MS come up with them, so others don't have the same sufferance. No- nothing suggested to date works- so why suggest it when it wasn't fully/ even tested?
My Office 2013 WORD document is 400 pages long, on brand new Sony Vaio PC, and save takes 42 seconds to save(!), with same symptoms of almost zero response etc. during this time. Very frustrating.
I've spent 22 years testing software for a major bank in London and can't believe the poor 'corrective' response to the problem, as with the other frustrated people here. Maybe MS testers should work first in an environment as I have where insufficient testing
could result in the loss of millions of pounds......
Surely your diagnostics should first be run on a known problematical document and the 'correction' tested with automated testing tools run on multiple relevant documents, with stress testing, regression testing, response testing, operability testing, reliability
testing, performance testing, etc., etc. Or perhaps MS doesn't have the resources?