Purpose & Applicability

This article explains the root cause and resolution for Seclore uninstallation/installation failures when deployed via ManageEngine Endpoint Central task sequences.

This issue is applicable in environments where:

  • Deployment is performed through Manage Engine using task sequence (Uninstall → Reboot → Install → Reboot) all in one sequence.
  • Machines are left unattended after reboot (no user login)
  • Seclore installation is performed via MSI package


Issue

During deployment via ManageEngine:

  • Uninstallation completes successfully
  • Machines reboot successfully
  • Installation fails on some machines

Observed behaviour:

  • Deployment succeeds only on machines where the user logs in after the first reboot in the above sequence
  • Deployment fails on machines with no active user session after the first reboot.


Event Viewer Logs from one of the failed machines 

Product: Seclore -- Error 1723.
There is a problem with this Windows Installer package.
A DLL required for this install to complete could not be run.
Action FSDCOnMoved, entry: f7, library: C:\WINDOWS\Installer\MSIF0DF.tmp





Key Observations from testing on 4 different machines

  • Deployment tested on 4 machines:
    • 1 machine succeeded → user logged in after the first reboot of the sequence.
    • 3 machines failed → no user login after reboot
  • Seclore was successfully uninstalled on all machines
  • Installation behaviour depends on user session state

Cause
The installation failures are attributable to the absence of an active, interactive user session after the reboot on the failed machines. In this condition, locked/inactive sessions may unload or restrict access to portions of the user profile, impacting per-user folders required by custom actions.




Resolution:
Improved Deployment Approach

Separate the workflow into two sequences:

  • Sequence A (Uninstall):
    • Uninstall Seclore
    • Reboot the machine (if required)
  • Sequence B (Install):
    • Install Seclore only when:
      • A user is actively logged in, and
      • Seclore is not already present on the endpoint

This ensures the installation runs under a valid user context and avoids failures.