This information relates to WinZip 12.1 and later along with the WinZip Command Line Support Add-on 3.0 and later.
Usually when WinZip is installed it writes a WinZip.addon file to a WinZip subfolder in the Windows CommonAppData folder. A typical path to this would be C:\ProgramData\WinZip in Windows 8, Windows 7, and Windows Vista. In Windows XP the typical path would be C:\Documents and Settings\All Users\Application Data\WinZip. When you register WinZip, the UZQF string value is updated in
HKEY_LOCAL_MACHINE\Software\Nico Mak Computing\WinZip\WinIni
with a new value and that value is also updated in the WinZip.addon file.
When a user runs WinZip, the same string will be updated in HKLM and will also be updated in
HKEY_CURRENT_USER\Software\Nico Mak Computing\WinZip\WinIni
if the install was not done under this user's profile. Otherwise the value is updated when WinZip is registered.
When WinZip Command Line Support Add-On runs, it looks for the value in the WinZip.addon file. If a value is found, but it is incorrect (perhaps due to an upgrade situation) WinZip Command Line Support Add-On will not run as registered. If it cannot read the WinZip.addon file for some reason, it looks in HKCU, and it may look for the value in HKLM as the last resort. The value found must be a registered value, otherwise the add-on will run as the evaluation version.
If your WinZip Command Line Support Add-On users will be running the add-on without ever having opened WinZip and if their profiles do not have permissions to read the entries in HKEY_LOCAL_MACHINE, you may want to create your own WinZip.addon file. To do so (after you have registered WinZip), look up the UZQF entry in HKEY_LOCAL_MACHINE as listed above, create a text file, rename it to WinZip.addon, and edit it to have the following information in it:
[Addon]
UZQF=****
AOFF=0
| Be sure to enter your actual 4 characters to replace the asterisks. You may also need to create the WinZip subfolder in your Windows CommonAppData folder and will need to place your WinZip.addon file in there. |
This should cause the add-on to always run as registered. Contact Technical Support if issues persist.
