The update file set is corrupted

[Бахтиёр]

KSC (15.1) is deployed on the server, and KES (12.7) on the endpoints.
When running updates from the KSC source, many endpoints show the error "Update file set is corrupted," while others (a smaller number of devices) display "Not all components were updated."

I have already cleared the storage and re-downloaded the updates, but the issue persists

[KarDip]

Hello @Бахтиёр

The errors "Update file set is corrupted" and "Not all components were updated" suggest issues with the update distribution or compatibility between KSC 15.1 and KES 12.7 on endpoints. Here’s a detailed approach to troubleshoot and resolve these errors:

---

1. Verify KSC and KES Compatibility

• Ensure that KES 12.7 is fully compatible with KSC 15.1. Compatibility mismatches can cause update issues.
• Refer to Kaspersky's compatibility matrix for confirmation.

---

2. Update the Network Agent

• If the Network Agent on endpoints is outdated (e.g., older than 15.1.0.2), it may not properly interact with KSC 15.1 or deliver updates correctly.
• Action: Upgrade the Network Agent on affected endpoints to the latest version supported by KSC 15.1.

---

3. Recheck Update Sources

• Confirm that KSC's update repository is correctly configured and not pulling corrupted or incomplete updates.
• Action:
  1. Go to Administration Server → Update → Update sources.
  2. Ensure updates are being downloaded directly from Kaspersky's global update servers.

---

4. Clear and Rebuild Update Storage

You’ve already cleared the storage, but let’s ensure it’s thoroughly rebuilt:

1. On the KSC server:
   • Navigate to C:\ProgramData\KasperskyLab\adminkit\1093\updates (default location; path may vary).
   • Stop the Kaspersky Administration Server service.
   • Delete the updates folder.
   • Start the service and re-download updates via Tasks → Download updates.
2. Redistribute updates to managed devices.

---

5. Check Endpoint Logs

• Review the update task logs on endpoints to identify specific files or modules causing the "corruption."
  • Go to KES interface → Reports → Update section.
  • Check which files or components failed.

---

6. Synchronize Endpoint Policies

• If policies between KSC and endpoints are inconsistent, it can prevent proper update distribution.
• Action: Reapply and synchronize the policies:
  • Open Policies → Endpoint policy in KSC.
  • Ensure the update task configuration matches your intended setup.
  • Click Enforce synchronization for affected devices.

---

7. Test with Alternate Update Sources

• Temporarily bypass the KSC update repository:
  • Configure affected endpoints to download updates directly from Kaspersky's global servers.
  • In KES Settings, change the update source to Kaspersky Lab's servers and test.

---

8. Verify Disk Space and Permissions

• Ensure the endpoints and the KSC server have enough disk space and appropriate permissions for update storage.
  • Check: %ProgramData%\Kaspersky Lab\KES\Temp\ on endpoints.
  • Ensure no other software (e.g., antivirus/firewall) interferes with the update process.

---

9. Debugging Further

• Run KSC diagnostics for a sample problematic endpoint:
  1. Open the Device Properties in KSC for an affected endpoint.
  2. Collect logs using the Support Utility (KES trace logs may help identify the root cause).

---

10. Escalate if Unresolved

• If the issue persists, collect the following data and contact Kaspersky Support:
  • Full KSC diagnostic logs (klactool utility).
  • Endpoint logs for update tasks.
  • Details about your environment (KSC version, OS versions, update policies).

---

By following these steps systematically, you should be able to pinpoint and resolve the update errors. Let me know if you need help with specific steps!

Thank you

 

Edited Tuesday at 12:21 AM by KarDip
spellcheck error