This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
A desktop publishing application from Microsoft that focuses on page layout and graphic design.
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.
Perhaps uncheck the "use Office to sync files faster..." setting in SkyDrive.
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'.
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!
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.
Timothy2-11, very well recapitulated.
I now rely much more on my much older and less powerful work PC to edit my Publisher files than my 6-core (8Gb 1866 ram, r9 270x) home PC because the older computer has 2010 and my home computer has 2013.
I have contacted Microsoft support at least twice about this issue. The individuals I have spoken to were helpful and polite, but always incapable of solving this problem. In one series of communications, the operator even claimed to attempt to replicate the issue on their system but could not confirm the same problems.
This operator has also remote operated my PC but I do not think he conclusively proved or solved anything with that attempt either.
My partner works in publishing and has scoffed at my use of Microsoft Publisher for professional applications in the past. I am a research scientist and have happily used Publisher 2010 for many years to edit and compose camera and microscope images for my personal records and for public presentations. It was my experience with Publisher 2013 that has caused me to reconsider my partner's advice and to rethink my use of Microsoft editing and compositional software for professional uses.
My recollection of conversing with Microsoft support was that the operators found it hard to comprehend that a user could be regularly managing documents consisting of tens to hundreds of very high resolution images with annotations. These images are, of course, overkill for printing and 'publishing' purposes, but perhaps it should be considered that some people may wish to edit, compose, and store original resolution images in the Publisher work space before flattening and compressing for publication?
Anyway, I am not sure I have added too much to this thread except, perhaps, another voice for (hopefully) Microsoft developers to hear.
Experiencing same problems
System Info:
Did all of the following:
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.