For perfectly legitimate reasons I don’t want to debate with Linux people, I run WinXP.
But dammit XP, I’M THE ADMINISTRATOR. If I tell you to end a process, DO IT! If I tell you to delete a file, DO IT! I don’t want to see any whiny error messages about a file being locked or in use. And if I tell you to delete a stuck print job from the queue, THEN DO IT! Don’t make me reboot the damn computer to clear the print queue.
What’s the point of having an Administrator account if you don’t have control over these things?
To save you some time in the future, you don’t actually have to reboot in that situation.
Go to Start->Run, type “services.msc” and hit Enter. Scroll down to the Print Spooler service, right click on it, and choose “Restart” from the menu that pops up.
What drives me nuts in not so much that it prevents you from deleting files that are in use, is that it cannot tell you (as far as I know) what is actually using the file.
My guess is a lock is getting set somewhere that’s just a boolean value, saying in use or not, so the OS doesn’t even know itself.
Does anybody know if Vista addresses this problem at all? Seems pretty trivial to me to also store what process/app is using the file.
If you want better control of processes, download Process Explorer, which is everything Task Manager should be. If you want to delete files that are in use, find which process(es) is/are using it with Process Explorer (“find handle…”), kill that process (carefully), then delete the file.
Of course, someone exercising admin rights carefully knew all that, right?
Erm, my extremely minor snark there was directed at the OP, not Revtim who snuck in unnoticed 'twixt preview and post. Yes, XP knows perfectly well which process is using what (it couldn’t operate otherwise), but the bundled task manager is just rubbish. MS’s acquisition of Sysinternals suggests they’re looking to address this in future, though. Hurrah for Mark Russinovich.
Simplified version: In all flavors of UNIX (AFAIK) the “file” you see in the “file system” is just another “handle” (reference) to the actual file object, and can be deleted at any time. A process using the file gets a different handle to the actual file. A file exists so long as any handles to it exist; when the last handle is released (e.g., when the process using the file you just deleted exits) THEN the file is gone.
It’s pretty handy, since you can open a temporary file, delete it right away, and read/write to it without worrying about having to dispose of it when your program finishes.
I’m on the fence about XP deleting files (I usually rename it and try again, then try a command line, then curse). Files stuck in the XP spooler I just ignore, since it’s such a pain to eliminate them.
Here’s something I’ve found that helps with some processes that won’t shut down. When you try to stop a program or close a window and nothing happens, open Task Manager and open Processes. Look for a process with a name like ( going by memory ) DUMPPRP; I probably didn’t spell it right, but it looks like it comes from"Dump Prepare". End that process, and whatever you tried to shut down earlier will also go away. YMMV; I’m not a computer expert, but it works for me.
Apologies for piggybacking on this thread, but my Task Manager is no longer accessible and I was wondering if anyone could help.
Quick background: I got hit with a virus on giants.com, so I updated and ran AVG and Ad-Aware. All clear, all good. But now when I try to run Task Manager, it says “The administrator has disabled the task manager.”
I run multiple accounts, and because I use some crappy “let’s save the data to program files” utilities, they are all administrator accounts. The task manager is only disabled in one of the accounts – my primary one – and it is still listed as an admin account.
What gives? Why is the Task manager greyed out on the taskbar right-click menu, and why does it give me that disabled message when I try to launch it from Start Menu=>Run? Rebooting doesn’t have any affect, as this has been a problem for a couple days now.
