stdole32.tlb in Excel Windows 10

Thanks for your reply.

It is a real pain and we shouldn't have to search the internet for solutions.

It is still a Microsoft product and just because support has ended the basic apps like excel and word should still be able to function without any problems on the operating system.

Yes it's all about the money. Works fine on an older version of 10 but not the new one. It's still windows 10 after all.

Going back to the previous version only prompts a new update and you can only fend that off for so long before security issues become an issue so to speak.

Unisntall and Reinstall Office 2007 and it will work fine.

I received the Win 10 Fall Creator's Update on my desktop a few weeks ago and encountered this problem with Office 2007 (plus the corresponding one where Word keeps trying to reinstall every time I open a .docx).  I've been putting off troubleshooting it.  But now I just installed a brand new Win 10 laptop and everything was working fine with Office 2007.  Then I got the Fall Creator's Update and now the laptop is doing the same thing.  I will try the "uninstalling updates" method, (but Win 10 will likely just reinstall the updates and it'll break again) or I'll try a clean remove and reinstall with Revo Uninstaller (I've been using that for years; it's a good tool for an IT person).  I hope one of those things works.  Option 2 is likely better, but what a giant pain in the rear for a suite that I just spent so much time configuring.

Regardless, it goes beyond Microsoft not supporting many of their older products now.  I firmly believe they're intentionally sabotaging the older programs in order to force people to upgrade.  The same thing mysteriously happened with IE 11 when MS really started to push Edge like a year ago - IE 11 will now very frequently crash or not play videos, etc., even on sites that it used to work fine with before and whose content hasn't changed.

Here's a follow-up to my above post.  Because it was easy to try, at first I edited the permissions on the "HKCR\Excel.Chart.8" registry key as suggested on some other sites, but that didn't help.  Because the problem only started after receiving the Fall Creator's update (just one day after I first set up the new laptop), I went ahead and uninstalled all of the "quality" Office updates I'd just received. That method is mentioned earlier in this thread, except I only uninstalled Office updates - I left regular Windows updates alone.  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.  After a reboot, my issue with Excel giving the stdole32.tlb error and trying to reinstall/reinitialize was gone, and I was able to open Word also without it trying to reinstall.  Then I immediately checked for updates and let Windows 10 re-install all of the updates it once more found for Office.  Several reboots later, and Office 2007 is still working fine.  Perhaps the problem update just hasn't reinstalled yet and I'll see the problem again?  We'll see.  But the hypothesis by some that Microsoft had a bad update in December and has since fixed it is probably false, because I only installed the laptop and Office 2007 on 1/17/2018, and received updates for it the same day, and then I got the Fall Creator's update on 1/18/2018.  It could be that the Fall Creator's Update itself just breaks one of those other Office updates (intentionally or not), and reinstalling the update fixes it. I wish I'd been able to isolate it to a specific KB number, but at least for now it's working.

Another reason I believe Microsoft may be doing it on purpose is that it hasn't happened to any machine on my domain at work.  Perhaps they're shying away from pissing off business customers in this instance.  I have about 20-25 Windows 10 systems all running Office 2007 Standard. At least half of them now have the Fall Creator's update, and the issue hasn't happened once.  But on my new personal stand-alone laptop running the same Office 2007 Standard with the identical product key, the problem occurred. (I work remotely from the laptop, so I'm allowed to use the company key for it.)  The problem also happened when I got the Win 10 Fall Creator's Update on my personal stand-alone desktop PC at home, where I'm running a personal copy of Office 2007 Professional Plus.  I'll have to see if the same method fixes that.  So it could be something else, but the main difference between my personal computers and the ones at my office is that the office ones are on a domain. *shrug*

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.