First a quite a bit of "background" (and you can skip right to bottom of this posting if you just want to get to a (rather short) description of the actual problem and the (really short) question): I generally run under the "original" user account in Windows 7, and as you may know about Windows 7, that account has only "limited" administrative privileges (and, somewhat ironically, the "real" Administrator account exists but is both "hidden" and disabled by default (I guess Microsoft really wants to prevent people from easily having "full control" over their machines; however, instructions on how to "unhide" it and enable the true "Administrator" account are readily available on the web)). Well these "limited" privileges are not enough to do a number of things that I need to do on a regular basis, and the two most important of those are increasing the priority of the Windows "Magnify" app from the command line (I am visually impaired and really need the "Magnify" app, and it tends to really "bog down" and not update itself very often if at all when the system gets busy), and the second important thing is to run the "handle" command (originally from "SysInternals.com; now owned by and available from Microsoft.com) which displays a list of the processes that have a "handle" on a particular object, and since I have very bad memory (sadly, not at all a joke, another one of my 4 independent disabilities) and like to delete files and directories when I am done with them so I don't have to wonder what they were/what the "status" of whatever they contained is because of my bad memory, and when running in a TCMD/TCC/cmd.exe session that does not have full administrative privileges I get the message "TCC: (Sys) The process cannot access the file because it is being used by another process. file_or_directory_name", so I need to find out what process is "using" the file or (particularly) directory so I can either terminate or do something in the process to cause it to "free" the object (CDing to a different directory is most often the solution in TCC if TCC is one of the "users" of a directory). Well the "handle" command requires "full" administrative" privileges (how Microsoft imagines anyone can run it in Windows 7 is beyond me, running it from the Windows GUI is totally impractical (it creates a cmd.exe "session" to run in, runs in that session, and then terminates itself which also terminates the cmd.exe session, and all of this happens before you have any chance at all of actually seeing the output of the command), and while you can start either a TCMD, TCC, or even cmd.exe session with full administrative privileges from the GUI, I don't like the Windows GUI very much for running programs; I much prefer running these things from a command line (I find the "Start" menu somewhat hard to "navigate" with my bad eyesight, and I use a relatively large font in TCMD/TCC), so therefore when I need to do such things I "Start" TCMD with the "/ELEVATED" parameter to do the either of the above as well as possibly other things.
Now to the actual "problem":
I start a TCMD session with the "/ELEVATED" parameter when I want do anything that requires "full" administrative privileges, but doing so has a rather odd and somewhat annoying side-effect: While TCMD is, in fact, started with full administrative privileges, a totally separate TCC session is also started also with full administrator privileges, which I then have to close. Again, not a major problem, but definitely somewhat annoying.
So, finally, on to the actual question: Why do both a TCMD session and TCC session start and is there anything I can do to prevent that from happening?
Now to the actual "problem":
I start a TCMD session with the "/ELEVATED" parameter when I want do anything that requires "full" administrative privileges, but doing so has a rather odd and somewhat annoying side-effect: While TCMD is, in fact, started with full administrative privileges, a totally separate TCC session is also started also with full administrator privileges, which I then have to close. Again, not a major problem, but definitely somewhat annoying.
So, finally, on to the actual question: Why do both a TCMD session and TCC session start and is there anything I can do to prevent that from happening?
