Hi cochese (the cochese from CodeProject perhaps "In Cod we trust" ?)



Off the cuff, I'd say that something has 'escaped' the layer, and is landing on the base.

As the file on the base is different than what the 'currently running' word version expects or requires, the self reapair is initiated.



You could look in the event log, and see which component(s) are causing the self-repair, and examine the msi packages to see which files / registry entries are effected.



With no more info, that's the best I can offer,

Cheers



Phil

That's actually a default behavior of Office, I'm surprised you're only seeing with Word. What's going on is office is running a repair and is switching default app types between programs.



You still should check what Phil suggested but more often then not with Office isn't just this file association repair (there's a KB article on MS.com explaining this).

hmmm, well that's annoying

Hello,

On my laptop I am using both MS Office 2003 and 2007, captured in 2 different layers. They work fine side by side, I can activate / open them in the same time, I can even have both versions of Word open in the same time, and edit different documents each in the same time. No installer gets triggered, all works fine.

The behaviour you are experiencing with office is a default problem.
Both Office word versions use a different value to write the user credentials.
This value makes the error occure.
ou can resolve this by opening the package and go to the windir\installer and delete the msi's there.
that will stop the auto creation and your word will run fine.