System locks files
-
Thursday, February 28, 2013 2:48 PM
I have experienced this problem many times on many different Windows 7 x86 installs and machines, sometimes even with a different source of installation. It only seems to occur under the condition that I move Users and ProgramData on a seperate partition on the same harddrive. Every individual case of this problem occurs when I touch a file, for example a rename or modification. When I try to delete the file, it will last like 5 minutes before it will automatically delete as if it was in some kind of queue, this part really puzzles me. It is also possible to remove the handle by logging off. For the information; the seperation of userfiles and systemfiles has always been done properly even though Windows' obvious poor support, all values under ProfileList have been modified to refer drive D, and hardlinks have been setup on the systemdrive. The main question is; What can cause the kernel to register a handle on files making me unable to modify, rename or delete them? It doesn't make sense.
Handle v3.5 Copyright (C) 1997-2012 Mark Russinovich Sysinternals - www.sysinternals.com System pid: 4 type: File 71C: D:\Users\Administrator\test.txt
Here is an example of the kernel holding a handle on one of my files, directly after having done a few modifications to it.
- Edited by Mzzr77 Thursday, February 28, 2013 2:48 PM
- Edited by Mzzr77 Thursday, February 28, 2013 2:49 PM
- Edited by Mzzr77 Thursday, February 28, 2013 2:50 PM
- Edited by Mzzr77 Thursday, February 28, 2013 2:50 PM
- Edited by Mzzr77 Thursday, February 28, 2013 2:51 PM
- Edited by Mzzr77 Thursday, February 28, 2013 2:57 PM
- Edited by Mzzr77 Thursday, February 28, 2013 3:02 PM
- Edited by Mzzr77 Thursday, February 28, 2013 3:03 PM
- Edited by Mzzr77 Thursday, February 28, 2013 3:04 PM
- Edited by Mzzr77 Thursday, February 28, 2013 3:05 PM
- Edited by Mzzr77 Thursday, February 28, 2013 3:05 PM
- Edited by Mzzr77 Thursday, February 28, 2013 3:06 PM
- Edited by Mzzr77 Thursday, February 28, 2013 3:08 PM
- Edited by Mzzr77 Thursday, February 28, 2013 3:10 PM
All Replies
-
Friday, March 01, 2013 6:07 AMModerator
Please test if you can modify the files in Safe Mode and clean boot.
Niki Han
TechNet Community Support
-
Sunday, March 03, 2013 12:20 AM
Hi Niki,
I just tried, and the problem doesn't occur in safe mode. Does this give you any clue, might a service be the cause? And if so which one is most likely?
I'm pretty sure this is not caused by a third party driver, since I have experienced this problem on multiple machines, with completely different hardware setups. And always under the same condition: splitting user files from program files..
-
Monday, March 04, 2013 3:41 PM
If the problem does not occur in Safe Mode then it is caused by some task or service that starts in Normal Mode only. You can use msconfig.exe to find the culprit.I just tried, and the problem doesn't occur in safe mode.
-
Monday, March 04, 2013 9:22 PM
I just tried, and the problem doesn't occur in safe mode.
If the problem does not occur in Safe Mode then it is caused by some task or service that starts in Normal Mode only. You can use msconfig.exe to find the culprit.
I understand, and I'd appreciate some direction. Many many services available!- Edited by Mzzr77 Monday, March 04, 2013 9:22 PM
-
Monday, March 04, 2013 9:43 PM
I understand, and I'd appreciate some direction. Many many services available!
This simply a matter of patience and perseverance:
- Boot into Safe Mode
- Click the Start globe
- Type the word msconfig in the Search box and press Enter
- Untick every tick mark under the Startup tab.
- Click the Services tab, then tick the box that hides the Microsoft services.
- Untick every remaining tick mark.
- Reboot in Normal Mode.
- If this fixes the problem, restore the tick marks in groups of 4 until you find the culprit, then leave it unticked.
- Edited by OberwaldMicrosoft Community Contributor Monday, March 04, 2013 9:43 PM
-
Tuesday, March 05, 2013 2:12 PM
I understand, and I'd appreciate some direction. Many many services available!
This simply a matter of patience and perseverance:
- Boot into Safe Mode
- Click the Start globe
- Type the word msconfig in the Search box and press Enter
- Untick every tick mark under the Startup tab.
- Click the Services tab, then tick the box that hides the Microsoft services.
- Untick every remaining tick mark.
- Reboot in Normal Mode.
- If this fixes the problem, restore the tick marks in groups of 4 until you find the culprit, then leave it unticked.
Its caused by a Microsoft service. -
Tuesday, March 05, 2013 4:33 PM
Which one?Its caused by a Microsoft service.
-
Tuesday, March 05, 2013 5:33 PM
Its caused by a Microsoft service.
Which one?
I don't know, I'll have to figure out -
Wednesday, March 06, 2013 10:15 PM
Update.
I have disabled all services. Problem still persists. I suspect this has a funny cause, but what?
For .bat and .exe files, it directly occurs after I have executed them. It doesn't really seem to happen to other file types like .jpg
For the information; Windows Defender is disabled, I have absolutely no security software installed on any machine.
And Again:
I have experienced this problem many times on many different Windows 7 x86 installs and machines, sometimes even with a different source of installation. It only seems to occur under the condition that I move Users and ProgramData on a seperate partition on the same harddrive.- Edited by Mzzr77 Wednesday, March 06, 2013 10:16 PM
-
Wednesday, March 06, 2013 10:48 PM
It might be safer to leave these folders where they are and create a junction to a different drive so that the data is not stored on the System partition. You would need to run some experiments.It only seems to occur under the condition that I move Users and ProgramData on a seperate partition on the same harddrive.
-
Thursday, March 07, 2013 12:26 AM
It might be safer to leave these folders where they are and create a junction to a different drive so that the data is not stored on the System partition. You would need to run some experiments.It only seems to occur under the condition that I move Users and ProgramData on a seperate partition on the same harddrive.
Hey I solved the problem. My configuration script for new installations is to blame.. It disables the Application Experience (AeLookupService) service, disallowing it to run. Somehow the system temporarily locks up if it doesn't receive a call from the service after running a ''unsafe'' file. The creation of the handle is caused by Explorer but owned by system. Appearantly Explorer is hardcoded to depend on the service. Happy to have the problem solved finally, sad because of the poor design. And so after all it had nothing to do with the seperation of folders, I knew that wouldn't make sense but it was most obvious to me somehow.
I learned to be more cautious with services once more after many many years lol.Thanks for the assist.
- Edited by Mzzr77 Thursday, March 07, 2013 12:41 AM
- Edited by Mzzr77 Thursday, March 07, 2013 12:42 AM
- Marked As Answer by Niki HanMicrosoft Contingent Staff, Moderator Thursday, March 07, 2013 4:06 AM
.png)
