Re: Update Rollup 1 Win 2000 SP4 not detected after install (KB891
- From: "Robert Aldwinckle" <robald@xxxxxxxxxxxxx>
- Date: Mon, 26 Dec 2005 09:34:35 -0500
"michaelf" <michaelf@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:60E432E7-14EB-410A-8CC7-3EB7F2520A49@xxxxxxxxxxxxx
....
> I installed MBSA 1.2.1 and checked for MSXML, MDAC and other missing
> updates. MBSA 1.2.1 results were that everything is installed properly and no
> missing things were found. I also installed msjet 4.0 newest version.
>
> Scanning again by Windows update says that Update rollup 1 is still missing.
>
> ..well I think, I do the same as other users where the problem still
> persists. I ignore it until the update rollup is released and hope that then
> the update is detected properly by windowsupdate.
That's too bad. The problem is that the tools you have now are less useful
for providing the necessary diagnostics. It used to be that hfnetchk from
the command line could show you discrepancies only in module versions.
Later (in MBSA 1.x) mbsacli -hf -z -v was supposed to substitute
for this functionality (and at one time I thought it did) but no more apparently.
If the new mbsacli -xmlout -catalog alternative (in MBSA 2.0)
is capable of providing even the same information which was once
in mssecure.xml nobody so far has shown us how.
And that would only provide a base for starting a scripting solution which
would be able to list all of the modules involved, their expected versions
and then be able to iterate through that list checking the actual versions
installed, reporting differences, etc.
I think the most disappointing thing is that the provided verbose
options are apparently useless for allowing people to even get
a full list of modules and versions being installed. That at least
would allow sites which have multiple machines to do their own
differencing on the verbose logs from failed and successful
installs and thus allow them to focus on a reduced set of modules
for further analysis.
I think that in the same way that there are separate checkers
for MDAC and MSXML support there should be one for
your OS rollups. The number of changed modules is just too
great to expect anybody to be able to manage that degree of
complexity using manual methods.
Such a checker would still be only a crutch though IMO.
Other OS provide tools for assisting with comprehensive
version management. I don't see why Windows shouldn't too.
>
> Thanks again for your help!
>
> Best regards,
> Michael
You're welcome.
Robert
---
.
- References:
- Re: Update Rollup 1 Win 2000 SP4 not detected after install (KB891861)
- From: Robert Aldwinckle
- Re: Update Rollup 1 Win 2000 SP4 not detected after install (KB891
- From: Robert Aldwinckle
- Re: Update Rollup 1 Win 2000 SP4 not detected after install (KB891861)
- Prev by Date: Re: Problems with Security Update for Microsoft
- Next by Date: Re: Failed Windows/Windows Family Updates
- Previous by thread: Re: Update Rollup 1 Win 2000 SP4 not detected after install (KB891
- Next by thread: Re: Service Pak 2
- Index(es):
Relevant Pages
|