> Source: [sk139752](https://support.checkpoint.com/results/sk/sk139752)

# sk139752 - Endpoint Security Client upgrade or uninstall fails with "Error 26795"

| Property | Value |
|----------|-------|
| Solution ID | sk139752 |
| Date Created | 2018-11-06 |
| Last Modified | 2021-03-09 |
| Technical Level | General |
| Products | Endpoint Security |
| Versions | Cloud, E89.X, E88.X |
| OS | Windows |

## Symptoms

- * Upgrade or uninstall of Endpoint Security Client fails with "error 26795".
* Error message looks something like the following: "Cached msi C:\\WINDOWS\\Installer\\XXXXXXX.msi of version 8X.XX.XXXX does not exist. Refer to sk139752"
* The MSI package file of previously installed client is missing.

## Cause

The missing MSI package file is the cached Endpoint Security Client package that was used for the installation/upgrade of the installed client. This file contains information about what files/folders/registry objects where installed, and this information is used by the Microsoft Windows Installer to remove unnecessary objects as a part of uninstallation/upgrade process.

This is the regular flow of any MSI package uninstallation/upgrade and the Windows Installer cannot proceed when corresponding cached file is missing.

This cached package is a part of the Microsoft Windows Installer database and should not be removed manually.

End users may delete the file directly, or indirectly (using any cleanup tools), to gain more space of their system drive, provided they have administrator privileges.

## Solution

* The same Endpoint Security Client package must be restored at the location specified in the error message by copy and rename operations as described below:

1. In the error message, check what Endpoint Client version is missing. For example, the string "80.84.6075" means that E80.84 is installed and that its build number ends with "6075".
2. For the next step, use the *EPS.msi* package that was used for deployment of the previous Endpoint Security version on this machine. **Using a different package will still result in installation error.**
3. Copy the package to the missing location on the affected machine, rename it according to the filename listed in the error string (e.g. C:\\WINDOWS\\Installer\\33618e3f.msi ).
4. Installation/removal/upgrade retry will work correctly after computer reboot.

<br />

* [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a script to fix this issue.
An installation package used for deployment with the same set of blades is required.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content