I'm going to merge all of my Sysinternal launchers here.
To use any of these wrappers, you will first need to download the executable. I have linked them to the proper page. Download the Launcher. Run the launcher, then follow the instructions in the ReadMe.txt. The links are also given in the readme.
Autoruns Portable
Autoruns Executable
Launcher
AutorunsPortable Homepage
Nascent Mirror
Autoruns Launcher
Homepage
Autoruns checks the registry and tells you whats, well, been set to Autorun
Process Explorer Portable
Process Explorer Executable
Launcher
Process Explorer Portable Homepage
Nascent Mirror
Process Explorer Launcher
Homepage
Process Explorer is essentially a beefier version of Task Manager
Process Monitor PortableNEW!
Process Monitor Executable
Launcher
ProcessMonitor Portable Homepage
Nascent Mirror
Autoruns Launcher
Homepage
Process Monitor allows you to see what a process is doing
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Ill definitively check the out.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
I am also making use of your Sysinternal loaders.
Cheers,
nwpsys
Hey, dude, you should make a lanucher for the BSOD screensaver. I'd love to see some certain people freak out!
There's no place like 127.0.0.1
How Screensavers Work
Doesn't need anything else. Some spyware use this screensaver now, but they run it from a different location than the system screensavers.
~Lurk~
Here's a trick that might be useful. This applies to Autoruns, but the same thing should work with the others.
It applies to the situation where the AutorunsPortable has been installed, but the Autoruns.exe program itself has not been copied to the appropriate directory.
NoProgramEXE: ClearErrors CopyFiles `\\live.sysinternals.com\tools\autoruns.exe` `$EXEDIR\App\${DEFAULTAPPDIR}\` CopyFiles `\\live.sysinternals.com\Tools\autoruns.chm` `$EXEDIR\App\${DEFAULTAPPDIR}\` IfErrors 0 FoundProgramEXEThere are some other changes that might need to be made, like setting variables that normally wouldn't get set if the EXE isn't found. Or just tell the user to restart.
Another option is to have the program run from that location -- that way you always have the latest. Of course that only works if the network/firewall allow.
That trick won't work all the time, obviously, but it should work enough of the time to be helpful.
MC
I think my router blocks SMB (it might be a default setting). So it probably won't work for anyone with a firewall or router with decent default settings (SMB over internet is not a common thing, it's intended for local networks).
Signature automatically removed for being too awesome.
That Sysinternals Live site isn't using SMB, it's using WebDAV which can go through most firewalls/routers. Your web proxy may be filtering executables.
BTW: To use WebDAV on Windows you need the WebClient service running (which is off by default in my experience).
Reference: http://www.edbott.com/weblog/?p=1993
http://en.wikipedia.org/wiki/WebDAV#Microsoft_Windows_clients (some troubleshooting tips)
Cancer Survivors -- Remember the fight, celebrate the victory!
Help control the rugrat population -- have yourself spayed or neutered!
Well, whatever magic Explorer uses to make it happen, if the trick works, the end user doesn't have to copy the files. Perhaps the installer could try the trick, and if it fails put up a messagebox reminding the user to do it manually. Or it could try another way.
I didn't say it would work all the time, just that it might work often enough to save some end users an additional and possibly awkward step. (I suppose someone wanting to use a sysinternals utility should not find that step awkward, but those types tend to be lazy and admire a good trick.)
There's at least one NSIS Plugin to let you use the http protocol directly, if WebDAV is not consistent enough for you. You can download the individual files from http://live.sysinternals.com/tools/, so you wouldn't have to worry about unzipping them.
Anyway, for what it's worth, I was hoping some might find it useful.
(SMB inbound should definitely be blocked at your router/firewall, but I don't believe an outbound SMB connection, if such is possible, bears much risk.)
MC
When I wrote these, I hadn't considered/didn't know about those. There's also a plugin for extraction.
I might consider adding the code for these. At least in Process Explorer and Process Monitor. I want the end user to at least understand zipping/unzipping a file before they start shutting off process willy nilly.
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
Here's another way to accomplish it, this time putting it in the installer:
;=== BEGIN: POST-INSTALL CODE CopyFiles `\\live.sysinternals.com\tools\autoruns.exe` `$INSTDIR\App\autoruns\` CopyFiles `\\live.sysinternals.com\Tools\autoruns.chm` `$INSTDIR\App\autoruns\` ;=== END: POST-INSTALL CODEMC
I used these apps without launchers. Now this is corrected. Thank you very much!
from the menu I can not start the process explorer, but it works when I start the launcher directly. What can I correct?
Otto Sykora
Basel, Switzerland
This may be a problem with the appinfo.ini files under App\Appinfo\appinfo.ini.
I'll take a and report back, as I'm curently swamped.
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
since I managed to correct this behaviour for other apps which did this.
But somehow did not get the the things right for this one her.
Otto Sykora
Basel, Switzerland
I am unable to start process explorer from the menu. I noticed that in the appinfo.ini on the last line, there is an extra "c" in Start=ProccessExplorerPortable.exe. However, when I corrected this, I was still unable to start Process Explorer fromthe menu.
In addition, the autorunsportable.ini in the other/source directory is for Startup Manager Portable.
You may have needed to restart the menu. The ini is probably wrong. I haven't taken the time to update these. I will do that at some point, but not right now.
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
I'm guessing you didn't do this because you were bored and the whole suite is just a bunch of executables and docs that you can just dump into a folder in the portableapps folder and it'll run fine. So I guess they leave something behind...but I have no idea what that is?
you can run regshot and you will see it is not so much they leave in the registry.
Just if you run the exe first time, it will make entries to the registry , yo uhave to click away some eula.
If it does not disturb, it is ok, I am also usung most things just plain.
Otto Sykora
Basel, Switzerland
I love the new quote feature. They leave registry keys behind in HKEY_CURRENT_USER\Sysinternals\AppName
The launcher simply backs up the registry key (if its already there), then inserts the user's (your) settings. When the program exits it reverses the procedure.
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
.. what would stop this being a single install? I.e. one that allows you to unzip the entire sysinternals suite into the Apps directory and has the main apps (the ones you list above) at top level - and so appear in the portable apps menu.
Then should you decide to add more of their apps it just means adding another exe for new the app rather than creating a new paf project.