Pending Login

(imported topic written by Ashwin.D91)

Hi,

I have created a baseline of a few MS patches and pushed it down. I noticed two behaviours:

  1. A few patches install, the status is pending restart and for the rest, the status is waiting. It proceeds only if I restart the machine.

  2. The status of the machine shows up as “Pending Login” and the action summary of the baseline says “Waiting for user to log in”. However, all the patches are in either “Fixed”, “Pending Restart”, “Not Relevant” or “Waiting” status.

Any idea what could be causing this?

Thanks

Ashwin

(imported comment written by BenKus)

If one of the Fixlets has the line “action requires login”, then this will happen… As far as I know, only the “Real Player 11” and some of the MS09-010 Fixlets have this behavior at the moment.

Ben

(imported comment written by Ashwin.D91)

Ben Kus

If one of the Fixlets has the line “action requires login”, then this will happen… As far as I know, only the “Real Player 11” and some of the MS09-010 Fixlets have this behavior at the moment.

Ben

Thanks for the reply. How about case 1?

(imported comment written by BenKus)

Do you have “corrupt patch Fixlets” in your baseline? Also, what options did you select in the Take-Action-Dialog.

Ben

(imported comment written by Ashwin.D91)

Nope. No corrupt patches. It is all standard windows patches. Also, the action settings were left at default.

Its just that a few patches install, their status is either pending restart or fixed and the rest are in the status ‘waiting’. No idea whats causing it. I have about 32 patches in the baseline.

Ashwin

(imported comment written by Ashwin.D91)

Also, may I know why MS09-010 patches require login? Is it stated in the Microsoft KB article because I couldn’t find the reason anywhere.

Thanks

Ashwin

(imported comment written by BenKus)

The Fixlet description talks about the need for the login.

Ben

(imported comment written by Ashwin.D91)

Hi Ben,

Yes, the fixlet does, but is there any documentation from Microsoft that supports this? What exactly is causing the administrator logon?

Thanks

Ashwin

(imported comment written by BenKus)

I think it is because the patch puts something in the RunOnce key, which is run at login time. As far as I know, this is something we noticed and Microsoft doesn’t directly explain it.

Ben