FG

Why would SYSTEM continue locking executable file handles after the app has exited?

Fresh3 days ago
Mar 15, 202643703 views
Confidence Score0%
0%

Problem

I'm seeing strange behavior on my Windows 7 machine; it appears that when an executable runs, SYSTEM keeps a handle to it open for the next minute or so. Here's my most recent encounter: I installed Steam, which starts steam.exe post-install to update itself. It appears to do this by writing a temp…

Error Output

C:\>fltmc instances
Filter                Volume Name                              Altitude        Instance Name      Frame  VlStatus
---------------…

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Unverified Fix
New Fix – Awaiting Verification

Fix for: Why would SYSTEM continue locking executable file handles after the app has exited?

Low Risk

Do the following: Disable Indexing on the problematic location. Enable the "Application Experience" service and set it to "Automatic". That is it. If your problem still persists, it may be Superfetch, although disabling that has brought me no luck.

Awaiting Verification

Be the first to verify this fix

Sign in to verify this fix

Environment