Uninstalling Actifile: Unloading and Removing the filter driver

Problem: In some cases, the installer may fail to unload the filter driver. This typically happens when the system was busy and could not release the busy driver. In these cases the filter driver may remain after Actifile is uninstalled

Symptoms: In rare cases the leftover driver (while not active) may cause long boots and boot issues.

Avoiding the issue: This issue can be avoided if Actifile is disabled prior to uninstalling the Actifile Package.
To disable Actifile, run the Powershell script Disable-Actifile.ps1 located in the Powershell Support Script directory (c:\Program Files(x86)\Actifile Agent\Powershell Support Scripts\). Once complete, uninstallation of the Actifile agent can be completed.

If Actifile was previously removed:
The following Powershell script removes the Actifile Filter. It first unregisters the filter from the filter hierarchy, and then deletes EaseFilter from the System32 directory. It should be run with elevated privileges:

fltmc unload EaseFilter
remove-item -Path $Env:WinDir\System32\drivers\EaseFlt.sys -Force

Alternatively, the following self-running code (a compiled version of the script above) can be used.

Verifying Removal: To check if EaseFilter is loaded on a machine you can use the following PowerShell script (as admin):

fltmc filters

The output will look like this:

PS C:WINDOWSsystem32> fltmc filters
Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
bindflt        1 409800 0
FsDepends 69 407000 0
WdFilter 69 328010 0
storqosflt 0 244000 0
wcifs 3 189900 0
EaseFilter 7 186200 0
CldFlt 63 180451 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
Wof 67 40700 0
FileInfo 69 40500 0

The highlighted row shows that EaseFilter is loaded.

Powered by BetterDocs