Windows Update vs. MBSA reports after April 2009 patches

It is about Windows XP Pro SP3
April 2009 patches applied for all MS applications, including those for OS.

After April patching completed the visiting and verifying patch status
using Windows Update Portal results in following findings:
KB955839 day light patch missing
KB952287 MDAC patch missing
KB951978 VBScrip/JScript patch missing

Verifying the current patch status using MBSA results in following findings:
KB955839 as above
KB951847 .NET patch missing

Verifying using Secunia PSI doesn't result in any findings.

Where these discrepancies from?
Especially those between Windows Update and MBSA results?

kakii wrote:
>
> It is about Windows XP Pro SP3
> April 2009 patches applied for all MS applications, including those for OS.
>
> After April patching completed the visiting and verifying patch status
> using Windows Update Portal results in following findings:
> KB955839 day light patch missing
> KB952287 MDAC patch missing
> KB951978 VBScrip/JScript patch missing
>
> Verifying the current patch status using MBSA results in following
> findings:
> KB955839 as above
> KB951847 .NET patch missing
>
> Verifying using Secunia PSI doesn't result in any findings.
>
> Where these discrepancies from?
> Especially those between Windows Update and MBSA results?
Make sure you have flipped to Microsoft update not Windows update.

Riffing on Susan's intuitive post:

Does http://windowsupdate.microsoft.com take you to Windows Update or
Microsoft Update?
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002


kakii wrote:
> It is about Windows XP Pro SP3
> April 2009 patches applied for all MS applications, including those for
> OS.
>
> After April patching completed the visiting and verifying patch status
> using Windows Update Portal results in following findings:
> KB955839 day light patch missing
> KB952287 MDAC patch missing
> KB951978 VBScrip/JScript patch missing
>
> Verifying the current patch status using MBSA results in following
> findings:
> KB955839 as above
> KB951847 .NET patch missing
>
> Verifying using Secunia PSI doesn't result in any findings.
>
> Where these discrepancies from?
> Especially those between Windows Update and MBSA results?

"kakii" <> schrieb:

> It is about Windows XP Pro SP3
> April 2009 patches applied for all MS applications, including those for OS.
>
> After April patching completed the visiting and verifying patch status
> using Windows Update Portal results in following findings:
> KB955839 day light patch missing
> KB952287 MDAC patch missing
> KB951978 VBScrip/JScript patch missing

All three are *optional* updates, with KB955839 beeing pushed as an
important update IIRC.

> Verifying the current patch status using MBSA results in following findings:
> KB955839 as above
> KB951847 .NET patch missing

MBSA has an error detecting KB951847 as a missing security update, even
if .NET Framework 2.0 is *not* installed. MS is aware of the issue (and
the issue, that KB951847 for Windows XP on systems which have only .NET
Framework 2.0 installed results in an allmost 280 MB heavy download).
Both issues regarding KB951847 on/for Windows XP aren't fixed yet, while
they are present since January 27th, the initial release date of KB951847.

Bye,
Freudi

The same results if using Microsoft Update
How can I get rid of the .NET stuff?
No .NET runtime env. installed on this machine.
But mbsa and mu report missing patches for .net.



Susan Bradley wrote:
> kakii wrote:
>>
>> It is about Windows XP Pro SP3
>> April 2009 patches applied for all MS applications, including those
>> for OS.
>>
>> After April patching completed the visiting and verifying patch status
>> using Windows Update Portal results in following findings:
>> KB955839 day light patch missing
>> KB952287 MDAC patch missing
>> KB951978 VBScrip/JScript patch missing
>>
>> Verifying the current patch status using MBSA results in following
>> findings:
>> KB955839 as above
>> KB951847 .NET patch missing
>>
>> Verifying using Secunia PSI doesn't result in any findings.
>>
>> Where these discrepancies from?
>> Especially those between Windows Update and MBSA results?
> Make sure you have flipped to Microsoft update not Windows update.