Update:
I attached RegMon to Word during startup, and it used the following
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\policy\AppPatch\v2.0.50727.00000\winword.exe
Which contains the following values:
------------
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\policy\AppPatch\v2.0.50727.00000\winword.exe]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\policy\AppPatch\v2.0.50727.00000\winword.exe\{2CCAA9FE-6884-4AF2-99DD-5217B94115DF}]
"Minimum File Version Number"="11.0.0.0"
"Maximum File Version Number"="11.0.9999.9999"
"Target Version"="v1.1.4322"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\policy\AppPatch\v2.0.50727.00000\winword.exe\{2CCAA9FE-6884-4AF2-99DD-5217B94115DF}\Registry
Keys]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\policy\AppPatch\v2.0.50727.00000\winword.exe\{2CCAA9FE-6884-4AF2-99DD-5217B94115DF}\Registry
Keys\{2CCAA9FE-6884-4AF2-99DD-5217B94115DF}]
"Key Presence"=dword:00000000
"Key
Name"="HKEY_CLASSES_ROOT\\Interface\\{000C0601-0000-0000-C000-000000000046}"
------------
If I rename the winword.exe registry key to winword2.exe for example,
word loads v2.0 of the CLR as expected, and the addin loads
successfully. For some reason, powerpoint.exe has not been added to the
AppPatch registry key, which explains why PowerPoint works.
My immediate impulse is to delete the registry keys for Word an
PowerPoint, but I've found no documentation about the registry key, so I
not sure it's the right solution.
> I appears that it works correctly for users that are not local
> administrators on the current machine. For these users, the .NET Runtime
[quoted text clipped - 38 lines]
>> This posting is provided "as is" with no warranties and confers no
>> rights.
"Jeffrey Tan[MSFT]" - 09 Nov 2005 09:35 GMT
Hi Jim,
Thanks for your feedback.
I do not think it is this registry key that caused your strange problem.
Because on my test machine, it has the same registry structure as you
posted. However, I do not know why after renaming this registry key, your
word will correctly load .Net2.0 CLR now. Anyway, because this registry
resides in my work well machine, I do not suggest you to delete this
registry key, because this may cause some serious issue.
Thanks
Best regards,
Jeffrey Tan
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Jim Meyer - 09 Nov 2005 10:34 GMT
Jeffrey Tan[MSFT] wrote:
> Hi Jim,
>
[quoted text clipped - 14 lines]
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
I'm almost 100% sure it does cause the problem - let me explain:
RegMon shows that when word runs for a non-administrator, Word gets an
Access Denied result when it attempts to open the AppPach registry key:
WINWORD.EXE:2324 OpenKey
HKLM\Software\Microsoft\.NETFramework\Policy\AppPatch\v2.0.50727.00000
ACCESS DENIED Access: 0xF003F TESTLAB\nonadminuser
For users with local administrator rights word successfully reads the
key and loads the specified 1.1 target version (which is wrong in our
case). So the registry key does determine the application compatibility
setting for the CLR version.
I've tried this across multiple test machine - admin users get v1.1 of
the CLR in Word and Excel, while non-admin users on the same machine get
v2.0 since the AppPatch key is not successfully read by word and excel.
For both types of users, PowerPoint loads v2.0, since there is no
powerpoint.exe listed under the AppPatch registry key.
I believe that the purpose of the AppPatch registry key is to prevent
v2.0 braking changes to affect word and excel addins running v1.1 of the
framework.
"Jeffrey Tan[MSFT]" - 10 Nov 2005 07:49 GMT
Hi Jim,
Thanks for your feedback.
This is really a strange issue. I have consulted our product team for this
issue, and based on the feedback, this issue can be fixed by installing the
update below:
http://www.microsoft.com/downloads/details.aspx?FamilyId=1B0BFB35-C252-43CC-
8A2A-6A64D6AC4670&displaylang=en
So I suggest you install this update and check if it resolves your problem.
Thanks
Best regards,
Jeffrey Tan
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Jim Meyer - 10 Nov 2005 10:27 GMT
I've just installed the update, and it fixes the issue for Word and
Excel. Thank you for the support.
Jeffrey Tan[MSFT] wrote:
> Hi Jim,
>
[quoted text clipped - 14 lines]
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
"Jeffrey Tan[MSFT]" - 10 Nov 2005 11:44 GMT
Cool, it seems that your issue is exactly the same one as what this update
fixed. If you need further help, please feel free to post. Thanks
Best regards,
Jeffrey Tan
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.