Top 5 steps to repair Microsoft® Publisher 2010

One of the very useful applications available with the Microsoft Office 2010 productivity suite is Microsoft Publisher 2010. By using this program you can effortlessly create professional-looking brochures, calendars, newsletters, greeting cards and much more. Equipped with better features as compared to its predecessors, Microsoft Publisher 2010 is your only companion if you had to deliver good quality publication and marketing material.

However, as everything comes along with its share of woes, if you ever encounter any errors while working on this program, you may be required to repair Microsoft Publisher 2010. Although this may sound difficult, by following these simple five steps, you can have your application up and running in no time. So, sit back, relax, and go through the easy resolutions compiled for you below:

Step 1: Hit the ‘Start’ button and type ‘Programs and Features’ and select ‘Enter’.

Step 2: Select the ‘Microsoft Office Publisher’ option.

Step 3: At the top of the Programs and Features window, look for the ‘Change’ button and select it.

Step 4: Hit the ‘Repair’ option and start the process by selecting ‘Continue’.

Step 5: Once the repair process is over, select the ‘Close’ option to complete the process.

However, in case you were facing issues with a particular Microsoft Publisher 2010 file, and not the application as a whole, you will have to try out a different solution. To do it ‘Restart’ your computer in Safe Mode.

Once the computer has booted, try to open the Microsoft Publisher 2010 application. If it opens up, you can carry on with your tasks. In case it does not open up, you will have to paste the publication into the Publisher program file. To do this, you will have to locate the publication file and type C:\Program Files\Microsoft Office\Office11 in run (for Microsoft Publisher 2003). You will have to paste the copied publication file in the mspub.exe file.

In many cases, copying a file which isn’t opening to another computer also solves the issue. You may also consider running error checking on the disk to repair the errors.

Image by cjdc