OK but it does allow one to manage updates and installs to utilities from Sysinternals Suite. But I guess you don't like that it is 3rd party software.
Advertising a paid third party software is generally not allowed. Maybe if it were free, but there are many software updaters, so it is kind of an offtopic. Well the link on softpedia leads to the official sysinternal download. Code: http://download.sysinternals.com/files/Autoruns.zip
Maybe they could mention it somewhere, so far it looks, that the outdated version is free and the new version is just a trial. Looks nice though.
Yes, it isn't obvious ... I said I wouldn't say more, but it is there - see partial screenshot from website below:
Hello, Autoruns for Windows version 13.52 has been released. Webpage: https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx Although the webpage still says version 13.51, the download is actually 13.52. I did notice that the download contains 64 bit versions in addition to the 32 bit versions now. When I ran and compared both versions, the results were quite different. I could not find any reference to a changelog or to the differences in the versions (32 vs 64 bit).
Thanks puff-m-d. Nice to see a 64bit version. The obvious difference is the detection. I see better coverage on Windows x64 w/ AutoRuns 64bit version.
Running the 64-bit version, AutoRuns found several red & yellow entries that were not there before. Excellent!
Something is wrong with the 64bit-version of AutoRuns. For some microsoft-drivers i see the imagepath: c:\windows\syswow64\drivers\ and 7-8 entries are marked red. But at the bottom left of the window is displayed: c:\windows\system32\drivers\ and in the registry too: c:\windows\system32\drivers So the imagepath should be displayed like this: c:\windows\system32\drivers\ (and not marked red) but it isn't If i start the 32bit-version i now see system32\drivers\ entries in AutoRuns, and that's correct on a 64bit-system.
@mood I confirm the same thing here. Those Syswow64 driver images don't even exist. You can right click then click "Jump to Image..." explorer opens This PC view.
I can confirm the ImagePath issue as well. And if you save the results, then clicking the AutoRuns log file, it won't open. Instead, one sees a "The file is corrupt" prompt. Clicking OK, opens a blank AutoRuns.
Autoruns v13.52 now officially published, still is the defective x64 exe in the zip file though. https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx
Just noticed myself that they officially released it. No change made, despite a user post on the official AutoRuns forum reporting this problem.
Autoruns v13.61 available now. No changelog seen yet. noted http://forum.sysinternals.com/autoruns-x64-1361-crashes_topic32252.html
Autoruns for Windows v13.52 Published: July 4, 2016 https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx Autorun zip now contains the v13.61 x32 and v13.61 x64
Same experiences with AutoRuns 64bit. 0xc000007b error usually comes from mixing up 32bit environment with 64bit. I guess there are some developers who don't test the compiled code before uploading to the download server.
