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 No 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 No 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 No 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 No comments

91 additional answers

Sort by: Newest
  1. Anonymous
    2015-07-08T17:32:35+00:00

    Hi,

    As I mentioned in an earlier post, I moved back to Pub2010 because I couldn't solve the unresponsiveness and slowness issues in 2013.

    I have previously tried all the fixes in this thread and none of them have been satisfactory (IMO). I have also tried disabling 'page navigation' and this didn't work. Hiding pictures (Ribbon VIEW/'Graphics manager'/ bottom of new panel 'Change picture display'/'Hide pictures') does make the document responsive, but it's arguable whether or not this is a fix, since you are removing a feature most people find integral for checking aesthetics and quality control.

    As for compressing pictures before I have even settled on their correct arrangement in the document, I feel this contradicts the very notion of desktop/professional publishing. It may be acceptable when you are sure you will not be resizing images and only need to export to one source, but I would normally treat image compression as a terminal procedure, in preparation for document export to one's chosen media/publisher. Also, as has been mentioned by others, one can work without compressed images in Pub2010. However, for testing, I have just now copy and pasted a complex multi high-res image containing page from one of my active 2010 documents to pub2013. As expected this 2013 document was then very unresponsive. Incidentally, the images appeared down-sampled in normal view at the same magnification in pub2013 compared to 2010 (see screen shot crops - didn't control crop size but both images are similarly scaled and magnified[150% in publisher]).

    left pub2010, right pub 2013. I have also tried pub 2010 with fast resize and zoom option on and I obtained the same result.

    This is kind-of interesting considering publisher 2013 doesn't even offer a fast resize and zoom option for displayed images, but this is not the main topic of this reply.

    I then took about 15 minutes manually selecting each image in the new pub2013 document and 'Saving as picture...', choosing .png and 300dpi. I then used the 'Graphics Manager' panel to replace each original image with the newly created 300dpi version. This also made the document responsive. In fact this page may now be as-responsive, if not more so, than the original page in the pub2010 document. Therefore, some would consider this a fix. I personally prefer to know I have the original resolution image within the document, so will continue to use pub2010. This method would also be quite time consuming, as an additional step or if one wants to modify/fix existing large documents, although there may be way to integrate the required steps into a new SOP when beginning new documents so as to be less time intensive.

    Kind regards,

    Sponges...

    Was this answer helpful?

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