You could try https://en.wikipedia.org/wiki/Unlocker to determine who exactly locks file.
As shown by the screencapture above, the issue is not the file being locked by a process (which I also verified with sysinternals). Also, as mentioned, it can be deleted.
Can you rename it? Can you move it to another folder? (with shutdowned service of course)
Rename it: yes. Delete: yes. Copy/move: No.
What exactly util from sysinternals did you use for locks check?
You can search for a filename and see all handles open to that file. When the glasswire service is running, it of course shows the connection to glasswire.db; when stopped, nothing is using it. Regardless though, this clearly isnât an âin-useâ error - or renaming/deleting wouldnât work (and the Windows error message would be related to âin useâ rather than to ownership/permissions)âŚ
Are you talking about ProcessExplorer ( http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx )? - there are too many different utils on SysinternalsâŚ
yes, process explorer.
Then could you please try unlocker anyway? Just to be sure.
Iâm not sure why you keep going on this line of âin use by another program.â It clearly isnât. That isnât the problem.
Because IMHO there are only 3 reasons could be why file could not be deleted:
- itâs opened in some application;
- it has some specific permissions by filesystem;
- filesystem is corrupted;
And whatâs special in âglasswire.dbâ? - itâs the only file created from service (i.e. from SYSTEM account)⌠And thus some security application could apply some specific rules to it.
Maybe Iâm wrong, but I donât see any other options.
- Definitely not. Again, Iâve verified that there are no open handles, the message shown by Windows is unrelated to âin use,â and I can rename/delete it, which obviously wouldnât be possible if it were open. Also, itâs not copyable in safe mode either.
2 & 3) Maybe, but Iâm totally out of ideas.
And whatâs special in âglasswire.dbâ?
No idea whatâs so special about it, but thatâs why Iâm posting here.
Here, maybe this will prove it to you:
->If I stop the service, delete glasswire.db, and create my own âglasswire.dbâ file (an empty textfile), I can copy & manipulate it as usual.
->If I stop the service, delete glasswire.db, and restart the service - letting Glasswire recreate its own file - it has the problem.
So whatever Glasswire is doing when it creates this database, itâs clearly weird. Never had this problem with any other file, and it only happens when Glasswire creates it.
Glasswire support, PLEASE chime in??
Unfortunately Iâm not sure I understand fully what is happening either. Nobody else has reported this problem and I canât recreate it myself. I will continue to investigate and see if I can come up with something to help.
Iâm sorry for the delay in solving the problem. I wish I knew!
Will any more info / screen captures / etc to show exactly whatâs happening be helpful?
I really have put hours into this, as well as run it past numerous extremely computer-knowledgeable people. Nobody has any idea whatâs going on. The message seems like an obvious issue of file ownership, but as mentioned, even after explicitly taking ownership & giving my own user account full permissions, just this file and no others wonât let itself be copied (renamed/deleted are OK, though): http://screencast.com/t/7eVUDmOUkE
I would try unlocker nothing to lose
âŚOk? Now can we please move on from the unlocker/file handle thing?
(& yep, I tried rebooting too - the file was not moved.)
âŚHereâs some new info tho! It appears to only happen with operations that actually require rewriting the contents of the file:
-I can delete it
-I can rename it
-I can move it within the same logical drive as where it started
-I cannot copy it
-I cannot move it to another drive (effectively a copy-and-delete)
-I cannot open it in a text editor
So it appears to specifically be the operation of reading its contents that arenât allowed. Although obviously Glasswire can read its contents.
What security/antivirus/anti-malware software do you have on your computer?
Microsoft Security Essentials, but as mentioned, I tried it in Safe Mode (in which case no security/antivirus/anti-malware is running). Same story.