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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-07-02T14:22:18+00:00

    Sorry for not being clear.  I have used the tool to compress all the pictures in the document and this has not solved the problem.  I assume this is the way to do this? Is there another tool for doing this other than clicking on each picture?  And also I apparently did not make clear the level of frustration I am experiencing as the deadline for this publication fast approaches and it takes minutes just to move a text box...thus the venting as an attempt to make the MS folks understand that this needs to be fixed.

    I posted my solution before on '13th April 2015'

    In short:

    Just****disable the 'Page Navigation' !!!!!!!!!!

    One can alternative with either CTRL+PageUp or CTRL+PageDown navigate between those pages or use CTRL+G to directly go to the different Pages.

    So what happens, when you disable 'Page Navigation' in Publisher 2013? (Ribbon\View\Show\Page Navigation)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-08T14:19:52+00:00

    Thanks for your more detailed explanation of your particular situation.

    I am afraid that there is some other variable that has not been discussed in this thread that contributes to or causes this lag time in Publisher 2013 for some users. As I said before I do not have this problem with my installation of Pub 2013 and have not been able to recreate it. Some users experience it, some don't and some like John Duxbury boot up one day and find the problem gone.

    I would like to hear from you if hiding the pictures and working with just picture placeholders does alleviate the problem for you. I still tend to think that at least one big part of this problem is with how Publisher 2013 handles graphics and the changes made along with the removal of the Fast Zoom picture option.

    With that said Pub 2013 has proven to be very buggy and is failing a lot of people in a lot of ways and if you have the option of moving back to Pub 2010 or even older then that might be your best choice. Many say that Pub 2007 was the best version. Though the older versions are no longer 'supported' I actually use Pub 2000 and 2003 for the majority of my production work. Given your part time needs, look around on Ebay and elsewhere and you might find an inexpensive older copy and that would work for you. You can even do a custom install and run both the older version and Pub 2013 at the same time.

    Other frustrated users have moved to Serif PagePlus which has a free version http://www.serif.com/desktop-publishing-software/ .

    Download the free version and within a few weeks Serif will start sending you offers of huge discounts on their most current paid versions.

    Another free option is Scribus :

    http://www.scribus.net/canvas/Scribus

    LibreOffice 4.0 also free and supports importing Microsoft Publisher documents for the first time:

    http://www.theregister.co.uk/2013/02/08/libreoffice_40_ships/

    Adobe InDesign: $20/month: https://creative.adobe.com/plans?single_app=indesign

    Office 2016 and Publisher 2016 is now available for public preview and hopefully this problem will be fixed when the final product is RTM. Note: do not install this beta unless you are willing to overwrite the Office installation currently on your computer. In fact most people should wait IMHO.

    Main Blog - http://blogs.office.com/2015/05/04/office-2016-public-preview-now-available/

    Instructions to get preview - https://products.office.com/en-us/office-2016-

    Once again if you get the chance please let us know if hiding the pictures and working with just picture placeholders does alleviate the problem for you. Confirmation would help narrow down the cause of this issue. Sorry I cannot offer better solutions.

    DavidF

    Was this answer helpful?

    0 comments