Why would SYSTEM continue locking executable file handles after the app has exited?
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.
KLIF is the Kaspersky AV driver. It's rather likely that it has to do with it.
My course of action in such a case would be to contact Kaspersky and ask for advice.
However, there is another thing you can try first: disable the driver (under HKLM\SYSTEM\CurrentControlSet\Services) by looking for KLIF or something similar as key name and setting the REG_DWORD value named Start to 4 (which means disabled), then reboot. This should prevent the KAV filter driver from being loaded. You can then use fltmc to verify the result.
The output from GMER you gave is irrelevant for the case at hand as it would affect only network connections, not file operations. It seems you had something like Kaspersky Internet Security installed (or still have it dormant on your machine).
Edit: just FYI luafv is responsible for FS virtualization in conjunction with UAC. I.e. if you don't have access to a file it's being put into a separate folder inside your profile. FileInfo belongs to SuperFetch - which actually could be part of your problem, but I've not had a similar problem on Windows 7 myself. It's generally not recommended to disable SuperFetch, though one can.
This happened to me once, and it turned out to be a remote computer which had the share folder open.
- Use Handle to find out what process is holding the file
- (It was System in my case)
- Try to close the Handle:
handle.exe -c E14 -p 4. Your file handle will be found in the output of your search for the file handle, and the processid will likely be the same for system. - It output
Error closing handle: T - Googling this, I found this related to the network
- I found on another machine, I did in fact have the folder open. Closed it. All good.