I've read that this is located in the windows\debug\ dir. I have
searched for the file name in my entire drive and it's not there.
I've been running MRT for a long time now, in its monthly updates. The
MRT.exe file is located in its proper place. So as it stands the
thing runs and I can't find out whether it found bad stuff or not.
Can someone please tell me how to get to that log file. Thanks.

On this system, the log file is \windows\debug\mrt.log.
Jim
<(E-Mail Removed)> wrote in message
news:7b47fa93-576e-4a85-9d8b-(E-Mail Removed)...
> I've read that this is located in the windows\debug\ dir. I have
> searched for the file name in my entire drive and it's not there.
> I've been running MRT for a long time now, in its monthly updates. The
> MRT.exe file is located in its proper place. So as it stands the
> thing runs and I can't find out whether it found bad stuff or not.
> Can someone please tell me how to get to that log file. Thanks.

<(E-Mail Removed)> said this in news item
news:7b47fa93-576e-4a85-9d8b-(E-Mail Removed)...
> I've read that this is located in the windows\debug\ dir. I have
> searched for the file name in my entire drive and it's not there.
> I've been running MRT for a long time now, in its monthly updates. The
> MRT.exe file is located in its proper place. So as it stands the
> thing runs and I can't find out whether it found bad stuff or not.
> Can someone please tell me how to get to that log file. Thanks.

Perhaps the file is hidden on your machine. What happens when you attempt to
create a *folder* called c:\Windows\debug\mrt.log?

On Jan 7, 11:11*am, "Jim" <j...@invalid.invalid> wrote:
> On this system, the log file is \windows\debug\mrt.log.
> Jim<programmernov...@yahoo.com> wrote in message
>
> news:7b47fa93-576e-4a85-9d8b-(E-Mail Removed)...
>
>
>
> > I've read that this is located in the windows\debug\ dir. *I have
> > searched for the file name in my entire drive and it's not there.
> > I've been running MRT for a long time now, in its monthly updates. The
> > MRT.exe file is located in its proper place. *So as it stands the
> > thing runs and I can't find out whether it found bad stuff or not.
> > Can someone please tell me how to get to that log file. *Thanks.- Hide quoted text -
>
> - Show quoted text -

Thanks for your response. The directory is there, but not the log
file. If I create one, will MRT.exe then use it so it can be
checked? Thanks again.

Why do you ask?

(E-Mail Removed) wrote:
> I've read that this is located in the windows\debug\ dir. I have
> searched for the file name in my entire drive and it's not there.
> I've been running MRT for a long time now, in its monthly updates. The
> MRT.exe file is located in its proper place. So as it stands the
> thing runs and I can't find out whether it found bad stuff or not.
> Can someone please tell me how to get to that log file. Thanks.

Sorry, I don't know the answer. The documentation for this tool seems
sparse to say the least.

However, a permission problem could prevent writing to the log file.

Jim
<(E-Mail Removed)> wrote in message
news:34f9308a-d547-4feb-83f9-(E-Mail Removed)...
On Jan 7, 11:11 am, "Jim" <j...@invalid.invalid> wrote:
> On this system, the log file is \windows\debug\mrt.log.
> Jim<programmernov...@yahoo.com> wrote in message
>
> news:7b47fa93-576e-4a85-9d8b-(E-Mail Removed)...
>
>
>
> > I've read that this is located in the windows\debug\ dir. I have
> > searched for the file name in my entire drive and it's not there.
> > I've been running MRT for a long time now, in its monthly updates. The
> > MRT.exe file is located in its proper place. So as it stands the
> > thing runs and I can't find out whether it found bad stuff or not.
> > Can someone please tell me how to get to that log file. Thanks.- Hide
> > quoted text -
>
> - Show quoted text -

Thanks for your response. The directory is there, but not the log
file. If I create one, will MRT.exe then use it so it can be
checked? Thanks again.

On 7 jan, 13:17, "Jim" <j...@invalid.invalid> wrote:
> Sorry, I don't know the answer. *The documentation for this tool seems
> sparse to say the least.
>
> However, a permission problem could prevent writing to the log file.
>

OK many thanks to you and everyone who posted.

On Jan 8, 10:21*am, "programmernov...@yahoo.com"
<programmernov...@yahoo.com> wrote:
> On 7 jan, 13:17, "Jim" <j...@invalid.invalid> wrote:
>
> > Sorry, I don't know the answer. *The documentation for this tool seems
> > sparse to say the least.
>
> > However, a permission problem could prevent writing to the log file.
>
> OK many thanks to you and everyone who posted.

Have you checked in the Event Log for any helpful messages?

Are you running MRT from Start, Run?

Does Start, Run, mrt.exe seem to start and run okay?

If you browse to the Debug folder are you able to create a new file
out there called mrt.log?

Perform some scans for malicious software, then fix any remaining
issues:

Download, install, update and do a full scan with these free malware
detection programs:

Malwarebytes (MBAM): http://malwarebytes.org/
SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

They can be uninstalled later if desired.

<(E-Mail Removed)> said this in news item
news:f0d7a0e0-a8ba-4c9b-acc1-(E-Mail Removed)...
> On 7 jan, 13:17, "Jim" <j...@invalid.invalid> wrote:
>> Sorry, I don't know the answer. The documentation for this tool seems
>> sparse to say the least.
>>
>> However, a permission problem could prevent writing to the log file.
>>
>
> OK many thanks to you and everyone who posted.

Would you care to post your solution, for the benefit of other posters who
experience the same problem?