Event Log

G

Guest

I was pointed in that direction by a reply to my previous
posting,(Confirmation of Scan on 24th) but he did not tell me how to find it!
As far as Defender's Help is concerned it does not exist!
 
G

Guest

OR, alternatively: Start>control panel>Performance and
Maintenance>ADministrative Tools>event viewer>system. I had never looked in
there before I installed Defender. Very interesting. If you see WinDefend,
you can right click on the entry to see more information. If there are
errors visible, you can click on a link within the info box and Windows
Explorer will connect with the Mircrosoft knowledge base if you are connected
to the Internet. It does not explain everything, but I have learned some
interesting information by investigating error entries.
 
G

Guest

zygy:

Try searching for "reportingevents.log"
In my sys, it's in C:\Windows\Software Distribution\ . Opens with Notepad.
Scroll down near the bottom to see recent updates. I don't know if it logs
scans by WD.
My WD consistently fails to report auto-scans at the scheduled time. Once
in a while it does a wild, unscheduled scan. Those it reports in Status. I
suspect that the wild ones are the only full scans it ever does.
 
G

Guest

I guess we each should have said which OS we are using. I'm using WindowsXP
SP2, Home Edition, English version. Defender is consistently running all its
scheduled scans on time and they are reported in the system log. I have only
scheduled quick scans since I learned how long a full scan would take. I try
to do a full scan on demand about once a week minimum. No problem there
either. I don,t schedule scans for night or offtime, because I use dial up
and the PC is usually shut down if I am not present and using it. Apparently,
there are differences from system to system. Actually, I feel that I have
been lucky once I got a good install on the 3rd try.
 
G

Guest

You: XP Home, SP2, English. Me: ditto. Apparently there are not only
differences from OS to OS but differences within OS from machine to machine
and user to user. Maybe that's what makes life interesting, but I'm sick of
living in interesting times, so I have abandoned WD until it comes off of
Beta. Glad yours is working, and hope it keeps on giving you good service.

I don't know how one is supposed to bow out of a thread like this one. Let
me just say I'm outa here, and no reply expected. Best to all. JVL
 
E

Eric Cross

Yes, Windows Defender logs and are reported under the System in the Event
Viewer by default. This is what I have done and created a new log view which
filters them from rest of the other system events. This way when you open
the Event Viewer all you have to click on is Windows Defender and you can
view all of the logs from one Event Source.

1. Click Start, click Run, type eventvwr.msc, and then click Ok.
2. Right-click System and choose "New Log View".
3. Right-click "System (2)", and then choose Properties.
4. Click the Filters tab.
5. Choose "WinDefend" from the Event Source drop down box.
6. Then click Apply and Ok.
7. Rename "System (2)" to "Windows Defender".
 
E

Eric Cross

Actually that didn't work. :(


Eric Cross said:
Yes, Windows Defender logs and are reported under the System in the Event
Viewer by default. This is what I have done and created a new log view
which filters them from rest of the other system events. This way when you
open the Event Viewer all you have to click on is Windows Defender and you
can view all of the logs from one Event Source.

1. Click Start, click Run, type eventvwr.msc, and then click Ok.
2. Right-click System and choose "New Log View".
3. Right-click "System (2)", and then choose Properties.
4. Click the Filters tab.
5. Choose "WinDefend" from the Event Source drop down box.
6. Then click Apply and Ok.
7. Rename "System (2)" to "Windows Defender".
Click to expand...
 
B

Bill Sanderson

Interesting idea, though--hadn't thought of creating a permanent alternate
view--there must be a way!

--
 
B

Bill Sanderson

Got it!--thanks, that was something I've always wanted to know how to do:

Start, Run
eventvwr.msc /a

Now make the desired changes
Then save it at the end.

Doesn't make it available in My Computer Management--but when you do start,
run Eventvwr, there's the new view.


--
 
B

Bill Sanderson

Well maybe that was too much of a shortcut:

mmc eventvwr.msc /a

Switch to author mode
make the changes
switch back to limited mode and save the file.

I suspect this does not work on XP Home--don't know about Windows 2000.

--
 
E

Eric Cross

Yes, I just tried it. It works on Windows 2000. Windows XP Home does have
the Event Viewer and I think it will work too.
 
B

Bill Sanderson

I suspect it may not have the MMC piece, though. However, modifying the
..MSC on another machine and moving it to the XP Home one should work,
although it may take some effort to get permissions correct.

I need to get XP Home working in a VPC so I can test this kind of stuff.

--
 
E

Eric Cross

I just talked to a friend who is running XP Home.

Yes, MMC is in XP Home too. Therefore it should work the same as XP Pro.
 
B

Bill Sanderson

Great- thanks!

--

Eric Cross said:
I just talked to a friend who is running XP Home.

Yes, MMC is in XP Home too. Therefore it should work the same as XP Pro.
Click to expand...
 
G

Guest

This is all very interesting, and I don't mind using the Event Viewer to find
out what's happening with Defender, BUT why doesn't Microsoft put an easily
accessible log viewer within Defender itself. That would help with a lot of
the current confusion.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Please Help! Virus? Avast, Firefox, Windows update quit working 4
Is Defender 'growing up'? 2
Amazon Login Location Different 4
scheduled scans 4
Windows defender versus client protection 4
Email Bounce Error 3
Windows Defender scheduling woes - Vista Home Premium 1
Real-time protection 3003 error 4

Top