Though Microsoft Outlook 2010 is usually dependable, it can crash due to unidentified errors. When that occurs, you may discover finding the problem and repairing your Outlook deployment unexpectedly complicated. But it doesn’t have to be.
Reinstall Outlook 2010
This might seem clear, but the first thing you should attempt is reinstalling MS Outlook 2010. To reinstall Outlook 2010, open the Control Panel and click Programs -> Uninstall a Program (please note that this method is for Windows 7 only, your options may be dissimilar for other OS). Search and then click the MS Office 2010 option and then click the 'Change' button.
When the installation wizard comes out, opt for the "Add or Remove Features" option and then click Continue. Next, select the "Not Available" option for Microsoft Outlook and click Continue. This eliminates the risk of uninstalling the other Microsoft Office modules.
After you have eliminated Outlook, replicate the steps listed above, apart from this time set "Outlook to Run From My Computer"; this will reinstall Outlook on your system.
What if reinstalling Outlook 2010 doesn’t work?
As you might assume, the uninstall/reinstall technique doesn’t resolve each and every Outlook problem. I’ve observed quite a lot of occasions where the issue still subsists after reinstalling Outlook. Luckily, there are other methods available at your disposal:
Repair the Outlook user profile
When you discover that you have received an Outlook issue, it is not necessary that MS Outlook is damaged, but in fact it can be the user’s profile. Windows 7 contains an alternative to repair it.
Open the Control Panel and click User Accounts -> Mail (or Mail 32-bit) -> E-Mail Accounts. When the E-mail Accounts screen becomes visible, choose the Outlook account, you are having problem with, then the Repair icon . Then Click Next and follow the prompt; Windows will try to restore the account configuration.
Rebuild the Outlook user’s profile
If you discover that you can't restore the Outlook user's email account profile, you are required to manually remove and remake the user’s mail profile.
Though, prior to removing the mail profile of the user, you need to assure to take back up of any .pst files. Now, open the Windows Control Panel and click User Accounts -> Mail (or Mail 32-Bit) -> Show Profiles. When the dialog box prompts, choose the user profile and click the Remove button (Figure 3).
After you have removed the profile from the machine, open Outlook. Upon opening, Outlook should automatically detect the user’s Exchange mailbox and create a new profile. In a couple of odd cases, I ran into situations where Outlook could not create a new profile. Fortunately, I was able to manually create a working profile by going to the dialog box and clicking the Add button. I don’t normally advise this, but it’s worth trying if you’re stuck.
Try starting Outlook 2010 in safe mode
If the steps explained so far don’t fix your issue, then attempt to launch MS Outlook in safe mode and then open a command prompt window and enter the following commands:
Cd program files (x86)\Microsoft Office\Office14
Note: The path listed in the second step might differ depending on whether you are using the 32-bit or 64-bit version of Microsoft Office.
After opening Outlook in safe mode, take the time to conclude whether or not the trouble still subsist. If the problem has vanished, the problem is nearly surely due to an add-in.
Then Restart Outlook in normal mode and click File -> Options -> Add-Ins. Use the Add-Ins screen to sight that add-ins that are presently in use. Halt any third-party add-ins and re-enable them one at a time, all the while testing Outlook among each step to find out which add-in is causing the difficulty.
With anticipation at this point, you have cut off the reason for the issue. If not, there is one more thing you can check. Open the Windows Event Viewer and navigate to Windows Logs -> Application. Outlook logs all events in the Application log. The Microsoft Office Alerts logs are a new prospective resource of information which are positioned under the Applications and Services Logs.