Subject: AutoRuns Compare - All entries green
Posted: 31 March 2014 at 8:15pm
Hi,
Same here.
The compare function has been acting strangely for some time but this is the oddest yet.
http://forum.sysinternals.com/autoruns-1160-compare-issue_topic29443.html
You can try emailing Mark about it again.
You can delete the Registry entries if you want.
If you really want to be tidy, delete the Windows.old folder.
![]() Feature request 2: Often, it is not enough to exclude an exact path (like C:\Windows\System32\KernelBase.dll). Instead, we most likely want to exclude entire directories (e.g. C:\Windows\System32\). When right-clicking a path, there should be the option to exclude that path, or any parent path of it. Example: I click on "C:\Windows\System32\KernelBase.dll" and get: Exclude "C:\Windows\System32\KernelBase.dll" Exclude "C:\Windows\System32\" (StartsWith) Exclude "C:\Windows\" (StartsWith) Exclude "C:" (StartsWith) |
![]() |
![]() I often need to filter only by read only events or write events. a right click option to do this would be great. so for example once the write view mode is enabled any actions on the files or registry that have to do with read (enum, query....etc) would be filtered out. the viceversa applies.. when in read view mode...all the write/modify actions will be filtered out. |
You can set a filter for these by right-clicking in the Category column and choosing Include or Exclude.
Or, you can manually build the filter in the Filter dialogue box. A favorite filter of mine is to show only writes, which does what you wish by hiding all read activity.
Category is Write then Include
![]() If there any possibility of adding in a feature to the CLI to take a large process monitor file and parse it with a filter to a smaller output file it would be a lifesaver. Something similar to what you can do with Tshark for wireshark traces, and with the netmon command line switches. I have tried this procmon /OpenLog Non_working.PML /LoadConfig ProcmonConfiguration. pmc /Quiet /SaveAs output.pml But the resultant file was just the same size as the input file. I had selected drop filtered events and the filter did work in the loaded trace. |
![]() |
I tested this and it seems to work as you requested.procmon.exe /OpenLog Non_working.PML /LoadConfig ProcmonConfiguration.pmc /Quiet /SaveAs output.pml /saveapplyfilter
About "Wear leveling" ...
http://en.wikipedia.org/wiki/Wear_levelling
Without using the "-C" parameter (clean free space) or the "-Z" parameter (zero free space), the file may not be securely deleted; and remain present on the storage medium.