If you are unfamiliar with the Sysinternals Process Explorer utility, you should really check it out… it gives you so much more information than the default task manager, including a tree view of all the processes so you can see which processes launched other processes. Če ste seznanjeni z uporabnimi Sysinternals Process Explorer, morate pošteno check it out ... to vam omogoča, da veliko več informacij, kot šef privzeto nalogo, vključno z drevesa zaradi vseh procesov, tako da boste lahko videli, ki je začela postopke drugih procesov. You can look at pretty much every piece of data concerning a process, including associated registry key handles, open files, dlls. Si lahko ogledate precej vsak podatek o postopku, vključno s pripadajočimi registrski ključ ročaji, odprte datoteke, DLL. There's even a search function. Obstaja tudi funkcijo iskanja.

You can also replace Task Manager with Process Explorer through the Options menu, which is the specific subject of this article, since it doesn't always work right in Vista. Prav tako lahko nadomestiti penzum šef s proces raziskovalec preko meniju Options, ki je poseben predmet tega članka, saj vedno ne dela pravice v razgled.

Here's the default screen… take special note of the little tiny graphs there. Tukaj je privzeti zaslon ... se posebej omeniti malo drobnih grafi tam.

If you click on those little graphs, or hit the Ctrl+I key combination, you'll bring up the System Information dialog, which gives you even more information. Če kliknete na tiste malo grafov, ali zadeti Ctrl + I kombinacijo tipk, boste bruhati pogovorno okno Sistemske informacije, ki vam daje še več informacij. Just try moving your mouse over any of the spikes in the graph… it'll show you which application caused that spike. Samo poskusite se gibljejo z miško nad katerim koli od dvige grafa ... da boste vi, ki kažejo, da uporaba povzročila spike.

Update Posodobitev

The latest version of Process Explorer doesn't have any problems with Vista, so everything below this point is for informational purposes only. Najnovejša različica za proces raziskovalec nima nobenih težav z Vista, tako da je vse pod to točko je zgolj informativne narave.

The problem comes in when you try to choose the Replace Task Manager option under Windows Vista with UAC enabled. Problem pride, ko ste poskušali izbrati nadomestiti penzum šef možnost v okviru sistema Windows Vista z omogočeno UAC.

note: If you've disabled UAC, no need to read beyond this point. Upoštevajte: Če ste onemogočen UAC, ni treba brati nad to točko.

If you haven't Če še niste disabled UAC invalidi UAC , you'll get this error message: , Boste dobili to sporočilo o napaki:

The problem happens because by default Task Manager isn't launched with administrative permissions, so the replacement for it isn't either. Problem se zgodi, ker privzeto Task Manager ni začela z upravnimi dovoljenja, tako da za zamenjavo ni niti. What we'll need to do is re-map the registry entry so that you can run it through the Start++ utility's sudo command to elevate it to administrator before we start it. Kaj bomo morali storiti, je ponovno zemljevid vnos v registru, tako da lahko zaženete prek Start + + uporabnost je sudo ukaz, da bi povzdignil administratorja, preden začnemo to.

First, make sure that you download and install Najprej se prepričajte, da prenesete in namestite Brandon Paddock's Start++ utility Brandon's Paddock Start + + uporabnost , which contains the sudo command we'll need for this. , Ki vsebuje ukaz sudo bomo potrebo po tem. (You could also use the elevate powertoy if you were so inclined) (Lahko uporabite tudi oplemenititi sila, če ste bili tako naklonjeni)

Now you'll need to open up your registry editor and browse to the following key. Sedaj boste morali odpreti vaš registracija urednik in poiščite ta ključ. You should note that if you want to turn off the replacement of Task Manager you need only delete this key. Vedeti morate, da če želite izklopiti zamenjavo upravitelja opravil morate le izbrisati ta ključ.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\taskmgr.exe HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Image File Execution Options \ Taskmgr.exe

Now look for the “Debugger” value in the right-hand pane and change it to point to this command string, which you'll need to modify to match your username, and the location where you put process explorer. Poglej za "Debugger" vrednost v desnem podoknu roko in jo spremenite v točko na ta ukaz niz, ki jih boste morali spremeniti, da se ujemajo z vašim uporabniškim imenom in lokacijo, kjer si dal proces raziskovalec. The key thing here is that it needs to be the full path to sudo.cmd as well as the full path to process explorer. Ključna stvar v tem, da je treba celotno pot do sudo.cmd, kot tudi celotno pot do procesa raziskovalec.

c:\users\geek\AppData\Local\Start++\CMDs\sudo.cmd c:\users\geek\bin\processexplorer\procexp.exe c: \ users \ geek \ AppData \ Local \ Start + + \ CMDs \ sudo.cmd c: \ users \ geek \ bin \ processexplorer \ procexp.exe

Note that there should only be a space between the two paths. Upoštevajte, da bi moral obstajati samo prostor med dve poti. After that, you should be able to replace task manager with process explorer just fine. Po tem, morate biti sposobni nadomestiti penzum šef s procesom raziskovalec šele lep.

Download Sysinternals Process Explorer from Microsoft Download Sysinternals Process Explorer od Microsofta

note: Thanks to the great and wonderful Steve for the heads up on this one. opomba: Zaradi velike in čudovit Steve za vzglavje ki gre gor na tega.