Application removed after Patch deployment

After a third-party patch is deployed, the application can become unusable and then disappear from the computer with no error in the deployment status. Endpoint Central has not identified a known issue in the recent patch package for this behavior.

Checks

Rule out these environmental causes before treating the deployment as a product defect:

• Security products such as antivirus, EDR, or DLP can quarantine an executable, DLL, or other application component. Verify whether a detection was flagged, exclude the application path, and retry the deployment.
• The deployed patch can be superseded. Whether the newer package replaces an older version depends on the vendor-supported installation behavior. The intended version must remain installed and working.
• On an affected computer, also check for a pending Windows restart, recent Windows updates installed around the same time, Windows Installer errors, and Group Policy restrictions.

Resolution

.NET Framework 3.5 can coexist with .NET Framework 4.x. Replacement within the 4.x series is different; see Microsoft version compatibility. If a component disappears, compare the exact task, installer result, Windows servicing events and installed-component state. Review Installed Patches audit fields before changing a decline rule.

1. Disable the antivirus or exclude the application path.
2. Confirm that there is no pending restart, and review recent Windows updates, Windows Installer errors, and Group Policy restrictions.
3. Reinstall the application on a test computer.
4. Deploy the latest available patch for that application and confirm that the new version remains installed.

If the application is removed again after these checks, collect the agent logs from the affected computer for analysis.