MS07-023 Vista, Excel 2007 FAILED but no longer detected?

Hi,

Something very odd with the Excel 2007 patch MS07-023 when installing on
Vista using Microsoft Update and WUA client 3.0.

I ran a scan of the machine and it downloaded and installed about 15
updates, including some for Office 2007. After a reboot, MU said everything
was "up to date" and no patches were shows as missing. However, I then
checked the machine with Shavlik, and it said MS07-023 was missing (!), all
other updates had worked.

The scary part is that (at this point) MU was NOT showing the patch as
missing, which is a security risk.

I looked at the MU history, and the patch was nowhere to be seen.

I looked in the SoftwareDistribution folder, and was amazed to see the patch
had been downloaded.

I looked in the WindowsUpdate.log file and it showed an attempt to install
the patch, but failed with 0x80240017.

I extracted the MSP from the CAB file in SoftwareDistribution and it
installed perfectly and now Shavlik says it's fine.

My question is, *if* the patch had FAILED to install under MU, why was it no
longer detected as missing by the MU scanning technology?

--
Gerry Hickman - (London UK)

(cross-post added to Office Update)
"Gerry Hickman" <> wrote in message
news:Ohylj$...
> Hi,
>
> Something very odd with the Excel 2007 patch MS07-023 when installing on
> Vista using Microsoft Update and WUA client 3.0.
>
> I ran a scan of the machine and it downloaded and installed about 15
> updates, including some for Office 2007. After a reboot, MU said everything
> was "up to date" and no patches were shows as missing. However, I then
> checked the machine with Shavlik, and it said MS07-023 was missing (!), all
> other updates had worked.
>
> The scary part is that (at this point) MU was NOT showing the patch as
> missing, which is a security risk.
>
> I looked at the MU history, and the patch was nowhere to be seen.
>
> I looked in the SoftwareDistribution folder, and was amazed to see the patch
> had been downloaded.
>
> I looked in the WindowsUpdate.log file and it showed an attempt to install
> the patch, but failed with 0x80240017.


http://technet2.microsoft.com/window....mspx?mfr=true

<quote>
0x80240017 WU_E_NOT_APPLICABLE
Install is not needed because no updates are applicable.
</quote>


>
> I extracted the MSP from the CAB file in SoftwareDistribution and it
> installed perfectly and now Shavlik says it's fine.
>
> My question is, *if* the patch had FAILED to install under MU, why was it no
> longer detected as missing by the MU scanning technology?


Time for verbose logging? <eg>

http://support.microsoft.com/kb/902093

However, since I usually find that not terribly informative
I would also run ProcMon at the same time...


Hopefully Office newsgroup readers may be more aware of this discrepancy
(cross-post added to Office Update).


Good luck

Robert Aldwinckle
---

Hi Robert,

>> I looked in the WindowsUpdate.log file and it showed an attempt to install
>> the patch, but failed with 0x80240017.

> 0x80240017 WU_E_NOT_APPLICABLE

Yup, but MS07-023 _is_ "applicable" to Excel 2007! Plus when I ran the
patch from the cache, it worked! I tested last night on a second Vista
computer running WUA 3.0 and Office 2007 and got the same problem, BUT
MU insists no patches are missing.

My Excel.exe binary say it's version 12.0.4518.1014 and the article
MS07-023 says the version should be 12.00.6014.5000

Bear in mind also, that the whole design of MU is that you can't
download something that's not "applicable" even if you wanted to - it
only scans for patches you can apply to the system you are scanning.

> Time for verbose logging? <eg>
>
> http://support.microsoft.com/kb/902093

Could be, but I'm getting fed up with these constant Microsoft Update
and WGA/OGA problems. They released WUA 2.0 as part of Vista without
testing it properly, getting a token from session 0 fails on Vista,
that's a really basic flaw, but Microsoft released it anyway. Now
they've released WUA 3.0 without testing it properly. This is just ONE
issue of many. They are basically releasing unfinished experimental
software and using their paying customers as guinea pigs.

> Hopefully Office newsgroup readers may be more aware of this discrepancy
> (cross-post added to Office Update).

Great idea, I should have done that first, as it's very much Office related.

--
Gerry Hickman (London UK)

Hi,
There was an issue with the detection logic for these updates that caused
problems only on vista and the updates have been re-released today with the
corrected logic.
The updates should be re-offered to the computers that don't have them
installed.

Please see
http://support.microsoft.com/kb/934233
and
http://support.microsoft.com/kb/934873
for more information

From the KB article
"
Known issues
If you used Microsoft Update or Microsoft Windows Server Update Services
(WSUS) to install this security update on a computer that is running Windows
Vista together with Microsoft Office 2007, the security update may not have
been offered or the security update may not have been installed
successfully.

Microsoft has revised the Microsoft Update detection logic to address this
issue.

Important No changes have been made to the security updates. Therefore, if
you have already installed the security update, you do not have to reinstall
the security update.

If you use Microsoft Systems Management Server together with Inventory Tool
for Microsoft Updates to deploy updates to client computers of if you use
WSUS to deploy updates to client computers, you may experience the following
symptoms:. You must reapprove the security updates.
.. Users for whom the security update installation failed previously are
again prompted to install the security updates.
.. The security updates are offered to users who have not yet installed the
security updates in the typical manner.
Note Customers who have already installed the security update successfully
do not have to take any further action.
"



--
Sudheer GN
Microsoft, WU Client


This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Gerry Hickman" <> wrote in message
news:#...
> Hi Robert,
>
>>> I looked in the WindowsUpdate.log file and it showed an attempt to
>>> install
>>> the patch, but failed with 0x80240017.
>
>> 0x80240017 WU_E_NOT_APPLICABLE
>
> Yup, but MS07-023 _is_ "applicable" to Excel 2007! Plus when I ran the
> patch from the cache, it worked! I tested last night on a second Vista
> computer running WUA 3.0 and Office 2007 and got the same problem, BUT MU
> insists no patches are missing.
>
> My Excel.exe binary say it's version 12.0.4518.1014 and the article
> MS07-023 says the version should be 12.00.6014.5000
>
> Bear in mind also, that the whole design of MU is that you can't download
> something that's not "applicable" even if you wanted to - it only scans
> for patches you can apply to the system you are scanning.
>
>> Time for verbose logging? <eg>
>>
>> http://support.microsoft.com/kb/902093
>
> Could be, but I'm getting fed up with these constant Microsoft Update and
> WGA/OGA problems. They released WUA 2.0 as part of Vista without testing
> it properly, getting a token from session 0 fails on Vista, that's a
> really basic flaw, but Microsoft released it anyway. Now they've released
> WUA 3.0 without testing it properly. This is just ONE issue of many. They
> are basically releasing unfinished experimental software and using their
> paying customers as guinea pigs.
>
>> Hopefully Office newsgroup readers may be more aware of this discrepancy
>> (cross-post added to Office Update).
>
> Great idea, I should have done that first, as it's very much Office
> related.
>
> --
> Gerry Hickman (London UK)

Hi,
Also, please see
http://blogs.technet.com/msrc/archiv...7-updates.aspx

We apologize for the trouble.


--
Sudheer GN
Microsoft, WU Client


This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Sudheer GN [MSFT]" <> wrote in message
news:...
> Hi,
> There was an issue with the detection logic for these updates that caused
> problems only on vista and the updates have been re-released today with
> the corrected logic.
> The updates should be re-offered to the computers that don't have them
> installed.
>
> Please see
> http://support.microsoft.com/kb/934233
> and
> http://support.microsoft.com/kb/934873
> for more information
>
> From the KB article
> "
> Known issues
> If you used Microsoft Update or Microsoft Windows Server Update Services
> (WSUS) to install this security update on a computer that is running
> Windows Vista together with Microsoft Office 2007, the security update may
> not have been offered or the security update may not have been installed
> successfully.
>
> Microsoft has revised the Microsoft Update detection logic to address this
> issue.
>
> Important No changes have been made to the security updates. Therefore, if
> you have already installed the security update, you do not have to
> reinstall the security update.
>
> If you use Microsoft Systems Management Server together with Inventory
> Tool for Microsoft Updates to deploy updates to client computers of if you
> use WSUS to deploy updates to client computers, you may experience the
> following symptoms:. You must reapprove the security updates.
> . Users for whom the security update installation failed previously are
> again prompted to install the security updates.
> . The security updates are offered to users who have not yet installed the
> security updates in the typical manner.
> Note Customers who have already installed the security update successfully
> do not have to take any further action.
> "
>
>
>
> --
> Sudheer GN
> Microsoft, WU Client
>
>
> This posting is provided "As Is" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
> "Gerry Hickman" <> wrote in message
> news:#...
>> Hi Robert,
>>
>>>> I looked in the WindowsUpdate.log file and it showed an attempt to
>>>> install
>>>> the patch, but failed with 0x80240017.
>>
>>> 0x80240017 WU_E_NOT_APPLICABLE
>>
>> Yup, but MS07-023 _is_ "applicable" to Excel 2007! Plus when I ran the
>> patch from the cache, it worked! I tested last night on a second Vista
>> computer running WUA 3.0 and Office 2007 and got the same problem, BUT MU
>> insists no patches are missing.
>>
>> My Excel.exe binary say it's version 12.0.4518.1014 and the article
>> MS07-023 says the version should be 12.00.6014.5000
>>
>> Bear in mind also, that the whole design of MU is that you can't download
>> something that's not "applicable" even if you wanted to - it only scans
>> for patches you can apply to the system you are scanning.
>>
>>> Time for verbose logging? <eg>
>>>
>>> http://support.microsoft.com/kb/902093
>>
>> Could be, but I'm getting fed up with these constant Microsoft Update and
>> WGA/OGA problems. They released WUA 2.0 as part of Vista without testing
>> it properly, getting a token from session 0 fails on Vista, that's a
>> really basic flaw, but Microsoft released it anyway. Now they've released
>> WUA 3.0 without testing it properly. This is just ONE issue of many. They
>> are basically releasing unfinished experimental software and using their
>> paying customers as guinea pigs.
>>
>>> Hopefully Office newsgroup readers may be more aware of this
>>> discrepancy
>>> (cross-post added to Office Update).
>>
>> Great idea, I should have done that first, as it's very much Office
>> related.
>>
>> --
>> Gerry Hickman (London UK)
>

Hi Sudheer,

Thank you for this confirmation and information!

--
Gerry Hickman - (London UK)

"Sudheer GN [MSFT]" <> wrote in message
news:%...
> Hi,
> Also, please see
>
http://blogs.technet.com/msrc/archiv...7-updates.aspx
>
> We apologize for the trouble.
>
>
> --
> Sudheer GN
> Microsoft, WU Client
>
>
> This posting is provided "As Is" with no warranties, and confers no
rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
> "Sudheer GN [MSFT]" <> wrote in message
> news:...
> > Hi,
> > There was an issue with the detection logic for these updates that
caused
> > problems only on vista and the updates have been re-released today with
> > the corrected logic.
> > The updates should be re-offered to the computers that don't have them
> > installed.
> >
> > Please see
> > http://support.microsoft.com/kb/934233
> > and
> > http://support.microsoft.com/kb/934873
> > for more information
> >
> > From the KB article
> > "
> > Known issues
> > If you used Microsoft Update or Microsoft Windows Server Update Services
> > (WSUS) to install this security update on a computer that is running
> > Windows Vista together with Microsoft Office 2007, the security update
may
> > not have been offered or the security update may not have been installed
> > successfully.
> >
> > Microsoft has revised the Microsoft Update detection logic to address
this
> > issue.
> >
> > Important No changes have been made to the security updates. Therefore,
if
> > you have already installed the security update, you do not have to
> > reinstall the security update.
> >
> > If you use Microsoft Systems Management Server together with Inventory
> > Tool for Microsoft Updates to deploy updates to client computers of if
you
> > use WSUS to deploy updates to client computers, you may experience the
> > following symptoms:. You must reapprove the security updates.
> > . Users for whom the security update installation failed previously are
> > again prompted to install the security updates.
> > . The security updates are offered to users who have not yet installed
the
> > security updates in the typical manner.
> > Note Customers who have already installed the security update
successfully
> > do not have to take any further action.
> > "
> >
> >
> >
> > --
> > Sudheer GN
> > Microsoft, WU Client
> >
> >
> > This posting is provided "As Is" with no warranties, and confers no
> > rights.
> > Use of included script samples are subject to the terms specified at
> > http://www.microsoft.com/info/cpyright.htm
> >
> > "Gerry Hickman" <> wrote in message
> > news:#...
> >> Hi Robert,
> >>
> >>>> I looked in the WindowsUpdate.log file and it showed an attempt to
> >>>> install
> >>>> the patch, but failed with 0x80240017.
> >>
> >>> 0x80240017 WU_E_NOT_APPLICABLE
> >>
> >> Yup, but MS07-023 _is_ "applicable" to Excel 2007! Plus when I ran the
> >> patch from the cache, it worked! I tested last night on a second Vista
> >> computer running WUA 3.0 and Office 2007 and got the same problem, BUT
MU
> >> insists no patches are missing.
> >>
> >> My Excel.exe binary say it's version 12.0.4518.1014 and the article
> >> MS07-023 says the version should be 12.00.6014.5000
> >>
> >> Bear in mind also, that the whole design of MU is that you can't
download
> >> something that's not "applicable" even if you wanted to - it only scans
> >> for patches you can apply to the system you are scanning.
> >>
> >>> Time for verbose logging? <eg>
> >>>
> >>> http://support.microsoft.com/kb/902093
> >>
> >> Could be, but I'm getting fed up with these constant Microsoft Update
and
> >> WGA/OGA problems. They released WUA 2.0 as part of Vista without
testing
> >> it properly, getting a token from session 0 fails on Vista, that's a
> >> really basic flaw, but Microsoft released it anyway. Now they've
released
> >> WUA 3.0 without testing it properly. This is just ONE issue of many.
They
> >> are basically releasing unfinished experimental software and using
their
> >> paying customers as guinea pigs.
> >>
> >>> Hopefully Office newsgroup readers may be more aware of this
> >>> discrepancy
> >>> (cross-post added to Office Update).
> >>
> >> Great idea, I should have done that first, as it's very much Office
> >> related.
> >>
> >> --
> >> Gerry Hickman (London UK)
> >