stdole32.tlb in Excel

Anonymous
2012-12-18T12:58:33+00:00

I am running Windows 8, and I have just reinstalled Office 2007.  When I open Excel, I get a screen that shows stdole32.tlb and then office goes on to configure.  This happens each time I open up Excel.  How do I stop this?  I don't have the regedit function, that I used to have with prior versions of windows.

Microsoft 365 and Office | Excel | For home | Windows

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.

0 comments No comments
Answer accepted by question author
Anonymous
2012-12-19T09:32:06+00:00

Hi Susie,

Thank you for posting in Microsoft Community.

In addition to Chip's suggestions you may also follow the steps mentioned below and check if it helps:

Try the steps mentioned below and check if it helps resolve the issue:

Important: Ensure to back-up the registry before changing the registry keys:

http://windows.microsoft.com/en-us/windows7/Back-up-the-registry

·         Go to Run (press Windows+R key on the keyboard simultaneously) and type regedit

·         Navigate to the HKEY_CLASSES_ROOT > Excel.Chart.8

·         Right Click on key and select Permissions

·         In the Permission windows > click on Add tab and add Everyone

·         Once this is done, click on the Advanced tab > Owner > highlight Everyone > click on Apply and Ok

·         In the Permission > select Everyone > enable the check box for Full Control and Read then click on Apply and Ok

·         Click on F5 to refresh, this should create a new Sub key below Excel.Chart.8 called Protocol > right click on the key and repeat step 3 – 5.

·         Refresh again and follow the same sequence of steps to add permission to the following Sub keys StdFileEditing >Server.

·         Close the registry editor.

You may also refer the link mentioned below which discusses about the similar error message and check if it helps:

http://answers.microsoft.com/en-us/office/forum/office_2007-office_install/stdole32tlb-file-missing/ba3e940d-d628-4334-ac89-5e8ac9878093

I hope the above suggestions helps to resolve your issue. If you need any further assistance reply and we will be glad to assist you.

Thanks.

Was this answer helpful?

300+ people found this answer helpful.
0 comments No comments

117 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-11-06T20:16:27+00:00

    It's painful, am merely living with this error.  Please check other replies that have helped lots of peeps.  I'm not willing to uninstall and re-install Office 2007 on my new Windows 10 Dell desktop.  If necessary I'll take it to the shop and hope they do the re-install with my old disc.  I've done this before and usually end up with more issues.  Good luck.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-11-06T18:32:49+00:00

    I am running Office 2007 on Windows 10.  After installing and removing a more recent trial version of office I also have had a plethora of problems.  All are resolved except the EXCEL issues described in these posts.  [stdole32.tlb followed by installation each time I start up.]

    Maybe I am neanderthal, but I just can't find all the keys etc documented here to fix in Regedit.  Uninstalling EXCEL and wiping the EXCEL files from Program Files &  Program Files (x86) directories seems to remove the offending regedit keys - but after reinstall it all is the same.

    PLEASE PLEASE PLEASE send us a simple script to download & run & fix this issue!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-10-19T22:57:10+00:00

    Also meant to mention that I have a brand new Windows 10 Dell desktop and yet since I am still using Office 2007, the bug bit anyway.  Yes, painful.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-10-19T22:07:38+00:00

    THANK YOU - That was such an easy fix until I upgrade my computer!

    Was this answer helpful?

    0 comments No comments