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.
Thanks but I think this is missing the point. Publisher is supposedly designed for producing high quality publications. It should be able to do these things and earlier versions of Publisher can manipulate the same files without difficulty. The problem therefore lies with Publisher 2013 which should be withdrawn from the market until these issues are addressed. There are too many of us reporting the same problem for it to be a hardware problem and so it must be something that has been changed for the 2013 edition that has caused the problem. In the meanwhile I have reverted back to the 2007 edition and have no problems. My biggest complaint is that I have paid for the 2013 edition and cannot get anyone from Microsoft to even acknowledge the problem, never mind issue a refund.
I understand what you are saying and am glad you have Pub 2007 to go to. In many ways I prefer it to not only Pub 2013, but also to Pub 2010.
At this point my goal is to try to define the problems with Publisher 2013 and the best 'fixes' or workarounds available to users until or if MS fixes these issues. I appreciate your help in identifying the specifics of this issue. Part of the challenge in finding solutions is that not every Publisher user is experiencing this 'slow down' issue. Further some of the 'fixes' help some, but not others. That is why I ask all the questions...I am trying to find the common elements among users that are experiencing the problem.
Anyway, this is all beside the point. I certainly appreciate your frustration and am not making excuses for MS. There are lots of things that I don't like about Pub 2013, and a growing list of 'bugs' that need to be fixed. Hopefully those fixes will come sooner rather than later.
DavidF
Thanks but I think this is missing the point. Publisher is supposedly designed for producing high quality publications. It should be able to do these things and earlier versions of Publisher can manipulate the same files without difficulty. The problem therefore lies with Publisher 2013 which should be withdrawn from the market until these issues are addressed. There are too many of us reporting the same problem for it to be a hardware problem and so it must be something that has been changed for the 2013 edition that has caused the problem. In the meanwhile I have reverted back to the 2007 edition and have no problems. My biggest complaint is that I have paid for the 2013 edition and cannot get anyone from Microsoft to even acknowledge the problem, never mind issue a refund.