Active Setup

From WikiDesktop

Active Setup

Active setup is useful for applications that have HKCU keys that need to be installed on a heal where there is no entry point in the application. The way this works is an application in active setup with run a heal on login prior to the user having access to the desktop.

At login two registry keys are compaired between HKLM and HKCU, the key paths are as follows;

HKLM\Software\Microsoft\Active Setup\Installed Components\%PRODGUID% and HKCU\Software\Microsoft\Active Setup\Installed Components\%PRODGUID%

If the HKCU key does not exist or if the version number in HKCU is less then the version number in HKLM, then the MSI or setup command line that is entered in the value StubPath is executed. %PRODGUID% can be any common value, but the GUID from the product is normally used.

Registry File

The following registry file can be modified and used in a msi to put down the correct entries;

The text after the "@" is the (default) and is what is shown when active setup runs at login. Change "ProductCode" in the first line to the Product GUID or something unique. The last line is "Version" and it must have commas in lieu of periods.

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\ProductCode]
@="[ProductName]"
"ComponentID"="[ProductName]"
"DontAsk"=dword:00000002
"IsInstalled"=dword:00000001
"Locale"="EN"
"StubPath"="[SystemFolder]msiexec.exe" /fu [ProductCode] /q
"Version"="x,x,x"

Notes

• The "/fu" switch will ONLY Fix USER registry keys and is typically all that is needed. However, the "/fpu" switch may be required to also ensure healing of profile files & folders.

• You can also run any program you want with Active Setup. This could be an executable that you have created in lieu of running the repair on the MSI.

• If you need to run Active Setup a second time after the initial install, it can be forced by incrementing the version number.