Word 2013: Extremely slow saving and pasting plain text in long documents

Anonymous
2013-01-16T14:12:48+00:00

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:

  1. Take a long document (*.docx) with at least 100 pages and try to save it. This takes forever - I can see the progress bar filling up slowly. It takes at least 10-20 seconds to save. During that process I cannot do anything within Word - not even scroll smoothly. It slows down to the point of almost freezing up. I didn't have this problem with Word 2010 on the same system.
  2. Take that same document (>100 pages) and try to copy&paste some text (for example out of Firefox) and paste it as plain text - this takes at least 1 to 2 seconds. I didn't have any kind of delay with Word 2010.
  3. Word 2013 seems to work ok with *.doc files - it's still slower than Word 2010 a lot faster than saving *.docx files.

I have no problems whatsoever with short documents. Can anyone confirm these problems with Word 2013 RC?

Microsoft 365 and Office | Word | For home | Windows

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.

0 comments No comments

163 answers

Sort by: Most helpful
  1. Anonymous
    2014-11-26T22:02:21+00:00

    I had this problem and tried all sorts of fixes. Disabling background saves works BUT you lose the autosaving and have to remember to save your work periodically. Eventually I noticed that documents created in 2013 saved without this delay whereas documents created in an earlier version of Word had the delay. Converting a document to the new format doesn't help one jot.

    The answer is simple:

    1. Save the original Word document in RTF file format
    2. Open a NEW Word 2013 document and import the RTF file
    3. Save the document in Word 2013 format

    Result - No extended delays when saving AND you can keep your background saves.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-11-26T18:37:06+00:00

    I agree Peter. The only thing you need to do to solve this issue is simply to disable background saves, which was already answered in this thread. I am not even sure what all that other stuff Dionysius mentions would help resolve.

    Was this answer helpful?

    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Anonymous
    2014-11-26T18:18:33+00:00

    Hello, Dionysius,

    Your entry puzzels me. Why go through all that trouble when it has been established that just one of your actions - disable background saving - solves the issue? 

    P.

    Hi all,

    I have been following this thread with interest, and struggling with this same problem, so let me report what I've done so far.

    First, clean up:

    • Deleted COM plug-ins
    • Repair install

    Then configuration changes:

    • Disable Hardware Acceleration
    • Remove internet from locations to save to
    • Disable background saving

    Results over the last 24 hours have been radically improved. I am working with a large and complicated document and so far response times have been much improved.

    I thank Stefan Blum and others here who have tried to engage the community and find solutions to this issue. My guess is that it could be multiple issues at once, on two levels: first, other programs can cause bad behaviors in Word and vice-versa; second, there may be multiple configuration options in Word that must be changed to avoid this behavior.

    I hope others continue to post their stories because in my experience, that is how debugging occurs: the user relates their configuration, the steps they took and the results they obtained, and the debugger tries to replicate the problem so they can fiddle with it and see if they can stop it from happening and/or understand what made it happen. For this reason, it is helpful for users to post their configuration, the process they used and exact results that occurred.

    I am considering submitting as a test document an out-of-copyright longer text, marked up with styles in a hierarchical manner as this seemed to produce the greatest slowdown.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-11-25T15:43:46+00:00

    Hi all,

    I have been following this thread with interest, and struggling with this same problem, so let me report what I've done so far.

    First, clean up:

    • Deleted COM plug-ins
    • Repair install

    Then configuration changes:

    • Disable Hardware Acceleration
    • Remove internet from locations to save to
    • Disable background saving

    Results over the last 24 hours have been radically improved. I am working with a large and complicated document and so far response times have been much improved.

    I thank Stefan Blum and others here who have tried to engage the community and find solutions to this issue. My guess is that it could be multiple issues at once, on two levels: first, other programs can cause bad behaviors in Word and vice-versa; second, there may be multiple configuration options in Word that must be changed to avoid this behavior.

    I hope others continue to post their stories because in my experience, that is how debugging occurs: the user relates their configuration, the steps they took and the results they obtained, and the debugger tries to replicate the problem so they can fiddle with it and see if they can stop it from happening and/or understand what made it happen. For this reason, it is helpful for users to post their configuration, the process they used and exact results that occurred.

    I am considering submitting as a test document an out-of-copyright longer text, marked up with styles in a hierarchical manner as this seemed to produce the greatest slowdown.

    Was this answer helpful?

    0 comments No comments