amlydiate
asked on
Word Excel Outlook 2010 quit after 2 minutes
I have an interesting problem with an installation of Office 2010. Word/Excel and Office all run for 2 minutes before quitting. Checking within each they show they are Activated with Microsoft and even when run in safe-mode the same happens. I've tried winword.exe /a and also get the same results. Could this be a licensing issue as I see Software protection service completes a licensing check when the programs are launched?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sam Simon Nasser
whats the error you get?
ASKER
I am trying a repair now and then a reinstall as plan B.
There are no error messages on screen or entered into the eventlog. They all just exit after exactly 2 minutes.
There are no error messages on screen or entered into the eventlog. They all just exit after exactly 2 minutes.
ASKER
I have performed a repair without any luck. I then uninstalled, rebooted and reinstalled, activated and still the same, programs quit after 2 minutes.
Look in the Event Manger and see all Office related messages (application in windows logs; and Microsoft Office alerts in Applications and services logs). Anything that stands out?
[You my have to perform a manual uninstallation of Office, same link as Fix It)]
[You my have to perform a manual uninstallation of Office, same link as Fix It)]
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your comment, have carried out a complete uninstall of all Office Products, you're right there were multiple copies including Home and Business 2010 and an entry called Office 2010. All removed, PC rebooted and the single Office 2010 Home and Business installed and error still occurs unfortunately
Can you restore your computer to an earlier point before the problem started occurring?
ASKER
Thanks both for your help, have split the points between you but found out after the user came clean that he had installed some third party modified print drivers which were causing the problem in the end.