ALA-FAEag - Automatic FRST fixlog creation tool.

[Smith83]

hxxp://wxx.ache.nl/cgi-bin/download.pl?file=ALA-FAEag

Drag and drop your frst and addtion.txt files into the ala folder, run the tool and await the fixlist....

Source

Does not catch everything, but it will save time for malware helpers using the FRST tool.

 

[Av Gurus]

Where Log files should be?
I got them on desktop and in C:\FRST\Logs but it couln't find.

 

[Av Gurus]

Added Log to installation folder ( C:\Program Files (x86)\ALA )
But...



Click on Continue and at the end just say fixlist created but I can't find it.

 

[Av Gurus]

OK, i found out.
FRST must be put in installation folder ( C:\Program Files (x86)\ALA ) and then run from there.
Log must be in that folder and Fixlist will be there.

 

[Smith83]

FRST must be put in installation folder ( C:\Program Files (x86)\ALA ) and then run from there.
Log must be in that folder and Fixlist will be there.

Drag and drop your frst and addtion.txt files into the ala folder,

 

[Smith83]

• Download FRST64 or FRST32.
• Save it to your desktop.
• If you do not know whether your machine is 32bit or 64bit check here.
• Download Install ALA.
• Hit start - Computer - Local Disk C:
• Navigate to Program Files x86
• Right Click ALA Create Shortcut.
• Drag ALA shortcut to desktop.
• Right Click FRST run as admin.
• Click SCAN.
• Allow completion.
• Two log Files will appear on desktop. FRST.txt Addition.txt
• Drag them both into ALA folder shortcut on desktop.
• Double click ALA shortcut to open.
• Right Click ALA Application -- Run as admin.
• 
• Press C when prompted.
• Allow completion.
• Drag the newly created Fixlist.txt onto your desktop.
• Right click the FRST program -- Run as Admin.
• Click FIX.

 

[imsoadude]

Tried it out, Works as expected definitely a time saver. Thanks for sharing!

 

[Smith83]

Keep in mind the program is still a baby, it's not gonna get everything. But it will help the average user remove known trash from a machine....

 

[cryogent]

Hi, this software is safe to use?
because failed in VT report 2/55 (Invincea, McAfee-GW-Edition) an Jotti report 1/18 (QuickHeal).
Even FRST (downloaded from 2 source) both 64/32 failed in VT report (2/56 - 4/56).
Is something FP report?

 

[Aura]

Just so you know, we weren't aware of the existence of this tool until today (someone posted it over at BleepingComputer). Some of us will probably test it soon (I will tonight) but as always, we don't really like tools that provides an "auto-creation" functionnality like this one since it's impossible for them to cover every single entries that needs to be fixed. My guess is that it just takes all the lines flagged with "ATTENTION" and puts them in a fixlist.

 

[kev216]

Interesting new and handy software. Thanks for sharing!

 

[cryogent]

Just so you know, we weren't aware of the existence of this tool until today (someone posted it over at BleepingComputer). Some of us will probably test it soon (I will tonight) but as always, we don't really like tools that provides an "auto-creation" functionnality like this one since it's impossible for them to cover every single entries that needs to be fixed. My guess is that it just takes all the lines flagged with "ATTENTION" and puts them in a fixlist.

Thanks for your answer,
however I asked if it's safe because it's reported as infected with something else malicious.
Same for FRST that is not new on the market.

 

[Aura]

The detections for FRST are false positives, I can guarantee you that. As for the ALA-FAEag, I have no idea since I didn't use it yet.

 

[TwinHeadedEagle]

Not a very good tool to use and rely on and here at the reasons.

I attached two reports below that I will compare with ALA and my personal Fixlist creating tool.

First problem is that report must be named exactly FRST.txt and Addition.txt. My tool doesn't require that.

Second reason is output that is very scarce and doesn't help you at all.

I attached both produced fixlist files so you can compare. Must admit that I don't update it that often and there are some lines that could be targeted too. Main reason is because I am the only user , but you can never rely on a tool to check report for you because it isn't safe. You always need to double check, but this helps a lot.

 

[Smith83]

Not a very good tool to use and rely on and here at the reasons.

It can clear the way for a helper, if the logfile is full of junk. You will of course need to go over it manually after.

(someone posted it over at BleepingComputer)

That was me....

 

[Aura]

Didn't know it was you since you don't use the same username here

And to be honest, if the log is full of junk, I personally run JRT, AdwCleaner, Malwarebytes, etc. first to cut it down, and grab a new set after.

 

[Smith83]

My tool doesn't require that.

Care to link to the tool? These types of forums are aimed at helping people correct?

 

[Smith83]

And to be honest, if the log is full of junk, I personally run JRT, AdwCleaner, Malwarebytes, etc. first to cut it down, and grab a new set after.

Yea, but it could be used from the start, then request new FRST logs and go from there. It does find a lot of entries with missing files and attention... It could save you time that is for sure.

Plus, I am going to put this online in some malware removal guides so the average person has access to something that can potentially help them.

 

[Smith83]

@TwinHeadedEagle Since you have a similar tool, perhaps you can contact the maker of ALA. Combine heads... Get a better program by merging the two. Since the aim is to help people fight against malware.

 

[Aura]

I already worked with logs that required me to create a huge fixlist. I don't particuliary mind, since most entries are back-to-back so you can select them all easily and copy them in your fixlist. It's more of a problem if these lines are separated somehow (but that rarely happens).