

This whole adventure began with my noticing and being annoyed by the default behaviour of AdwCleaner when I first tried it the other day: by default it creates a new folder on C: and stores its logs and settings there, no matter where you parked the downloaded program file (AdwCleaner.exe) when you got it. Hitting Scan then will do exactly what you expect it to do, and you'll find that (1) the log is in the folder whose path you specified, and (2) there's no new AdwCleaner folder on C.Įxample from my PC: "D:\Malware Tools\AdwCleaner\adwcleaner_8.2.exe" /path "D:\Malware Tools\AdwCleaner"

If you make a shortcut to the executable and edit the target line of the shortcut's Properties so that after the path to the executable that's already there you enter /path, running it from the shortcut will produce a CLI for a moment, and then go to the usual GUI. I've experimented with it, and made a further discovery that answers my questions: I'm not aware of using it that way but perhaps the Developer may have other ideas for you. That shortcut runs the scan, puts the log in D:\Malware Tools\AdwCleaner\Logs and prevents the creation of an entirely unnecessary intrusion into the C: drive. "D:\Malware Tools\AdwCleaner\AdwCleaner.exe" /scan /path "D:\Malware Tools\AdwCleaner" exe file with the Target line as follows: In my case, I created D:\Malware Tools\AdwCleaner and put the executable there. With the help of a command prompt query on the executable (AdwCleaner.exe ?), I got the idea for the Path parameters, and discovered to my great satisfaction that not only does the use of correct parameters stop the creation of an unnecessary folder on C:, but also puts the logs where they belong, in the same folder as the executable file. Was annoyed by AdwCleaner the first time I ran it, because by default it created a folder on my C: drive (where I put absolutely nothing other than the OS if I can help it) and put its logs there.
