Microsoft Windows Vista Community Forums - Vistaheads
Recommended Download



Welcome to the Microsoft Windows Vista Community Forums - Vistaheads, YOUR Largest Resource for Windows Vista related information.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

Driver Scanner

Critical Updates

microsoft.public.windowsupdate






Speedup My PC
Reply
  #1 (permalink)  
Old 04-15-2009
AliceZ
 

Posts: n/a
Critical Updates
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 my other 3 computer's
Malicious logs (re KB890830). thanks, Alice

(Answer received on MS Community Security Adm forum - FAIK 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.)

Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 04-16-2009
PA Bear [MS MVP]
 

Posts: n/a
Re: Critical Updates
The 14 Apr-09 behavior is normal & expected AFAIK. Dunno if we'll see it
again when the next version of the MSRT is released next month but I suspect
we won't.

PS: The MSRT is not a "ciritical update."
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002

AliceZ wrote:
> 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 my other 3 computer's
> Malicious logs (re KB890830). thanks, Alice
>
> (Answer received on MS Community Security Adm forum - FAIK 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.)


Reply With Quote
  #3 (permalink)  
Old 04-16-2009
AliceZ
 

Posts: n/a
Re: Critical Updates
I'm sorry. I should have mentioned that I was referring to the Update KB
890830 and when I looked in the log for the Malicious Software Removal Tool
(KB890830), I saw that new line = "Security policy adjusted. Engine requests
reboot and try again, ignoring."
I never saw that line before and I wondered if it was something new and I
would continue to see it (and that it wasn't pointing to a 'problem').

===============

"PA Bear [MS MVP]" wrote:

> The 14 Apr-09 behavior is normal & expected AFAIK. Dunno if we'll see it
> again when the next version of the MSRT is released next month but I suspect
> we won't.
>
> PS: The MSRT is not a "ciritical update."
> --
> ~Robear Dyer (PA Bear)
> MS MVP-IE, Mail, Security, Windows Client - since 2002
>
> AliceZ wrote:
> > 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 my other 3 computer's
> > Malicious logs (re KB890830). thanks, Alice
> >
> > (Answer received on MS Community Security Adm forum - FAIK 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.)

>
>

Reply With Quote
  #4 (permalink)  
Old 04-16-2009
PA Bear [MS MVP]
 

Posts: n/a
Re: Critical Updates
Again, yes, it is something new, I've never seen it before either (and my
MRT log goes back to April 2005), and no one knows if we'll see it again
(but I expect we won't).

AliceZ wrote:
> I'm sorry. I should have mentioned that I was referring to the Update KB
> 890830 and when I looked in the log for the Malicious Software Removal
> Tool
> (KB890830), I saw that new line = "Security policy adjusted. Engine
> requests
> reboot and try again, ignoring."
> I never saw that line before and I wondered if it was something new and I
> would continue to see it (and that it wasn't pointing to a 'problem').
>
> "PA Bear [MS MVP]" wrote:
>> The 14 Apr-09 behavior is normal & expected AFAIK. Dunno if we'll see it
>> again when the next version of the MSRT is released next month but I
>> suspect we won't.
>>
>> PS: The MSRT is not a "ciritical update."
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-IE, Mail, Security, Windows Client - since 2002
>>
>> AliceZ wrote:
>>> 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 my other 3 computer's
>>> Malicious logs (re KB890830). thanks, Alice
>>>
>>> (Answer received on MS Community Security Adm forum - FAIK 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.)


Reply With Quote
  #5 (permalink)  
Old 04-27-2009
Drew
 

Posts: n/a
Re: Critical Updates
I noticed the 'Security policy adjusted' message in my April log as well.
And it looks like the account of the user that installed the tool was granted
the 'Debug programs' user right. Is this normal?

"PA Bear [MS MVP]" wrote:

> Again, yes, it is something new, I've never seen it before either (and my
> MRT log goes back to April 2005), and no one knows if we'll see it again
> (but I expect we won't).
>
> AliceZ wrote:
> > I'm sorry. I should have mentioned that I was referring to the Update KB
> > 890830 and when I looked in the log for the Malicious Software Removal
> > Tool
> > (KB890830), I saw that new line = "Security policy adjusted. Engine
> > requests
> > reboot and try again, ignoring."
> > I never saw that line before and I wondered if it was something new and I
> > would continue to see it (and that it wasn't pointing to a 'problem').
> >
> > "PA Bear [MS MVP]" wrote:
> >> The 14 Apr-09 behavior is normal & expected AFAIK. Dunno if we'll see it
> >> again when the next version of the MSRT is released next month but I
> >> suspect we won't.
> >>
> >> PS: The MSRT is not a "ciritical update."
> >> --
> >> ~Robear Dyer (PA Bear)
> >> MS MVP-IE, Mail, Security, Windows Client - since 2002
> >>
> >> AliceZ wrote:
> >>> 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 my other 3 computer's
> >>> Malicious logs (re KB890830). thanks, Alice
> >>>
> >>> (Answer received on MS Community Security Adm forum - FAIK 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.)

>
>

Reply With Quote
  #6 (permalink)  
Old 04-27-2009
PA Bear [MS MVP]
 

Posts: n/a
Re: Critical Updates
Dunno.

Drew wrote:
> I noticed the 'Security policy adjusted' message in my April log as well.
> And it looks like the account of the user that installed the tool was
> granted the 'Debug programs' user right. Is this normal?
>
> "PA Bear [MS MVP]" wrote:
>> Again, yes, it is something new, I've never seen it before either (and my
>> MRT log goes back to April 2005), and no one knows if we'll see it again
>> (but I expect we won't).
>>
>> AliceZ wrote:
>>> I'm sorry. I should have mentioned that I was referring to the Update KB
>>> 890830 and when I looked in the log for the Malicious Software Removal
>>> Tool
>>> (KB890830), I saw that new line = "Security policy adjusted. Engine
>>> requests
>>> reboot and try again, ignoring."
>>> I never saw that line before and I wondered if it was something new and
>>> I
>>> would continue to see it (and that it wasn't pointing to a 'problem').
>>>
>>> "PA Bear [MS MVP]" wrote:
>>>> The 14 Apr-09 behavior is normal & expected AFAIK. Dunno if we'll see
>>>> it
>>>> again when the next version of the MSRT is released next month but I
>>>> suspect we won't.
>>>>
>>>> PS: The MSRT is not a "ciritical update."
>>>> --
>>>> ~Robear Dyer (PA Bear)
>>>> MS MVP-IE, Mail, Security, Windows Client - since 2002
>>>>
>>>> AliceZ wrote:
>>>>> 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 my other 3 computer's
>>>>> Malicious logs (re KB890830). thanks, Alice
>>>>>
>>>>> (Answer received on MS Community Security Adm forum - FAIK 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.)


Reply With Quote
  #7 (permalink)  
Old 04-30-2009
Harry Johnston [MVP]
 

Posts: n/a
Re: Critical Updates
PA Bear [MS MVP] wrote:

> Dunno.


I dunno either, but my educated guess would be yes. It would hardly be
surprising if the MSRT needs to peek into various processes to decide if they're
malicious, and you need the debug programs user right to do so.

Harry.

>
> Drew wrote:
>> I noticed the 'Security policy adjusted' message in my April log as well.
>> And it looks like the account of the user that installed the tool was
>> granted the 'Debug programs' user right. Is this normal?
>>
>> "PA Bear [MS MVP]" wrote:
>>> Again, yes, it is something new, I've never seen it before either
>>> (and my
>>> MRT log goes back to April 2005), and no one knows if we'll see it again
>>> (but I expect we won't).
>>>
>>> AliceZ wrote:
>>>> I'm sorry. I should have mentioned that I was referring to the
>>>> Update KB
>>>> 890830 and when I looked in the log for the Malicious Software Removal
>>>> Tool
>>>> (KB890830), I saw that new line = "Security policy adjusted. Engine
>>>> requests
>>>> reboot and try again, ignoring."
>>>> I never saw that line before and I wondered if it was something new
>>>> and I
>>>> would continue to see it (and that it wasn't pointing to a 'problem').
>>>>
>>>> "PA Bear [MS MVP]" wrote:
>>>>> The 14 Apr-09 behavior is normal & expected AFAIK. Dunno if we'll
>>>>> see it
>>>>> again when the next version of the MSRT is released next month but I
>>>>> suspect we won't.
>>>>>
>>>>> PS: The MSRT is not a "ciritical update."
>>>>> --
>>>>> ~Robear Dyer (PA Bear)
>>>>> MS MVP-IE, Mail, Security, Windows Client - since 2002
>>>>>
>>>>> AliceZ wrote:
>>>>>> 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 my other 3 computer's
>>>>>> Malicious logs (re KB890830). thanks, Alice
>>>>>>
>>>>>> (Answer received on MS Community Security Adm forum - FAIK 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.)

>

Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Critical Updates AliceZ microsoft.public.windows.vista.general 4 12-08-2008 18:39
I can't install critical updates Maslow microsoft.public.windowsupdate 32 11-09-2008 17:37
Critical Updates AliceZ microsoft.public.windows.vista.security 3 05-01-2008 17:46
Help with critical updates pamcgill75 microsoft.public.windowsupdate 2 12-03-2007 02:46
OT Critical Updates Engel microsoft.public.es.windowsvista 0 08-29-2007 03:58




All times are GMT +1. The time now is 09:37.




Driver Scanner - Free Scan Now

Vistaheads.com is part of the Heads Network. See also XPHeads.com , Win7Heads.com and Win8Heads.com.


Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 RC 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120