I am finding Publisher 2013 unbelievably slow, so slow as to be unworkable.

Anonymous
2013-03-25T23:19:54+00:00

I have a new laptop and it handles all programs well including Photoshop but Publisher 2013 is extremely slow.  Even highlighting text can take over a second.  Earlier versions of Publisher are fine.  Can anyone suggest a cause and a solution?

Microsoft 365 and Office | Publisher | For home

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
Answer accepted by question author
Anonymous
2013-03-25T23:31:57+00:00

Perhaps uncheck the "use Office to sync files faster..." setting in SkyDrive.

Reference: http://answers.microsoft.com/en-us/office/forum/office_home-office_install/microsoft-office-document-cache-sync-client/6b011698-e0d8-4cc0-b3c2-674ba2565fc3?page=1

DavidF

[Edit] After posting the above, I ran across another possible fix:

In Publisher go to File > Options > Advanced and check 'disable hardware graphics acceleration'.

Was this answer helpful?

9 people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2013-05-16T13:29:34+00:00

I also had this problem.  I didn't when I first installed Publisher, but after about a week it became so slow it was driving me crazy!  I tried all the options that were listed in this forum, and none of them helped.  I finally just ended up uninstalling Microsoft Skydrive all together - I wasn't using it anyway - and bam!  Problem fixed! Publisher now runs great!

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2013-05-03T18:43:53+00:00

I was struggling with the same slow unusable situation with Publisher 2013.    I dropped back to Publisher 2010.  I do not have the time nor would I expect to fuss around trying all these patches/delete patches/updates.

........editing earlier post.

I have pretty good efficiency editing a 68.9MB pub doc in Pub2010 but it was too big to save as jpg or pdf or anything other than .pub.   Switching back to 2013 I was able to create a  9.7MB pdf but still could not export a jpg.

Was this answer helpful?

0 comments

91 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-12-02T16:25:29+00:00

    Experiencing same problems

    System Info:

    • Windows 7 Professional, 64-bit
    • Quad Core CPU 1.77GHz
    • 8GB RAM
    • Nvidia 1GB Video Card

    Did all of the following:

    1. Ensured that Office is up to date (as of December 2, 2104)
    2. Selected (checked box) "Legacy Drag Preview"
    3. Selected (checked box) "Disable Hardware Graphics
    4. Closed all other applications and used Task Manager to "End Processes" for all other non-essential applications and programs running in the foreground and background.
    5. Ensured that maximum RAM in use, while Publisher is open and .pub file is opened, does not exceed 4GB (even though the operating system and Office version are 64-bit and should be able to use all of the available 8GB of RAM)
    6. Verified that CPU usage does not exceed 60% while performing edits on the .pub file
    7. Verified that hard drive usage does not exceed 60% while performing edits on the .pub file
    8. Verified that SkyDrive (OneDrive) is not installed.
    9. Verified that the problem occurs with newly created Publisher projects as well as existing files.

    I've spent almost 5 hours editing one file that would have taken me about 30 minutes on older versions of Publisher. This problem does not appear to be related to hardware capability constraints or conflicts with other applications (since all other applications, with the exception of McAfee, have been closed) and the symptoms precisely resemble most of the other experiences posted in this thread. I don't have my older versions of Publisher available so I could really use some solid information with regard to solving this problem.

    Was this answer helpful?

    0 comments
  2. 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