| Why am I receiving error 1260 when trying to install service packs? |
Following the release of Microsoft Security Update KB2918614 there have been numerous external reports of software installations and upgrades failing for multiple products that use Windows installer packages (.msi).
MSI Minor Upgrades are affected and will trigger the following error in the MSI log and the Application event log:
Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy. For more information, open Event Viewer or contact your system administrator
Cause:
The issues are triggered by the Secure Repair function introduced in the Windows Installer Service as part of this Microsoft Security Update.
Solution:
CAUTION: This solution requires modifying your system's registry and should be followed by a system IT professional!
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
On the Edit menu, point to New, and then click DWORD Value.
Type SecureRepairPolicy for the name of the DWORD, and then press Enter.
Right-click SecureRepairPolicy, and then click Modify.
In the Value data box, type 2, and then click OK.
Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
On the Edit menu, point to New, and then click Key.
Type SecureRepairWhitelist for the name of the key, and then press Enter.
Double-click the SecureRepairWhitelist key to open it.
On the Edit menu, point to New, and then click String Value.
Create a separate String Value for each of the following Account Ability product codes:
{9C2F4A48-5622-4DEF-8415-31BAA78CC524}
{A92A07C8-2D8A-474A-8D11-0E43B17E8D43}
{584AF4AC-C782-4499-800A-94EF33410308}
|
 |
| Can I install a service pack from a concurrent user workstation? |
Although concurrent users can check for service packs and download service packs, service packs must be installed from the same computer (or server) that performed the original installation (installation computer).
TIP: The installation computer is easily identified by the picture of a computer displayed directly to the left of the facebook icon on Account Ability's 'Status Bar'. |
|
| Is there an alternative way to install a service pack other than from Account Ability's Help menu? |
|
You can download the service pack directly from Account Ability's Download page. You will, however, need the password originally provided by the 'About Account Ability (Check for Updates)' selection located on the 'Help' menu. |
|
| Which domains should I add to our security gateway in order to allow service packs to download? |
idmsinc.com
accountabilitysoftware.com
accountabilitysoftware.net |
|
| Why do I get a security violation when trying to install a service pack? |
Account Ability's service pack installation script downloads the setup.exe to a TEMP folder located within Account Ability's installation folder. If you installed Account Ability to the 'Program Files' or 'Program Files (x86)' folder, Windows 7 (and later) automatically creates this TEMP folder within the user's virtual storage area and restricts the download, thus resulting in the security violation. This is one of the reasons why you should avoid installing Account Ability to 'Program Files'.
Solution: Download the service pack directly from Account Ability's Download page. You will need the password originally provided by the service pack installation script. |
|
