Installing Office hotfixes on Vista

[David Thielen]

We have a customer using Office 2000 on Vista (dare to be different). They
are installing LockbackRegKey.msi and ExtensibilityMSM.msi

The problem is our installer checks for a registry entry at
HKEY_CLASSES_ROOT\Interface\{000C0601-0000-0000-C000-000000000046} to see if
the hotfixes are installed. And while that folder exists, there is no default
entry and no sub-folders, so our installer thinks the hot fixes are not
installed.

Any idea what's going on here? Do these hotfixes not install right under
Vista? Or do we need to use a different registry check to see if they are
installed?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[Jialiang Ge [MSFT]]

Hello Dave,

From Orca (http://msdn2.microsoft.com/en-us/library/aa370557(VS.85).aspx),
I notice that the Registry setting of lockbackRegKey.msi is:
Interface\{000C0601-0000-0000-C000-000000000046}
And its Product code (from the Orca Property table) is:
{64F3B15C-24C7-4B2B-9B72-65CCBBD7F06B}

The Windows Setup support engineers in my team told me that it is suggested
to use the Product Code and MsiGetProductInfoEx API
(http://msdn2.microsoft.com/en-us/library/aa370131(VS.85).aspx) to check if
the MSI's been installed. Or use the Visual Studio Setup project:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2166828&SiteID=1

I've reproduced the issue that
Interface\{000C0601-0000-0000-C000-000000000046} does not have sub keys
after lockbackRegKey.msi installation in my Windows 2000 (haven't tested in
Vista yet) + Office 2000 test system. It seems to be an Office 2000
specific problem, instead of a Windows (Vista) problem. I believe the
lockbackRegKey msi is still necessary to Office 2000, I am asking the
product team for more information and will get back to you as soon as
possible.

Regards,
Jialiang Ge ([email protected], remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

 

[Jialiang Ge [MSFT]]

Hello Dave,

I find a newly updated KB article 948461 that can address this problem:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;948461

We can set the registry key directly without executing lockback msi for the
Office 2000 environment. See:

<quote>
Clients that are running Office 2000 or Office XP

Microsoft does not provide a managed runtime for Microsoft Office 2000 or
for Microsoft Office XP (2002). Therefore, Microsoft does not offer an
update to these clients. Without a host runtime to enforce component
isolation, components that different vendors produce can interfere with
other components. These components can cause problems for the client. These
components can also cause application instability or runtime errors.
Therefore, Microsoft discourages using managed code in Office 2000 or in
Office XP. Be careful when you try to introduce managed code into these
Office versions. These Office versions were designed and tested before the
..NET Framework was created.

If you have a solution that must use managed code in Word 2000, in Word
2002, in Excel 2000, or in Excel 2002, you can manually configure the
client system to bypass the lockback policy and to enable the .NET
Framework 2.0 CLR to load those versions. To do this, follow these steps:

1. Click Start, click Run, type regedit , and then press ENTER.
2. Locate and then right-click the following registry key:
HKEY_CLASSES_ROOT\Interface
3. Point to New, and then click Key.
4. Enter {000C0601-0000-0000-C000-000000000046} as the name for the new
registry key.
5. In the right side, double-click the default registry entry, enter
Word/Excel .NET Framework 2.0 Lockback Bypass Key in the Value data box,
and then click OK.
6. Close Registry Editor.
Note Setting this bypass key can cause compatibility problems for solutions
that are designed by using VSTO 2003. As long as this client remains on
Office 2000 or on Office XP, this should not be a problem. However, if the
client upgrades to Office 2003, the client must install the full update
that was mentioned earlier to be supported by Microsoft. It becomes your
responsibility to make sure that this configuration is correct if you
manually set this bypass key.
</quote>

Regards,
Jialiang Ge ([email protected], remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

 

[David Thielen]

thank you

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm