Confirmed. Autoruns64 v.13.61 crashes upon start up with 0xc000007b error. M$ should implement an Insiders program just like their Windows OS
I went to download yesterday and if I remember right, there was a 64 bit version I tried and didn't get the error on startup. my version is 13.52. I will have to try the 13.61 and see how that goes. edit: I see what you are saying. the version shown on the site is 13.52 but the download is indeed 13.61 and mine crashes also. x64 version crash upon start up (0xc000007b)
They don't even test the executables before they go public I think we have to wait a few weeks until we have a correct 64bit version.
Does anybody have problems with Autoruns crashing while saving data? I have this problem since 13.51.
It appears like it crashes but I let it run for a couple min and saved just fine. 13.52 however when I try to open the file it shows corrupt. edit: I timed the save and on my machine it was saved to desktop. it took 2 min 10 sec.
I have similar experience. It crashes (or at least Windows says it crashed and closes it) and then created file is not usable.
Re Autoruns v13.61: Few minutes ago downloaded once again. https://technet.microsoft.com/el-gr/sysinternals/bb963902(en-us).aspx Seems that problem solved [x64 version crash upon start up (0xc000007b)]. also here=
841896 Autoruns64.exe (v13.61) https://live.sysinternals.com/Autoruns64.exe And again these SysWOW64-Entries for non-existing drivers But the 32bit-version works fine.
There happens to be multiple issues with AutoRuns 64bit. Trying to launch as Administrator via AutoRuns File menu fails. Error importing file: The system cannot find the path specified. AutoRuns screen then disappears and reappears with a empty listing AutoRuns entries are randomly being giving syswow64 location and file not found status. "C:\Windows\system32\hkcmd.exe” can get reported as c:\windows\syswow64\hkcmd.exe
Lists that date, but the download server gets updated and the version on the site doesn't reflect it for some time afterwards.
Just tried the latest version 13.61. not seeing: crash on launce of autoruns anymore. not seeing: Trying to launch as Administrator via AutoRuns File menu fails. save function: now appears to work even though it takes a few min. am still seeing: AutoRuns entries are randomly being giving syswow64 location and file not found status. virustotal feature seems to work a bit better.
Trying to launch as Administrator via AutoRuns File menu fails. Error importing file: The system cannot find the path specified. AutoRuns screen then disappears and reappears with a empty listing The above happens under both the x64 and the x86 versions running under Windows 10.
Autoruns v13.62 https://technet.microsoft.com/el-gr/sysinternals/bb963902(en-us).aspx Thursday, July 28, 2016 https://live.sysinternals.com/
Sysinternals Suite Updated: July 29, 2016 https://technet.microsoft.com/en-gb/sysinternals/bb842062 ------------------- What's New (July 29, 2016) Sysmon v4.1 https://technet.microsoft.com/en-gb/sysinternals/default.aspx
Sysinternals Suite Updated: August 29, 2016 https://technet.microsoft.com/en-gb/sysinternals/bb842062 ------------------------- Update: Sysmon v4.12, Autologon v3.1, Sigcheck v2.54, Process Monitor v3.31 https://blogs.technet.microsoft.com...on-v3-1-sigcheck-v2-54-process-monitor-v3-31/
Process Explorer 16.20 (procexp & procexp64) Nov 17, 2016 https://live.sysinternals.com/ http://www.majorgeeks.com/files/details/microsoft_process_explorer.html
I see that they've finally added Control Flow Guard detection for processes in 16.20 which is nice. I'm not too sure yet what else is new yet.
@Mister X That is interesting, I would have figured that it would show CFG correctly for an updated Windows 8.1 machine. There must be some slight difference between the way in which a program can query processes for CFG status between Windows 10 and Windows 8.1 but hopefully somebody who frequents that Sysinternals forums can bring this up there as well for the developers to fix.
