How to Delete MSO.DLL

Written by joshua benjamin
  • Share
  • Tweet
  • Share
  • Email

The MSO.DLL file is a part of Microsoft Office 2007, and most of the programs included with the suite make use of it. If the MSO.DLL file becomes corrupted, it can cause all your Microsoft Office programs to become unstable, and may also prevent you from doing a repair reinstall. It is possible to delete the file manually, but doing so involves editing the registry, and should only be attempted by experienced computer users.

Skill level:
Moderately Challenging

Other People Are Reading

Instructions

  1. 1

    Open the Start menu and type "regedit" into the Windows Live Search Box. Windows XP users should select the "Run" command and type "regedit" into the textbox that pops up. This opens the Windows Registry Editor.

  2. 2

    Navigate to the following registry key in the Editor window:

    HKEY_CLASSES_ROOT\TypeLib{2DF8D04C-5BFA-101B-BDE5-00AA0044DE52}\2.2\0\win32

  3. 3

    Locate the MSO.DLL file description in the registry key. This will tell you exactly where the file is located on your computer. Note this, as you will need to remember it later.

  4. 4

    Right-click on the registry key and then select "Delete" and "Yes" to completely erase the key. This will enable you to delete the MSO.DLL file off your hard drive.

  5. 5

    Navigate to where the MSO.DLL file is located on your hard drive, select it and press the "Delete" key. Confirm your choice to send the MSO.DLL file to the recycle bin.

Tips and warnings

  • Do not delete the registry key if there are other files besides the MSO.DLL file inside. Doing so may damage your computer. Contact Microsoft Support to determine if it is safe to delete the key if there are other files inside.

Don't Miss

Filter:
  • All types
  • Articles
  • Slideshows
  • Videos
Sort:
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the eHow.co.uk site, you consent to the use of cookies. For more information, please see our Cookie policy.