Re: KB837009.. same Windows Update every day!!!

From: Noel Paton (NoelDPspamless_at_btopenworld.com)
Date: 01/23/05


Date: Sun, 23 Jan 2005 01:12:11 -0000

In a fully updated VM of ME I see the following entries in A/R programs
IE (Q880203)
.NET Framework 1.1
MDAC KB 870669
IE6SP1 & Internet Tools
OE6
MS VGX Q833989
OE Q887797
Windows ME Q823559 Update
(and that's all from MS - after a clean install, updating with the CD, and
then patching from Windows Update))

It's now 1:11 in the a.m. and I can't see straight<g> - I'll attempt a
response in the morning.

-- 
Noel Paton (MS-MVP 2002-2005, Windows)
Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj
Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
"Robert Aldwinckle" <robald@techemail.com> wrote in message 
news:O6PxQLOAFHA.3836@tk2msftngp13.phx.gbl...
> "Noel Paton" <NoelDPspamless@btopenworld.com> wrote in message
> news:uHy8AiLAFHA.2676@TK2MSFTNGP12.phx.gbl...
>> The Security CD is simply a collection of WIndowsUpdates - no more and no
>> less.
>> The wrapper on the CD forces the install of ALL the available updates on 
>> the
>> CD, in their proper order.
>
> So then wouldn't we expect Joann to see them in Add/Remove Programs?
>
> Any idea *which* of those updates installed that  6.00.2800.1478?
> Perhaps there is one which I am not aware of which *can* be uninstalled
> and reinstalled.
>
> E.g.  is there an equivalent  WinME  version of  887797?
> What module versions does it involve?
>
> Yes!   I had forgotten that I had my  XPsp1  partition updated.
> I have  887797  on it and  6.00.2800.1478  is the new version
> that it installs.
>
> Why the heck don't they include module version in the logs?
> And why isn't there better documentation of that update period?
>
>
> Now, getting back to Joann and her  WinME.
> She says she can't see any  OE  entries in  Add/Remove Programs.
> Is that expected or not?  Actually I didn't explicitly ask her to check
> for  887797.   Since that supersedes both 837009 and 823353
> I imagine it might make those two to disappear from that list?
> Also, in XP the user has to check a box in A/RP labeled  Show Updates.
> Is there by any chance a similar box that  WinME  users have to check?
> If so I would be hopeful that to fix the regressed module what she might
> do is check that box and then look for   887797,  then uninstall
> and reinstall that update.
>
>
> If as you suggest all cumulative updates were installed by the Security
> Update CD then uninstalling  887797 would probably restore the
> versions from 823353.   Do you think it would be necessary also to
> uninstall  823353 which in turn presumably would revert to 837009?
> And what about that one?  The only reason for doing anything more
> than uninstalling and reinstalling  887797 would be to try to make WU 
> behave.
> It would be interesting to see what  WU would do if she backed out to 
> 837009
> and could see it listed there in her A/RP.
>
>
> Since the version of  msident.dll is common to all three updates
> I suspect that simply uninstalling  887797  could fix that  problem,
> although we don't know at which point that regression occurred.
> Thinking about it some more the most likely reason that I can
> see for the regression to have occurred would be that the copy
> failed when  837009  was done; so most likely no fix to it would occur
> simply as a result of doing an uninstall.   She would have to do
> at least one reinstall to replace that module.
>
>
>>
>> MS considered (in their infinite wisdom and supposedly better knowledge)
>> that this was a better thing than allowing the user to duck out of some
>> upgrades (WMP9 and others) and discounted evidence that some older 
>> machines
>> couldn't run the upgraded apps.
>>
>> As a matter of routine in all systems that I come into contact with, I 
>> run
>> Belarc Advisor, to assess the state of the Hotfixes/patches - anything 
>> that
>> shows as barfed in that definitely needs a re-install, and anything where 
>> it
>> shows as 'could not be verified', needs further investigation of the type
>> that I see you've already done with Joann's system,
>>
>> Should forcing the patch to install cause problems, then it's a fairly
>> simple matter to force a reinstall of the subsequent patches. (Belarc 
>> gives
>> links to the MSKB articles involved)
>
>
> I would now agree to a   /N:V  install but for  887797
> The idea would be to fix the  msident.dll  problem
> and ensure that an update which supersedes  837009
> is clearly and correctly in place.   If  837009 continues
> to be offered after that I would conclude that there is
> a bug in the  WU  database (at least for  WinME).
>
>
> Thanks for your help, Noel.
>
>
> Robert
> --- 
>
> 


Relevant Pages

  • Re: Missing Hyperlinks
    ... We have installed the latest update and it does not fix the problem. ... We cannot uninstall and install the original because we use Entourage ... We are on version 11.2.4 for Powerpoint. ...
    (microsoft.public.mac.office.powerpoint)
  • RE: Problem re-installing Office 2000 - Word
    ... Here I got a fix for you that should work. ... Uninstall Office 2000. ... It is the same disk I used to install office prior ... >> CD are you trying to use: retail full, retail upgrade, or OEM? ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: MS Office 2003 on XP
    ... not reinstall. ... Dell said if I did that it would ... I uninstall it then try to install it again with the disc I have it will ...
    (microsoft.public.office.setup)
  • Re: MS Office 2003 on XP
    ... not reinstall. ... Dell said if I did that it would ... I uninstall it then try to install it again with the disc I have it will ...
    (microsoft.public.office.setup)
  • Re: MS Office 2003 on XP
    ... not reinstall. ... Dell said if I did that it would ... I uninstall it then try to install it again with the disc I have it will ...
    (microsoft.public.office.setup)

Loading