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
    2014-12-03T15:44:57+00:00

    Good luck Tim.  I too I have produced big posters on Publisher 2010 and found it very good.  I am now confident that I can produce them on 2013 too, although I've not done any recently.  I use 2013 for lots of things including producing pdf files, photo collages and web based magazines and it does have advantages over 2010, once it started to work.  I reverted to 2010 and then one day I tried 2013 again almost unintentionally and found it all working properly.  Try periodically?  Good luck.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-12-03T15:08:34+00:00

    Thank you John, I did verify that I am at the most recent Office 2013 update release level. I've done very large image project (24" x 36") in Publisher 2010 including a highly detailed poster size publication that combined high resolution photos, graphic elements and text which I printed on a large format plotter. No lags or issues with manipulating all of the different elements. My current project involves one simple 11x14 photo with one shape object and one text box. The project still needs some adjustments. Just dragging out and resizing a text box can take over one minute. I've scoured the internet and have yet to find any other resolution. I'm quite educated on computer and network hardware and software and performing troubleshooting.

    I've created an environment to troubleshoot in an effort to isolate and identify this problem. That environment maximizes all of the PC hardware resources, with ALL extraneous non-essential applications, drivers, processes and services removed from the environment. I've tried alternate photos and photo formats (JPG, PNG, TIF, etc.) to confirm that problem is not related to a corrupt image file or corrupt metadata associated with the image file.

    It's frustrating and confounding when I see Microsoft MVPs responding to these type of posts with ineffective suggestions with no apparent means for them to communicate these issues to engineering and development.

    I appreciate your comments and understand that you're not an MVP, just another user and contributor such as myself.

    Thanks, Tim

    Was this answer helpful?

    0 comments