A family of Microsoft word processing software products for creating web, email, and print documents.
With Spelling and Grammar check off, my 40 page 30MB file with lots of images saved in less than 4 seconds. Over 45 seconds otherwise.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am using the latest Word 2013 RC in German. Allthough I am very pleased with the overall performance and features of this new version, I ran into some very annoying problems, that didn't exist with the latest Word 2010. These should be easy to reproduce:
I have no problems whatsoever with short documents. Can anyone confirm these problems with Word 2013 RC?
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
With Spelling and Grammar check off, my 40 page 30MB file with lots of images saved in less than 4 seconds. Over 45 seconds otherwise.
but it doesn't solved my problem! same as before. anyways thank u
Wait, you've assigned Microsoft's customers homework to fix problems with its software? This is almost always the solution proposed by any Microsoft-affiliated poster on these boards--it matters not the problem. This, imo, is precisely why people are switching to other productivity suites.
Yes! It's extremely annoying. Just the way NOT to treat paying customers.
I'd like to ooint out that I, although I have a work-around, is still troubled by the bug. I have lost important work several times because I've been forced to turn the background saving off.
Bad, Microsoft!
Hey, it seems MS has finally fixed the bug!!!
I've used the new Office 2016 for a while and saving is quick - even after I removed the work-arounds. In fact, it seems like a recent update has improved performance even further.
Has anyone read anything about this? Har MS actually acknowledged the existance of the bug, or just quietly fixed it?