Removing a stuck WinFsp on Windows: real diagnostics, MSI failure, and forced removal

Removing a stuck WinFsp on Windows: real diagnostics, MSI failure, and forced removal

This incident involved a broken WinFsp uninstall flow: MSI inconsistency, protected directory, and winfsp-x64.dll locked in memory.

Core diagnostic flow

1. Validate MSI registration:

wmic product where "name like '%WinFsp%'" get name, version, identifyingnumber

1. Do not trust service state alone:

sc query winfsp
driverquery /v | findstr /i winfsp
fltmc | findstr /i winfsp

fltmc output indicates the filter driver is still active in kernel space.

1. Use PowerShell-native deletion syntax:

Remove-Item "C:\Program Files (x86)\WinFsp" -Recurse -Force

1. If deletion fails after ownership/ACL fixes, treat it as handle lock:

.\handle64.exe winfsp-x64.dll

1. If needed, remove in Safe Mode and clean driver/service registry residue:

reg delete "HKLM\SYSTEM\CurrentControlSet\Services\WinFsp.Launcher" /f

Conclusion

This is not a “simple uninstall issue.” It is a kernel-adjacent persistence and lock problem. A layered workflow (MSI -> driver -> handles -> registry cleanup) is what makes removal permanent.

This post is licensed under CC BY-NC.