Critical Updates

  • Thread starter Thread starter AliceZ
  • Start date Start date
A

AliceZ

I just downloaded several Critical Updates for my WinXP (sp3) and when I
looked at the log I noticed a new line was included.

In the past it read:

Microsoft Windows Malicious Software Removal Tool v2.8, March 2009
Started On Wed Mar 11 12:15:32 2009
Results Summary:
----------------
No infection found.
Return code: 0
Microsoft Windows Malicious Software Removal Tool Finished On Wed Mar 11
12:17:03 2009

The new log reads:
Microsoft Windows Malicious Software Removal Tool v2.9, April 2009
Started On Tue Apr 14 17:38:23 2009
Security policy adjusted. Engine requests reboot and try again, ignoring.
Results Summary:
----------------
No infection found.

Return code: 0
Microsoft Windows Malicious Software Removal Tool Finished On Tue Apr 14
17:39:47 2009

Does the new line -

"Security policy adjusted. Engine requests reboot and try again, ignoring."

- mean anything? Or is it just something new that will continue to show in
the logs?
I noticed it on two of my computer's Malicious logs (re KB890830).

thanks, Alice
 
AliceZ said:
I just downloaded several Critical Updates for my WinXP (sp3) and
when I looked at the log I noticed a new line was included.

In the past it read:

Microsoft Windows Malicious Software Removal Tool v2.8, March 2009
Started On Wed Mar 11 12:15:32 2009
Results Summary:
----------------
No infection found.
Return code: 0
Microsoft Windows Malicious Software Removal Tool Finished On Wed Mar
11 12:17:03 2009

The new log reads:
Microsoft Windows Malicious Software Removal Tool v2.9, April 2009
Started On Tue Apr 14 17:38:23 2009
Security policy adjusted. Engine requests reboot and try again,
ignoring. Results Summary:
----------------
No infection found.

Return code: 0
Microsoft Windows Malicious Software Removal Tool Finished On Tue Apr
14 17:39:47 2009

Does the new line -

"Security policy adjusted. Engine requests reboot and try again,
ignoring."

- mean anything? Or is it just something new that will continue to
show in the logs?
I noticed it on two of my computer's Malicious logs (re KB890830).

thanks, Alice
Click to expand...

AFAIK this is nothing to worry about. But you could try posting in
m.p.security or m.p.windowsupdate if you're very concerned, to see whether
they have any clues.
 
Back
Top