Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Fix to FIrefox 41.0.1 caused Office 2007 products not to start with 0x80000003 error

  • 4 tontu
  • 1 am na jafe-jafe bii
  • 1 view
  • i mujjee tontu mooy jscher2000

more options

Once the Firefox update 41.0.1 was installed my Outlook, WinWord and Powerpoint 2007 will not start and give me an error message of 0x80000003. This happened immediately after the install of the firefox update. When I start the computer in safe mode I am able to start Outlook, Winword and Powerpoint. I am running Windows 7 with latest updates. How do I fix this?

I also tried to reinstall office 2007 after no success using the repair function and running Microsoft office configuration analyzer and Microsoft Officer Diagnostic Tools.

Corwyhn moo ko soppali ci

All Replies (4)

more options

duplicate

Corwyhn moo ko soppali ci

more options

Do you mean that once Firefox starts those other programs won't start, or even if you do not start Firefox before those programs, they won't start?

Could you check for any "extras" that might have installed when you updated Firefox? Open the Windows Control Panel, Uninstall a Program. After the list loads, click the "Installed on" column heading to sort by date. Any unknown items??

I wonder whether the Hotspot Shield extension could be a factor. I'm not sure how it works, for example, whether it installs any Windows services or startup programs. Have you been using that all along without any difficulty?

more options

Whether firefox is running or not the Office programs still give me the error message. I can only start the office programs in safe mode.

Nothing new was installed when firefox update was installed as per Uninstall a Program. And yes I have been using hotspot shield for a long time with no problems.

more options

Usually if programs work when you start them in Windows Safe Mode and not normally, the problem is another program in the startup sequence. You can use the Autoruns program to review what is set to auto-run at startup to see whether anything looks odd or suspicious. Otherwise, I'd have to suggest Microsoft's forums.

Autoruns: https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx