Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I copied a few million files from one disk array to another on a Server 2008 box. Then I wanted to move the share that people used to access those files, so it would point at the new location of the files.

I innocently clicked "stop sharing" on the first share, thinking it would just delete a record somewhere, and deny network access to the directory.

That was three hours ago, and Windows still says "Stop sharing... this may take a few minutes". I assume that means it's updating the permissions on every file in under the shared directory. yay.

How can I figure out how much longer I have to wait?

What happens if I click cancel?


share|improve this question

It sure does sound like a file is currently open or somehow locked in use. try PsFile from Sysinternals (now a part of Microsoft) it will help you track the file. no reboot necessary to install this utility.

share|improve this answer
Thanks, Nicholas. PsFile reports that none of the files are open. PerfMon shows that the disks have been running hard since I tried to drop the share; it looks like the server is working, not waiting. – Jesse Oct 14 '10 at 14:55
The lock then appears to be local. Could be volume shadow copy or any sort of local file replication? An ntbackup job? If you can check the disk access on the local system itself what files are open from there, visible in the task manager as well under resource monitor this might help provide more insight. – Nick O'Neil Oct 14 '10 at 15:00
Looking at perfmon, I see file accesses by System, dllhost.exe, and explorer.exe. These keep changing -- it seems like they're accessing every file in the share. – Jesse Oct 14 '10 at 15:08
How can I tell if something is holding a lock? – Jesse Oct 14 '10 at 15:08
try starting task manager, go to performance, click 'Resource Monitor' at the bottom and then expand Disk, see what processes are reading files, check to see if those files are the path which was the share which was initially mentioned. also check under cpu, memory and network they will give more insign to see what is going on. – Nick O'Neil Oct 14 '10 at 15:10

As far as I can see, Windows was hung for no good reason. I clicked cancel, which immediately closed the dialog. I was then able to edit and create the shares I needed very quickly.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.