Article ID: 286100 - View products that this article applies to.
This article was previously published under Q286100
This article has been archived. It is offered "as is" and will no longer be updated.
Registry keys that are written directly under the HKEY_CURRENT_USER hive by Windows Installer per-computer installations on Windows NT Terminal Server and Windows 2000 with Terminal Services do not get propagated to other users. This causes the Windows Installer to attempt to repair the application for all users. The user that installed the application is not affected.
The keys written at the root of the HKEY_CURRENT_USER hive do not get propagated. This is by design. The Windows Installer on Terminal Server computers runs an installation in the context of system so that all changes and updates are redirected into the HKEY_USER\.Default hive. Only the HKEY_USER\.Default\Software hive is propagated. So, each time that a user starts the application, the Windows Installer resiliency gets triggered because it is looking in the HKey_Current_User hive. Rebooting and reinstalling will not fix the problem.
If your installation needs to write keys to the HKEY_CURRENT_USER hive on Terminal Server, then they should be written under HKEY_CURRENT_USER\Software instead of HKEY_CURRENT_USER\.
For additional information on Terminal Services and application integration, click the article number below to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/186498/EN-US/ )Terminal Server Application Integration Information
Article ID: 286100 - Last Review: October 23, 2013 - Revision: 2.0