Lỗi file appleapplicationsupport.msi was rejected by digital signature policy năm 2024
When installing a large Microsoft Windows Installer (.msi) package or a large Microsoft Windows Installer patch (.msp) package on a computer that is running Microsoft Windows Server 2003 or XP, the following error message displays: Show Code: Error 1718. File FileName was rejected by digital signature policy. Similar errors may also appear stating: "The installation of OR "1706 The installation source for this product is not available. Verify that the source exists and that you can access it." This happens during the installation of an ArcGIS .msp file such as service packs and the 9.3.1 update. CauseThis problem occurs if the Windows Installer process has insufficient contiguous virtual memory to verify that the .msi package or the .msp package is correctly signed. Solution or WorkaroundA supported fix is available for Windows Server 2003. See the Related Information below for the Microsoft Knowledge Base document as well as the Windows Server 2003 fix. When you try to install a large Microsoft Windows Installer (.msi) package or a large Microsoft Windows Installer patch (.msp) package on a computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP, you receive the following error message: Error 1718. File FileName was rejected by digital signature policy. Additionally, the following event may be logged in the Application log: Type: Error Source: MsiInstaller Category: None Event ID: 1008 Date: Date Time: Time User: Na Computer: ComputerName Description: The installation of FileName is not permitted due to an error in software restriction policy processing. The object cannot be trusted. CauseThis problem occurs if the Windows Installer process has insufficient contiguous virtual memory to verify that the .msi package or the .msp package is correctly signed. ResolutionA supported fix is available for Windows Server 2003. There is no fix available for Windows XP. Windows Server 2003 hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Windows Server 2003 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.Note Download the hotfix by following the instructions later in this article. Update for Windows Server 2003 (KB925336)119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file. File name File version File size Date Time Platform SP requirement Service branch Advapi32.dll 5.2.3790.2895 620,544 07-Mar-2007 07:05 x86 SP1 SP1QFE Advapi32.dll 5.2.3790.4036 619,008 07-Mar-2007 07:02 x86 SP2 SP2QFE Update for Windows Server 2003, x64 Edition (KB925336)119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file. File name File version File size Date Time Platform SP requirement Service branch Advapi32.dll 5.2.3790.2895 1,051,648 07-Mar-2007 07:52 x64 SP1 SP1QFE Wadvapi32.dll 5.2.3790.2895 620,544 07-Mar-2007 07:52 x86 SP1 SP1QFE\WOW Advapi32.dll 5.2.3790.4036 1,052,160 07-Mar-2007 16:52 x64 SP2 SP2QFE Wadvapi32.dll 5.2.3790.4036 619,008 07-Mar-2007 16:52 x86 SP2 SP2QFE\WOW Update for Windows Server 2003 for Itanium-based Systems (KB925336)119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file. File name File version File size Date Time Platform SP requirement Service branch Advapi32.dll 5.2.3790.2895 1,481,216 07-Mar-2007 11:42 IA-64 SP1 SP1QFE Wadvapi32.dll 5.2.3790.2895 620,544 07-Mar-2007 11:42 x86 SP1 SP1QFE\WOW Advapi32.dll 5.2.3790.4036 1,482,240 07-Mar-2007 16:53 IA-64 SP2 SP2QFE Wadvapi32.dll 5.2.3790.4036 619,008 07-Mar-2007 16:53 x86 SP2 SP2QFE\WOW PrerequisitesNo prerequisites are required. Restart requirementYou must restart your computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes. File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. WorkaroundThis workaround applies to Windows Server 2003 and to Windows XP. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows To work around this problem, change the PolicyScope registry value to 1 before you try to install the package. To do this, follow these steps. Note If the computer is joined to a domain, a domain policy update may override the registry changes that you make. We strongly recommend that you disconnect the computer from the domain before you follow these steps.
If the previous steps do not resolve the issue, follow these steps:
Important After you follow the previous steps, local administrators can install the .msi package or the .msp package. After the package is installed, reset the enforcement level by following the previous steps. In step 5, click All users instead of All users except local administrators. Notes
More InformationStarting with Microsoft Windows XP, a security policy named Software Restriction Policies (also known as SAFER) was introduced to help users avoid running unsafe files. Windows Installer uses Software Restriction Policies to verify the signatures of signed .msi package files and signed .msp package files. Windows Installer does this to make sure that the files were not tampered with before they are installed on the computer. Windows XP and Windows Server 2003 require the whole .msi package file or the whole .msp package file to be loaded into one contiguous piece of memory in the address space of the Windows Installer process. If a .msi package file or a .msp package file is too large to fit into a contiguous piece of virtual memory, Windows Installer cannot verify that the package is correct. In this scenario, you experience the symptoms that are described in the “Symptoms” section. The fix that is described in this article enables Software Restriction Policies to use less virtual memory to perform the signature verification. Therefore, Windows Installer can verify any size files. |