Re: Windows 2000 SP4 Update Rollup "Sticking"
- From: "Robert Aldwinckle" <robald@xxxxxxxxxxxxx>
- Date: Sat, 30 Jul 2005 22:45:39 -0400
"Dave Hawley" <DaveHawley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9581723C-9146-4B40-A2AD-29F15B077752@xxxxxxxxxxxxxxxx
> Thanks Robert.
> I have sent you an e-mail with the logs attatched.
Dave,
Since the uninstall-reinstall idea didn't work my guess is that there
was something wrong before the Rollup was first installed.
To check that out I tried to look at version information from your first
uninstall. Unfortunately we only get partial details from that log.
E.g. here is a summary of its layout:
1. a bunch of deletes of cached copies of modules.
No problem there I suppose that we don't see any version info.
2. a few deletes of supposedly operational files
3. a bunch of copies of supposedly operational files
but it's not clear what the source is; probably the the backup folder
the spuninst.exe program is being run from:
D:\WIN-NT\$NtUpdateRollupPackUninstall$
<example>
....
13.031: Deleted file: D:\WIN-NT\system32\dllcache\write32.wpc
13.031: Deleted file: D:\WIN-NT\system32\drivers\fltmgr.sys
13.031: Deleted file: D:\WIN-NT\system32\windows media\server\nscm.exe
13.031: Deleted file: D:\WIN-NT\system32\windows media\server\nsiislog.dll
13.031: Deleted file: D:\WIN-NT\system32\windows media\server\nsisapi.exe
13.047: Deleted file: D:\WIN-NT\system32\windows media\server\nspmon.exe
13.141: Copied file: D:\WIN-NT\system32\advapi32.dll
....
</example>
Some of the copies are explicitly "delayed" (i.e., pending reboot)
but there are more which involve .tmp names so I suspect that
some of the other operations which were expected to succeed
(e.g., either as deletions or as copy steps) failed and therefore
were dynamically given the same treatment. Unfortunately there
is no real proof of this. Worse, some of the ones which I suppose
were originally deletions have no more identification when they are
processed after the boot than their version numbers:
<example>
---- PendingFileRenameOperations After Uninstallation ------
70.766:
Source: D:\WIN-NT\system32\_000000_.tmp.dll
Version: 5.0.2195.7038
70.766:
Destination:
Version:
</example>
The copy steps at least are fully identified but as you say there are
a lot of them and there is no easy way of tying them to any particular
manifest to validate their regression. And what if some aren't regressions?
That might be what the installer was getting confused about and in that
case perhaps we could uninstall something, such as one of the updates
which the Rollup was supposed to be supplementing in order for the
Rollup to update to the version that it wants, so then the installer isn't
confused any more. Etc. (Who knows?)
Did you manually enter the spuninst.exe command or was there some
UI which did it for you? If you can enter the command manually there
are apparently some extra switches you could use which would force more
detailed diagnostics (e.g. hopefully some indication of why a copy or
delete is being done as well as more explicitly relating the .tmp files
to the modules being processed and the final version they should have.
In any case the option I think we want is /verbose as described in here:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/deployment/winupdte.mspx
HTH
Robert
---
.
- Follow-Ups:
- Re: Windows 2000 SP4 Update Rollup "Sticking"
- From: Dave Hawley
- Re: Windows 2000 SP4 Update Rollup "Sticking"
- Prev by Date: Re: Error using windows update
- Next by Date: Can not install update KB883939 cumulative sec. update for IE SP1
- Previous by thread: Re: Updat Fail
- Next by thread: Re: Windows 2000 SP4 Update Rollup "Sticking"
- Index(es):
Relevant Pages
|
