stdole32.tlb in Excel

Anonymous

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.

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

Answer accepted by question author

Anonymous

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.

0 comments

117 additional answers

Anonymous

2018-02-14T13:37:54+00:00

Hi Russell

Yes the new version of Office is a major culprit.

The best fix, but you have to be a masochist to consider it now, is to reinstall windows 10, remove the new office from the Programs & Features.

The look on MS website, there's a 'Remove Office 365' I think it was called

This clears much of the garbage in folders & registry

Then in RegEdit, clear out the remaining bits of >Office13 nodes (you'd have thought MS' miodule would have done that but it doesn't!)

THEN

Reinstall Office 2007. I did that and it all runs OK now, not hiccups or other annoyances.

I have to use Office 2013 where it do voluntary work, and fail to see it offers any advantages over 2007, the ribbon is vastly inferior, and as I don't use mega excel spreadsheets I don't need 2010 or later
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-14T00:44:10+00:00

I am willing to accept that MS no longer supports Office 2007, but would like them not to break things in updates.

When I purchased a new Windows 10 PC, I was told Office 2007 would work. And it did work at first. The mistake I made was to select the option to update Office as well as Windows. After the first update to Office, I started to experience this stdole32 issue. My wife upgraded to Windows 10 from a Windows 7 Dell Laptop, has never updated Office, and has never experienced any issues with Office 2007 in Windows 10. I unsuccessfully tried the regedit fixes outlined on this support site. My only option was to reinstall Windows, reinstall Office 2007 and not select any updates to Office. This has worked and I no longer experience the stdole issue. I still experience an issue where MS Word does a new config when I open it and I am unable to open an Excel file directly. I have to open Excel 2007 first and then open the file. I think this is because I have an introductory Office 2016 install that came with the PC. So it goes...
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-13T23:06:24+00:00

I agree with most of what you say Opteron. Well I've gone back to win7 on a mainly offline machine. Still waiting for Bill Gates to come out of his Howard Hughes seclusion. Has IT reached its zenith...... who wants anything more than selfies and facebook. The dumming down aspects of IT are drawing us back into the dark ages. Kids, you're living in a virtual world so we only need virtual kids now. If only we could get the virtual kids to buy virtual trainers....

Most people don't use even 10 percent of Office2000 potential. Its only habit with me as I know Libreoffice can satisfy all my current needs if I'm pushed..... but I need my =sum() fix occasionally.

It all goes back to being suckered in to the free win10 upgrade without being made aware that some equipment wouldn't be supported ie inspiron.

Would you buy a second hand car from microsoft? sorry.... previously owned in newspeak.

And after the initial win10 which started lightening fast..... now it takes an eternity again usually while windows is getting my machine 'ready' and I can't tell what's eating up 400GB of disk space. It sure ain't me.

Just off to check out Chrome OS but not holding my breath
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-13T22:41:04+00:00

Honestly, I see many comments about expecting a fix from Microsoft. Office 2007 is 11 years old and has been officially unsupported for quite some time now.

Do you expect them to support this forever because you paid a couple hundred bucks for it a decade ago?

smh.

well if they screw it up in the first place, they should fix it. It was working fine until windows 10 upcock broke it. And why is office 365 better (for the user) anyway. Libreoffice is looking better by the minute but I guess win10 will find a way of sabotaging it too...
Was this answer helpful?

0 comments No comments