Office 2007 Installs on Every Startup

[b1acksh33p]

I recently purchased Office 2007 Student edition and installed it. It works well except for the fact that every time I start it it runs through and install and configuration process. I have uninstalled it, deleted all the registry entries and reinstalled it several times and it still keeps doing it. This is effectively keeping me from using Office and its driving me nuts. I really don't want to waste $150 on software that won't work. I attached some screenshots of what happens to this post. And yes, you forum elites, I did google this thoroughly before I posted

Edit: I installed the zoho plugin shortly after I installed the software...the problem started after that. Could there be a connection? I don't see how a zoho plugin could screw it up but you never know.

Edited August 2, 2007 by b1acksh33p

[neo]

Open Registry Editor and navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

and

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

check for the entry of Office 2007 and delete.

You can run msconfig and goto Startup tab and disable entry of Office 2007.

Edited August 2, 2007 by neo

[puntoMX]

Edit: I installed the zoho plugin shortly after I installed the software...the problem started after that. Could there be a connection? I don't see how a zoho plugin could screw it up but you never know.

It seems that there is a connection between the two on tour computer. Simply said, Office sees a damaged install and recovers the installation process by reinstalling a part of that office. I don’t think its file related, but something went wrong in the registry...

[b1acksh33p]

Open Registry Editor and navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

and

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

check for the entry of Office 2007 and delete.

You can run msconfig and goto Startup tab and disable entry of Office 2007.

Thanks, I tried that, but there were no entries for Office at all. Strange...

[b1acksh33p]

Edit: I installed the zoho plugin shortly after I installed the software...the problem started after that. Could there be a connection? I don't see how a zoho plugin could screw it up but you never know.

It seems that there is a connection between the two on tour computer. Simply said, Office sees a damaged install and recovers the installation process by reinstalling a part of that office. I don’t think its file related, but something went wrong in the registry...

I think you are right because I get an error when I start excel that doesn't appear in any of the other programs. It says "stdole32.tlb" and thats it. See the attached screenshot...The question is, what do I do about it? If uninstalling doesn't work, I'm not sure what else to do.

[puntoMX]

Okay, so that part of Windows is damaged.

Try to do this:

- Click Start > Run.

- Type CMD. Click OK.

- Change to the root folder of drive C, type cd\ or c:, and press ENTER.

- Insert the Windows Installation CD.

- Type expand cd_drive_letter:\i386\stdole32.tl_ drive:\Windows\system32\stdole32.tlb, and press ENTER, where cd_drive_letter is your CD drive, and drive is the letter of the drive where Windows is installed. For example:

expand D:\i386\stdole32.tl_ C:\Windows\System32\stdole32.tlb

- Type exit.

- Restart your computer.

Does it work now?

[b1acksh33p]

Okay, so that part of Windows is damaged.

Try to do this:

- Click Start > Run.

- Type CMD. Click OK.

- Change to the root folder of drive C, type cd\ or c:, and press ENTER.

- Insert the Windows Installation CD.

- Type expand cd_drive_letter:\i386\stdole32.tl_ drive:\Windows\system32\stdole32.tlb, and press ENTER, where cd_drive_letter is your CD drive, and drive is the letter of the drive where Windows is installed. For example:

expand D:\i386\stdole32.tl_ C:\Windows\System32\stdole32.tlb

- Type exit.

- Restart your computer.

Does it work now?

Grrr...I don't have a windows installation CD. I want to try this! Any other options?

[puntoMX]

You just need the file stdole32.tlb to be copied in *drive*:\Windows\system32\ that’s all, so the fastest way would be if you can ask some one near to you to pass it too you.

Is it Windows XP by the way?

[b1acksh33p]

You just need the file stdole32.tlb to be copied in *drive*:\Windows\system32\ that’s all, so the fastest way would be if you can ask some one near to you to pass it too you.

Is it Windows XP by the way?

No, its windows vista home premium. I will see if I can find the file.

[billw]

You just need the file stdole32.tlb to be copied in *drive*:\Windows\system32\ that’s all, so the fastest way would be if you can ask some one near to you to pass it too you.

Is it Windows XP by the way?

Hello,

 

Hopefully, this thread isn't dead. As it seems to be a common issue with Office 2007, I too have the same issue but under slightly different circumstances. I'm moving Office 2007 Pro from my wife's XP machine to my Win 7-x64 system. I previously had Office 2003 Pro on my PC, but removed it to go to 2007. I have the same exact issues with Excel always going into a setup mode, and calling out stdole32.tlb as missing, however, it is in fact, properly installed on my system. See below.

 

Note that Word, Power Point, and Publisher (I'm not using Outlook) startup and run without issue. Only Excel give me problems.

 

I've read ad nausium of very many different user's "solutions", and none seem to resolve the issue. I reinstalled 2003 and no change, uninstalled all and nada. I also used "Office 2003 MicrosoftFixit50416.msi" and "Office 2007 MicrosoftFixit50154.msi", sweeped through the registry and removed all instances of Office 2003/2007 with no change. I even activated and logged in as Administrator, and still the same Excel stdole32.tlb/Startup issues.

 

Any help would be greatly appreciated.

 

Thanks,

Bill Walch

[jaclaz]

This thread isn't dead (anymore ) you just revived it by digging through it's grave and bringing it back to life (which is the good thing about not closing thread, sometimes they return ).

 

The screenshot you posted unfortunately does not provide any actually useful information, and certainly not about it being installed (or installed properly) it only says that the file exists (good).

 

But this error has been reported in connection mainly with two distinct issues (causing the same behaviour/error message) one is a permission issue on a Registry hive and the other is related to missing entires in the Registry (not actually connected directly on indirectly with stdole32.tlb).

 

Check if the first case applies to your system, see here:

http://andyjwilliams.co.uk/technology/vista-office-2007-installation-problems-stdole32tlb/

or if the second case applies, see here:

http://davidoverton.com/blogs/doverton/archive/2007/07/21/how-to-get-rid-of-the-installer-configuration-dialog-when-running-office-2007-and-office-2003-on-the-same-system-for-vista-and-other-versions-of-windows.aspx

 

If neither cases (and relative solutions) apply to your system or if you have troubles in applying the fixes, please let us know, it is well possible that it is *something else* or, if you prefer, the stdole32.tlb issue is *somehow* like a "generic error" that may be triggered by several causes, but let's first see if any of the two known and common ones apply.

Just as an example, there are other (fewer) reports about the issue having been solved by completely uninstalling all versions of Office through some of the "third party advanced uninstallers".

 

jaclaz

[billw]

This thread isn't dead (anymore ) you just revived it by digging through it's grave and bringing it back to life (which is the good thing about not closing thread, sometimes they return ).

 

The screenshot you posted unfortunately does not provide any actually useful information, and certainly not about it being installed (or installed properly) it only says that the file exists (good).

 

But this error has been reported in connection mainly with two distinct issues (causing the same behaviour/error message) one is a permission issue on a Registry hive and the other is related to missing entires in the Registry (not actually connected directly on indirectly with stdole32.tlb).

 

Check if the first case applies to your system, see here:

http://andyjwilliams.co.uk/technology/vista-office-2007-installation-problems-stdole32tlb/

or if the second case applies, see here:

http://davidoverton.com/blogs/doverton/archive/2007/07/21/how-to-get-rid-of-the-installer-configuration-dialog-when-running-office-2007-and-office-2003-on-the-same-system-for-vista-and-other-versions-of-windows.aspx

 

If neither cases (and relative solutions) apply to your system or if you have troubles in applying the fixes, please let us know, it is well possible that it is *something else* or, if you prefer, the stdole32.tlb issue is *somehow* like a "generic error" that may be triggered by several causes, but let's first see if any of the two known and common ones apply.

Just as an example, there are other (fewer) reports about the issue having been solved by completely uninstalling all versions of Office through some of the "third party advanced uninstallers".

 

jaclaz

 

Hi jaclaz,

 

Thanks for the reply. Yes, I've tried both the "solutions" you mentioned (and many others) and it made no difference. You are correct in that stdole32.tlb is on the system, but it's anyone's guess what app installed it (or when). The only tell-tail is the file date of 6/10/2009, if that helps at all, but probably not. I'm assuming that the "Trusted Installer" is from MS, but that's just a SWAG.

 

As for uninstalling, i've used "WindowsInstall Clean Up", "Revo Uninstaller", among others, as well as MS's MicrosoftFixit solutions. I also followed the Manual Uninstall instructions from MS (http://support.microsoft.com/kb/928218). I've Un/Reinstalled Office about 6 times, all with the same/similar results. On the last itteration, Word came up with the Startup screen a few times, but stopped. As I mentioned, the other Office apps run fine, just Excel give me trouble.

 

Two additional "solutions" I read about is to install Office 2007 SP1 (I currently have SP3 installed). The other one is to used a Vista version of stdole32.tlb in place of what's on my system. My laptop is running Vista, so that may be worth a try too. Running out of options.

 

Thanks,

Bill

 

P.S. Is there a spell checker on this system?

Edited December 2, 2014 by billw

[kaljukass]

It will not save you. Looks like you have the whole system corrupt. Rescues only clean reinstallation. Otherwise you wasting only time. And everything ends on the same way.

[jaclaz]

It will not save you. Looks like you have the whole system corrupt. Rescues only clean reinstallation. Otherwise you wasting only time. And everything ends on the same way.

It is refreshing to have this kind of optimism injections on a thread.

 

@billw

You may want to try this:

http://answers.microsoft.com/en-us/office/forum/office_2007-office_install/stdole32tlb-message-and-reconfiguring-every-time/08afbcb2-e3a2-4028-8ec1-0b45f24b76b2

The tool is not available anymore, but it can be retrieved thanks to the Wayback Machine

https://web.archive.org/web/20100301160429/http://support.microsoft.com/kb/290301

https://web.archive.org/web/20100531005942/http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d5e1bd/msicuu2.exe

 

The tool was retired for a reason :

https://web.archive.org/web/20100831061718/http://support.microsoft.com/kb/290301

 

But it is still IMHO worth a try.

 

jaclaz

[submix8c]

FWIW, just searching on "stdole32.tlb" I get all kinds of hits, one being:

http://answers.microsoft.com/en-us/office/forum/office_2007-office_install/stdole32tlb-file-missing/9f1bfc94-7263-4422-a17b-a67233d8f111

And another (same solution):

http://answers.microsoft.com/en-us/office/forum/office_2007-excel/stdole32tlb-in-excel/6304959e-796a-45a4-9abc-82805b0f716d

Here's an oddball. By chance, is this an OEM Win7 and had a "newer" Office installed?

http://www.bleepingcomputer.com/forums/t/528044/stdole32tlb-in-excel-2007/

 

HTH (no, I don't have Win7x64+Office2K7 installed ATM, so not sure if the above *will* help... sorry.)