stdole32.tlb in Excel Windows 10

Thanks for this.

With regards to **"**I uninstalled every Office update on my system that wasn't an Office "Security" update, and I also didn't uninstall Office 2007 SP3 and the Office 2007 Compatibility Pack either".

I have 56 update under Office Enterprise. So did I pick out  all non security updates ( there are quite a few) and uninstall? It's just that Office 2007 came pre-installed on laptop and when I tried to use the product code to download a copy from Microsoft just in case I messed it up I got an error saying as software was pre-installed by HP I must approach them for recovery. My laptop warranty expired so I didn't want to end up stranded.

Sorry to be a pain but your help is appreciated.

Just because a couple of people earlier in this thread had success with it, that's what I did - yes.  I went to Control Panel > Programs and Features > View Installed Updates. Then one at a time I uninstalled every update under the Microsoft Office Standard 2007 section that started with the word "Update." I didn't uninstall any updates starting with the word "Security."  There were about 12-15 on my new laptop. But the exact number of those types of updates will likely vary for you, based on the exact version of Office 2007 you have, which optional components you (or HP) chose to install or not install, etc. Looking at my work desktop right now, I count 18 such updates in the list.  Then, as I said, I rebooted and checked for updates, and then I let Windows 10 reinstall any Office 2007 updates it found.  So far it's working for me, but it hasn't even been 24 hours yet. So I have no idea if the fix will stick or if so for how long it'll last.

Just completely uninstalling and reinstalling the entire Office 2007 suite (using the free Revo Uninstaller application to be thorough) is a viable option that's worked for some people. But I only want to do that as a last resort. I have a decent amount of custom stuff I set up with Office 2007, like custom Outlook templates and so forth that I use for work.  So uninstalling these updates took less time for me, and it's worth a shot for you in my opinion. At worst it won't work and Windows should reinstall the updates. If it doesn't work then a complete clean reinstall might work.  But if your laptop is out of warranty/support from HP (which it would be if it came with Office 2007 pre-installed), and you don't have your product key, then reinstalling from scratch could be very bad. If you don't have any documentation from when you bought the laptop that lists the key, then you could try one of the free keyfinder apps that are out there.  Magical Jellybean Keyfinder is one I've used before, but there are several others. It might not be there if Office was pre-installed by HP, but normally the Office 2007 product key will be listed in your registry - it's just encrypted.  But one of the free keyfinder apps ought to be able to read it so you can write it down and save it.  But if you end up uninstalling and can't reinstall, don't hold me responsible - it's ultimately Microsoft's fault. :)

Thanks for your help again.

I managed to use the keyfinder to identify my 2007 product key but when I inserted it in the download tool it came up with an error code and prompted me to contact Microsoft customer services. I have no idea why this happened as I wasn't prepared to sit in queue to explain my predicament.

Decided to have a go at uninstalling as outlined in your above post and managed to uninstall 7 by working down the list. After that it wouldn't allow me to do any more as apparently I had to wait while it was busy dealing with a previous uninstall. Rebooted a few times but it wasn't having any of it. 

So I decided to go with what I had and installed the new updates which included quite a few new security updates as well.

Rebooted afterwards and hey presto all is good with Excel, word and surprise surprise LibreOffice.

Thanks once more for your guidance, much appreciated.

I was able to fix the stdole32.tlb box popping up issue when opening excel 2007. I went to the Office folder and then right clicked on the Excel 2007.exe file. Under compatibility I configured the file to run under XP sp3.

Now when executing, it brings up the UAC box and I have to select yes but it does not have the stdole32.tlb error. I went in and checked UAC to never notify. Now after opening Excel it goes right in with no issues. It seemed that XP sp3 was the only one that would work. I tried using Win 7 and 8 I and I got different errors when trying to run under those OS's. Hope this helps somebody.

Had the same problem (with Excel only, no other Office programs) since general MS updates I could no longer avoid in the last few days. After reading most of this forum, I started with what seemed the easiest experiment - I simply uninstalled anything (from the recent udate) that was labelled excel 2007, but NOT security excel 2007 - just like the previous post, BUT I only uninstalled the latest updates - because the problem never existed with any previous update. I think it was only three updates that I uninstalled. It appears to now be opening and working correctly.

Its only been an hour - but it works correctly! This would appear to be the simplest fix requiring the least amount of effort - or time wasted by MS!