Re: Win2k Critical Update problem

(My interpretation of some assumed typos <w>)

"seamusm" <> wrote in message
news:F5ADF72A-B68F-4DEF-BD83-...
> Hi,
> I am using Win2k Prof V5.0.2195 SP4 Build 2195 and cannot install
> critical updates since Jan when KBB 91711, 41533 and 40987 first arrived.

KB891711 KB841533 and KB840987 you mean?
(Why are you using B for 8 or dropping the 8 altogether?)


> Previously all autoupdates had installed fine.
> When installing any of the above updates from disc I get the error message:
> " The file cmd.exe is missing from the KBB 41533 installation. The
> file must be present for KB 41533 to continue ".
> I can find cmd.exe at c:\WINNT\system32\ but nowhere else on the
> system.........anyone any idea as to what is wrong here ?

Apparently that update for your OS includes a new version of that
module.

<title>MS04-031 : Vulnerability in NetDDE Could Allow Remote Code Execution (841533)</title>

<quote>
21-Sep-2003 00:45 5.0.2195.6824 236,304 Cmd.exe
</quote>

Do a search of your entire harddrive to find that module name
and tell us what version you find where.

Also do a search of files which were modified the day you tried
the update which contain that cmd string. Perhaps you will find
some more files or diagnostics to give you some further clues.


Good luck

Robert Aldwinckle
---


> thanks
> Seamus
>

"Robert Aldwinckle" wrote:
> (My interpretation of some assumed typos <w>)
( correct assumptions )

> > I am using Win2k Prof V5.0.2195 SP4 Build 2195 and cannot install
> > critical updates since Jan when KBB 91711, 41533 and 40987 first arrived.
>
> KB891711 KB841533 and KB840987 you mean?
> (Why are you using B for 8 or dropping the 8 altogether?)
doh ! - transcribing late at night. the 4 updates in question are:
KB835732, 891711, 840987 and 841533.
>
> > Previously all autoupdates had installed fine.
> > When installing any of the above updates from disc I get the error message:
> > " The file cmd.exe is missing from the KBB 41533 installation. The
> > file must be present for KB 41533 to continue ".
> > I can find cmd.exe at c:\WINNT\system32\ but nowhere else on the
> > system.........anyone any idea as to what is wrong here ?
>
> Apparently that update for your OS includes a new version of that
> module.
how do I get hold of the new version of the module ?

> Do a search of your entire harddrive to find that module name
> and tell us what version you find where.
strangely a search with Explorer gives no results looking for
cmd.exe or even cmd.*....but Start, Run with cmd.exe brings up
a `dos window` C:\WINNT\system32\cmd.exe.

> Also do a search of files which were modified the day you tried
> the update which contain that cmd string.
how would I go about that ?

appreciate your help.

Seamus M

"seamusm" <> wrote in message
news:21582596-3B05-4FD6-8497-...
>
> "Robert Aldwinckle" wrote:
>> (My interpretation of some assumed typos <w>)
> ( correct assumptions )
>
>> > I am using Win2k Prof V5.0.2195 SP4 Build 2195 and cannot install
>> > critical updates since Jan when KBB 91711, 41533 and 40987 first arrived.
>>
>> KB891711 KB841533 and KB840987 you mean?
>> (Why are you using B for 8 or dropping the 8 altogether?)
> doh ! - transcribing late at night. the 4 updates in question are:
> KB835732, 891711, 840987 and 841533.
>>
>> > Previously all autoupdates had installed fine.
>> > When installing any of the above updates from disc I get the error message:
>> > " The file cmd.exe is missing from the KBB 41533 installation. The
>> > file must be present for KB 41533 to continue ".
>> > I can find cmd.exe at c:\WINNT\system32\ but nowhere else on the
>> > system.........anyone any idea as to what is wrong here ?
>>
>> Apparently that update for your OS includes a new version of that
>> module.
> how do I get hold of the new version of the module ?
>
>> Do a search of your entire harddrive to find that module name
>> and tell us what version you find where.
> strangely a search with Explorer gives no results looking for
> cmd.exe or even cmd.*....but Start, Run with cmd.exe brings up
> a `dos window` C:\WINNT\system32\cmd.exe.

That probably means that your Search tool isn't set up correctly.
You may need to enable More settings... (or Advanced settings...
etc.) to ensure that you can find *any* file on your machine.
Another possibility is that you aren't starting with the right drive
or if you have the right drive you aren't allowing it to search
all folders, etc.


>
>> Also do a search of files which were modified the day you tried
>> the update which contain that cmd string.
> how would I go about that ?

More advanced settings in your search tool.
I am only familiar with NT4 and XP.
Never used W2K. Is there a Help for it?
E.g. in XP I just pressed Win-F and F1
to bring up "Search Companion overview"

In NT4 IIRC there was also a Help but the options
were much more obvious IMO anyway since it used
tabs instead of XP's quirky now-you-see-'em now-you-don't
side-bar options. The functionality is identical;
so I imagine that you will have it too in your OS.
You'll just have to experiment a bit.

The essential idea is that you just restrict your search
to one day by making the date range which undoubtedly
is supported somehow just have the same begin and
end.

A related option you should have is the ability to search
for text within files. In that case you could enter cmd
as the text you want to search for and again restrict
your date range to the one day that the update was
attempted. Doing that you would hope to be able
to find some diagnostics from your update attempt
which were related to the new version of cmd.exe

There is another feature of XP's search which you
may not have but which could be useful for you and
that is that it can search for files within .zip and .cab
file archives. Even so, if you can search those file
types for containing strings you may get a clue about
what files they contain and then use other tools to
expand them to see if they really do contain the files
you need. Etc.


>
> appreciate your help.
>
> Seamus M
>
>


Good luck

Robert
---

> >> > I am using Win2k Prof V5.0.2195 SP4 Build 2195 and cannot install
> >> > critical updates since Jan when KBB 91711, 41533 and 40987 first arrived.
> >>
> >> KB891711 KB841533 and KB840987 you mean?
> >> (Why are you using B for 8 or dropping the 8 altogether?)
> > doh ! - transcribing late at night. the 4 updates in question are:
> > KB835732, 891711, 840987 and 841533.
> >>
> >> > Previously all autoupdates had installed fine.
> >> > When installing any of the above updates from disc I get the error message:
> >> > " The file cmd.exe is missing from the KBB 41533 installation. The
> >> > file must be present for KB 41533 to continue ".
> >> > I can find cmd.exe at c:\WINNT\system32\ but nowhere else on the
> >> > system.........anyone any idea as to what is wrong here ?
> >>
> >> Apparently that update for your OS includes a new version of that
> >> module.
> > how do I get hold of the new version of the module ?
???

> >> Do a search of your entire harddrive to find that module name
> >> and tell us what version you find where.
> > strangely a search with Explorer gives no results looking for
> > cmd.exe or even cmd.*....but Start, Run with cmd.exe brings up
> > a `dos window` C:\WINNT\system32\cmd.exe.
>
> That probably means that your Search tool isn't set up correctly.
> You may need to enable More settings... (or Advanced settings...
> etc.)...........
ok. I learned to use the search command properly !

> .......................Even so, if you can search those file
> types for containing strings you may get a clue about
> what files they contain and then use other tools to
> expand them to see if they really do contain the files
> you need. Etc.
I found this text file created on the day I tried the manual install:

~~~~~~~~~~~~~~~~~~~~~
[KB891711.log]
0.370:
================================================== ==============================
0.370: 2005/01/11 19:31:01.482 (local)
0.370: c:\55be83819adc2343da20befb008d\update\UPDATE.EXE (version 5.5.33.0)
0.400: Service Pack started with following command line: -q /Z -ER
2.473: DoInstallation: CleanPFR failed: 0x2
2.483: SetProductTypes: InfProductBuildType=BuildType.IP
2.493: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.584: IncludeDirectoryIdFromInfSection: No DirId found for:
DontRemoveOnUninst.DirId
2.604: DoInstallation: FetchSourceURL for
c:\55be83819adc2343da20befb008d\update\update.inf failed
2.604: CreateUninstall = 1,Directory = C:\WINNT\$NtUninstallKB891711$
2.644: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed:
0xe0000102
2.664: BuildCabinetManifest: update.url absent
2.684: Starting AnalyzeComponents
2.684: AnalyzePhaseZero used 0 ticks
2.684: OEM file scan used 0 ticks
7.340: AnalyzePhaseOne: used 4656 ticks
7.340: AnalyzeComponents: Hotpatch analysis disabled; skipping.
7.340: AnalyzeComponents: Hotpatching is disabled.
7.360: AnalyzePhaseTwo used 20 ticks
7.360: AnalyzePhaseThree used 0 ticks
7.360: AnalyzePhaseFive used 0 ticks
7.531: AnalyzePhaseSix used 171 ticks
7.531: AnalyzeComponents used 4847 ticks
7.531: Downloading 0 files
7.531: bPatchMode = FALSE
7.531: Inventory complete: ReturnStatus=0, 4927 ticks
7.531: Num Ticks for invent : 4927
7.531: Allocation size of drive C: is 4096 bytes, free space = 16094261248
bytes
7.531: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
7.531: Drive C: free 15348MB req: 17MB w/uninstall: NOT CALCULATED.
7.531: CabinetBuild complete
7.531: Num Ticks for Cabinet build : 0
7.551: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed:
0xe0000102
8.742: Num Ticks for Backup : 1211
10.064: Num Ticks for creating uninst inf : 1322
10.094: Registering Uninstall Program for -> KB891711, KB891711 , 0x0
10.104: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed:
0xe0000102
10.355: PFE2: Not avoiding Per File Exceptions.
11.436: GetCatVersion: Failed to retrieve version information from
C:\WINNT\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB891711.cat
with error 0x57
12.858: Copied file: C:\WINNT\system32\KERNEL32.DLL
13.679: Copied file: C:\WINNT\system32\WIN32K.SYS
13.820: Copied file: C:\WINNT\system32\WINSRV.DLL
13.910: Copied file: C:\WINNT\system32\BASESRV.DLL
14.000: Copied file (delayed): C:\WINNT\system32\SET239.tmp
14.080: Copied file: C:\WINNT\system32\GDI32.DLL
14.140: Copied file (delayed): C:\WINNT\system32\SET23A.tmp
14.250: Copied file: C:\WINNT\system32\mf3216.dll
14.370: Copied file: C:\WINNT\system32\mpr.dll
14.461: Copied file (delayed): C:\WINNT\system32\SET23C.tmp
14.551: Copied file: C:\WINNT\system32\MSGINA.DLL
14.631: Copied file (delayed): C:\WINNT\system32\SET23D.tmp
14.731: Copied file: C:\WINNT\system32\USER32.DLL
14.861: Copied file (delayed): C:\WINNT\system32\SET23E.tmp
14.941: Copied file: C:\WINNT\system32\sp3res.dll
15.782: Copied file: C:\WINNT\Driver Cache\i386\kernel32.dll
16.073: Copied file: C:\WINNT\Driver Cache\i386\win32k.sys
16.484: Copied file: C:\WINNT\Driver Cache\i386\winsrv.dll
16.604: Copied file: C:\WINNT\system32\DllCache\sp3res.dll
17.345: Copied file: C:\WINNT\system32\DllCache\BASESRV.DLL
17.435: Copied file: C:\WINNT\system32\DllCache\GDI32.DLL
17.565: Copied file: C:\WINNT\system32\DllCache\kernel32.dll
17.815: Copied file: C:\WINNT\system32\DllCache\mf3216.dll
17.946: Copied file: C:\WINNT\system32\DllCache\mpr.dll
18.066: Copied file: C:\WINNT\system32\DllCache\MSGINA.DLL
18.186: Copied file: C:\WINNT\system32\DllCache\USER32.DLL
18.316: Copied file: C:\WINNT\system32\DllCache\win32k.sys
18.627: Copied file: C:\WINNT\system32\DllCache\winsrv.dll
18.937: Num Ticks for Copying files : 8873
18.977: Num Ticks for Reg update and deleting 0 size files : 40
19.047: ---- Old Information In The Registry ------
19.077: Source:C:\WINNT\system32\_000017_.tmp.dll (5.0.2195.6946)
19.077: Destination:
19.077: Source:C:\WINNT\system32\_000018_.tmp.dll (5.0.2195.6966)
19.077: Destination:
19.087: Source:C:\WINNT\system32\_000019_.tmp.dll (5.0.2195.6946)
19.087: Destination:
19.117: Source:C:\WINNT\system32\SET239.tmp (5.0.2195.6951)
19.117: Destination:C:\WINNT\system32\BASESRV.DLL (5.0.2195.6951)
19.167: Source:C:\WINNT\system32\SET23A.tmp (5.0.2195.6945)
19.167: Destination:C:\WINNT\system32\GDI32.DLL (5.0.2195.6945)
19.197: Source:C:\WINNT\system32\SET23C.tmp (5.0.2195.6824)
19.197: Destination:C:\WINNT\system32\mpr.dll (5.0.2195.6824)
19.227: Source:C:\WINNT\system32\SET23D.tmp (5.0.2195.6928)
19.227: Destination:C:\WINNT\system32\MSGINA.DLL (5.0.2195.6928)
19.288: Source:C:\WINNT\system32\SET23E.tmp (5.0.2195.7017)
19.288: Destination:C:\WINNT\system32\USER32.DLL (5.0.2195.6897)
19.288: ---- New Information In The Registry ------
19.288: Source:C:\WINNT\system32\_000017_.tmp.dll (5.0.2195.6946)
19.288: Destination:
19.288: Source:C:\WINNT\system32\_000018_.tmp.dll (5.0.2195.6966)
19.288: Destination:
19.288: Source:C:\WINNT\system32\_000019_.tmp.dll (5.0.2195.6946)
19.288: Destination:
19.288: Source:C:\WINNT\system32\SET239.tmp (5.0.2195.6951)
19.288: Destination:C:\WINNT\system32\BASESRV.DLL (5.0.2195.6951)
19.288: Source:C:\WINNT\system32\SET23A.tmp (5.0.2195.6945)
19.288: Destination:C:\WINNT\system32\GDI32.DLL (5.0.2195.6945)
19.288: Source:C:\WINNT\system32\SET23C.tmp (5.0.2195.6824)
19.288: Destination:C:\WINNT\system32\mpr.dll (5.0.2195.6824)
19.288: Source:C:\WINNT\system32\SET23D.tmp (5.0.2195.6928)
19.288: Destination:C:\WINNT\system32\MSGINA.DLL (5.0.2195.6928)
19.288: Source:C:\WINNT\system32\SET23E.tmp (5.0.2195.7017)
19.288: Destination:C:\WINNT\system32\USER32.DLL (5.0.2195.6897)
29.652: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
29.652: IsRebootRequiredForFileQueue: At least one file operation was
delayed; reboot is required.
If none are listed below, check above for
delayed deletes.
29.652: IsRebootRequiredForFileQueue: c:\winnt\system32\user32.dll was
delayed; reboot is required.
29.652: IsRebootRequiredForFileQueue: c:\winnt\system32\winsrv.dll was
no-delay replaced; reboot is required.
29.652: IsRebootRequiredForFileQueue: c:\winnt\system32\win32k.sys was
no-delay replaced; reboot is required.
29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\kernel32.dll was
no-delay replaced; reboot is required.
29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\msgina.dll was
delayed; reboot is required.
29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\mpr.dll was delayed;
reboot is required.
29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\gdi32.dll was
delayed; reboot is required.
29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\basesrv.dll was
delayed; reboot is required.
29.662: DoInstallation: A reboot is required to complete the installation of
one or more files.
29.703: VerifySize: Unable to verify size: Source = NULL: c:\winnt\oem11.cat
32.847: RebootNecessary = 1,WizardInput = 1 , DontReboot = 1, ForceRestart = 0
0.410:
================================================== ==============================
0.430: 2005/01/18 20:54:33.605 (local)
0.430: c:\8fad019abf546f30a28749de562a5141\update\UPDATE. EXE (version
5.5.33.0)
0.460: Service Pack started with following command line: -q /Z -ER
2.824: DoInstallation: CleanPFR failed: 0x2
2.854: SetProductTypes: InfProductBuildType=BuildType.IP
2.854: SetAltOsLoaderPath: No section uses DirId 65701; done.
3.224: IncludeDirectoryIdFromInfSection: No DirId found for:
DontRemoveOnUninst.DirId
3.274: DoInstallation: FetchSourceURL for
c:\8fad019abf546f30a28749de562a5141\update\update. inf failed
3.274: CreateUninstall = 0,Directory = C:\WINNT\$NtUninstallKB891711$
3.384: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed:
0xe0000102
3.404: BuildCabinetManifest: update.url absent
3.424: Starting AnalyzeComponents
3.424: AnalyzePhaseZero used 0 ticks
3.485: OEM file scan used 0 ticks
6.148: AnalyzePhaseOne: used 2724 ticks
6.148: AnalyzeComponents: Hotpatch analysis disabled; skipping.
6.148: AnalyzeComponents: Hotpatching is disabled.
6.148: AnalyzePhaseTwo used 0 ticks
6.148: AnalyzePhaseThree used 0 ticks
6.178: AnalyzePhaseFive used 0 ticks
6.178: Missing file cmd.exe
6.178: AnalyzePhaseSix used 0 ticks
6.178: AnalyzeComponents used 2754 ticks
6.178: Downloading 0 files
6.178: bPatchMode = FALSE
6.178: Inventory complete: ReturnStatus=2, 2904 ticks
6.178: Num Ticks for invent : 2904
6.188: The file cmd.exe is missing from the KB891711 installation.
The file must be present for KB891711 Setup to continue.

Press OK to cancel Setup.
6.279: VerifySize: Unable to verify size: Source = NULL: c:\winnt\oem11.cat
6.499: KB891711 Setup canceled.
6.499: Update.exe extended error code = 0xf00d

etc etc
~~~~~~~~~~~~~~~
does this give any clues ?

some (basic?) questions:
1. should I be in touch with MS support directly about this ?
2. Is there a recent update (SP4 ?) that I can reinstall to
reload missing files ?
3. should I be looking to upgrade this mc to XP
( I see most posts here are to do with XP)

thanks
for your help.

seamus m

"seamusm" <> wrote in message
news:94E55894-CCA8-48A1-BC22-...
>
>> >> > I am using Win2k Prof V5.0.2195 SP4 Build 2195 and cannot install
>> >> > critical updates since Jan when KBB 91711, 41533 and 40987 first arrived.
>> >>
>> >> KB891711 KB841533 and KB840987 you mean?
>> >> (Why are you using B for 8 or dropping the 8 altogether?)
>> > doh ! - transcribing late at night. the 4 updates in question are:
>> > KB835732, 891711, 840987 and 841533.
>> >>
>> >> > Previously all autoupdates had installed fine.
>> >> > When installing any of the above updates from disc I get the error message:
>> >> > " The file cmd.exe is missing from the KBB 41533 installation. The
>> >> > file must be present for KB 41533 to continue ".
>> >> > I can find cmd.exe at c:\WINNT\system32\ but nowhere else on the
>> >> > system.........anyone any idea as to what is wrong here ?
>> >>
>> >> Apparently that update for your OS includes a new version of that
>> >> module.
>> > how do I get hold of the new version of the module ?
> ???
>
>> >> Do a search of your entire harddrive to find that module name
>> >> and tell us what version you find where.
>> > strangely a search with Explorer gives no results looking for
>> > cmd.exe or even cmd.*....but Start, Run with cmd.exe brings up
>> > a `dos window` C:\WINNT\system32\cmd.exe.
>>
>> That probably means that your Search tool isn't set up correctly.
>> You may need to enable More settings... (or Advanced settings...
>> etc.)...........
> ok. I learned to use the search command properly !

So, where is cmd.exe? What version is it? (Version#, Size, and Date)
If you have the Support Tools installed you can use filever.


>
>> .......................Even so, if you can search those file
>> types for containing strings you may get a clue about
>> what files they contain and then use other tools to
>> expand them to see if they really do contain the files
>> you need. Etc.
> I found this text file created on the day I tried the manual install:

It looks as if it worked. Did you do the boot it wanted to do?
BTW would you have had an Anti-virus app enabled then?
Perhaps you should have disabled it first in case those
delayed copy's were interfered with by the AV app.

BTW was this really that long ago or is your computer's date wrong?

Why did you need to do it again?


>
> ~~~~~~~~~~~~~~~~~~~~~
> [KB891711.log]
> 0.370:
> ================================================== ==============================
> 0.370: 2005/01/11 19:31:01.482 (local)
> 0.370: c:\55be83819adc2343da20befb008d\update\UPDATE.EXE (version 5.5.33.0)
> 0.400: Service Pack started with following command line: -q /Z -ER
> 2.473: DoInstallation: CleanPFR failed: 0x2
> 2.483: SetProductTypes: InfProductBuildType=BuildType.IP
> 2.493: SetAltOsLoaderPath: No section uses DirId 65701; done.
> 2.584: IncludeDirectoryIdFromInfSection: No DirId found for:
> DontRemoveOnUninst.DirId
> 2.604: DoInstallation: FetchSourceURL for
> c:\55be83819adc2343da20befb008d\update\update.inf failed
> 2.604: CreateUninstall = 1,Directory = C:\WINNT\$NtUninstallKB891711$
> 2.644: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed:
> 0xe0000102
> 2.664: BuildCabinetManifest: update.url absent
> 2.684: Starting AnalyzeComponents
> 2.684: AnalyzePhaseZero used 0 ticks
> 2.684: OEM file scan used 0 ticks
> 7.340: AnalyzePhaseOne: used 4656 ticks
> 7.340: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> 7.340: AnalyzeComponents: Hotpatching is disabled.
> 7.360: AnalyzePhaseTwo used 20 ticks
> 7.360: AnalyzePhaseThree used 0 ticks
> 7.360: AnalyzePhaseFive used 0 ticks
> 7.531: AnalyzePhaseSix used 171 ticks
> 7.531: AnalyzeComponents used 4847 ticks
> 7.531: Downloading 0 files
> 7.531: bPatchMode = FALSE
> 7.531: Inventory complete: ReturnStatus=0, 4927 ticks
> 7.531: Num Ticks for invent : 4927
> 7.531: Allocation size of drive C: is 4096 bytes, free space = 16094261248
> bytes
> 7.531: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
> 7.531: Drive C: free 15348MB req: 17MB w/uninstall: NOT CALCULATED.
> 7.531: CabinetBuild complete
> 7.531: Num Ticks for Cabinet build : 0
> 7.551: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed:
> 0xe0000102
> 8.742: Num Ticks for Backup : 1211
> 10.064: Num Ticks for creating uninst inf : 1322
> 10.094: Registering Uninstall Program for -> KB891711, KB891711 , 0x0
> 10.104: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed:
> 0xe0000102
> 10.355: PFE2: Not avoiding Per File Exceptions.
> 11.436: GetCatVersion: Failed to retrieve version information from
> C:\WINNT\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB891711.cat
> with error 0x57
> 12.858: Copied file: C:\WINNT\system32\KERNEL32.DLL
> 13.679: Copied file: C:\WINNT\system32\WIN32K.SYS
> 13.820: Copied file: C:\WINNT\system32\WINSRV.DLL
> 13.910: Copied file: C:\WINNT\system32\BASESRV.DLL
> 14.000: Copied file (delayed): C:\WINNT\system32\SET239.tmp
> 14.080: Copied file: C:\WINNT\system32\GDI32.DLL
> 14.140: Copied file (delayed): C:\WINNT\system32\SET23A.tmp
> 14.250: Copied file: C:\WINNT\system32\mf3216.dll
> 14.370: Copied file: C:\WINNT\system32\mpr.dll
> 14.461: Copied file (delayed): C:\WINNT\system32\SET23C.tmp
> 14.551: Copied file: C:\WINNT\system32\MSGINA.DLL
> 14.631: Copied file (delayed): C:\WINNT\system32\SET23D.tmp
> 14.731: Copied file: C:\WINNT\system32\USER32.DLL
> 14.861: Copied file (delayed): C:\WINNT\system32\SET23E.tmp
> 14.941: Copied file: C:\WINNT\system32\sp3res.dll
> 15.782: Copied file: C:\WINNT\Driver Cache\i386\kernel32.dll
> 16.073: Copied file: C:\WINNT\Driver Cache\i386\win32k.sys
> 16.484: Copied file: C:\WINNT\Driver Cache\i386\winsrv.dll
> 16.604: Copied file: C:\WINNT\system32\DllCache\sp3res.dll
> 17.345: Copied file: C:\WINNT\system32\DllCache\BASESRV.DLL
> 17.435: Copied file: C:\WINNT\system32\DllCache\GDI32.DLL
> 17.565: Copied file: C:\WINNT\system32\DllCache\kernel32.dll
> 17.815: Copied file: C:\WINNT\system32\DllCache\mf3216.dll
> 17.946: Copied file: C:\WINNT\system32\DllCache\mpr.dll
> 18.066: Copied file: C:\WINNT\system32\DllCache\MSGINA.DLL
> 18.186: Copied file: C:\WINNT\system32\DllCache\USER32.DLL
> 18.316: Copied file: C:\WINNT\system32\DllCache\win32k.sys
> 18.627: Copied file: C:\WINNT\system32\DllCache\winsrv.dll
> 18.937: Num Ticks for Copying files : 8873
> 18.977: Num Ticks for Reg update and deleting 0 size files : 40
> 19.047: ---- Old Information In The Registry ------
> 19.077: Source:C:\WINNT\system32\_000017_.tmp.dll (5.0.2195.6946)
> 19.077: Destination:
> 19.077: Source:C:\WINNT\system32\_000018_.tmp.dll (5.0.2195.6966)
> 19.077: Destination:
> 19.087: Source:C:\WINNT\system32\_000019_.tmp.dll (5.0.2195.6946)
> 19.087: Destination:
> 19.117: Source:C:\WINNT\system32\SET239.tmp (5.0.2195.6951)
> 19.117: Destination:C:\WINNT\system32\BASESRV.DLL (5.0.2195.6951)
> 19.167: Source:C:\WINNT\system32\SET23A.tmp (5.0.2195.6945)
> 19.167: Destination:C:\WINNT\system32\GDI32.DLL (5.0.2195.6945)
> 19.197: Source:C:\WINNT\system32\SET23C.tmp (5.0.2195.6824)
> 19.197: Destination:C:\WINNT\system32\mpr.dll (5.0.2195.6824)
> 19.227: Source:C:\WINNT\system32\SET23D.tmp (5.0.2195.6928)
> 19.227: Destination:C:\WINNT\system32\MSGINA.DLL (5.0.2195.6928)
> 19.288: Source:C:\WINNT\system32\SET23E.tmp (5.0.2195.7017)
> 19.288: Destination:C:\WINNT\system32\USER32.DLL (5.0.2195.6897)
> 19.288: ---- New Information In The Registry ------
> 19.288: Source:C:\WINNT\system32\_000017_.tmp.dll (5.0.2195.6946)
> 19.288: Destination:
> 19.288: Source:C:\WINNT\system32\_000018_.tmp.dll (5.0.2195.6966)
> 19.288: Destination:
> 19.288: Source:C:\WINNT\system32\_000019_.tmp.dll (5.0.2195.6946)
> 19.288: Destination:
> 19.288: Source:C:\WINNT\system32\SET239.tmp (5.0.2195.6951)
> 19.288: Destination:C:\WINNT\system32\BASESRV.DLL (5.0.2195.6951)
> 19.288: Source:C:\WINNT\system32\SET23A.tmp (5.0.2195.6945)
> 19.288: Destination:C:\WINNT\system32\GDI32.DLL (5.0.2195.6945)
> 19.288: Source:C:\WINNT\system32\SET23C.tmp (5.0.2195.6824)
> 19.288: Destination:C:\WINNT\system32\mpr.dll (5.0.2195.6824)
> 19.288: Source:C:\WINNT\system32\SET23D.tmp (5.0.2195.6928)
> 19.288: Destination:C:\WINNT\system32\MSGINA.DLL (5.0.2195.6928)
> 19.288: Source:C:\WINNT\system32\SET23E.tmp (5.0.2195.7017)
> 19.288: Destination:C:\WINNT\system32\USER32.DLL (5.0.2195.6897)
> 29.652: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
> empty; nothing to do.
> 29.652: IsRebootRequiredForFileQueue: At least one file operation was
> delayed; reboot is required.
> If none are listed below, check above for
> delayed deletes.
> 29.652: IsRebootRequiredForFileQueue: c:\winnt\system32\user32.dll was
> delayed; reboot is required.
> 29.652: IsRebootRequiredForFileQueue: c:\winnt\system32\winsrv.dll was
> no-delay replaced; reboot is required.
> 29.652: IsRebootRequiredForFileQueue: c:\winnt\system32\win32k.sys was
> no-delay replaced; reboot is required.
> 29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\kernel32.dll was
> no-delay replaced; reboot is required.
> 29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\msgina.dll was
> delayed; reboot is required.
> 29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\mpr.dll was delayed;
> reboot is required.
> 29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\gdi32.dll was
> delayed; reboot is required.
> 29.662: IsRebootRequiredForFileQueue: c:\winnt\system32\basesrv.dll was
> delayed; reboot is required.
> 29.662: DoInstallation: A reboot is required to complete the installation of
> one or more files.
> 29.703: VerifySize: Unable to verify size: Source = NULL: c:\winnt\oem11.cat
> 32.847: RebootNecessary = 1,WizardInput = 1 , DontReboot = 1, ForceRestart = 0
> 0.410:
> ================================================== ==============================
> 0.430: 2005/01/18 20:54:33.605 (local)
> 0.430: c:\8fad019abf546f30a28749de562a5141\update\UPDATE. EXE (version
> 5.5.33.0)
> 0.460: Service Pack started with following command line: -q /Z -ER
> 2.824: DoInstallation: CleanPFR failed: 0x2
> 2.854: SetProductTypes: InfProductBuildType=BuildType.IP
> 2.854: SetAltOsLoaderPath: No section uses DirId 65701; done.
> 3.224: IncludeDirectoryIdFromInfSection: No DirId found for:
> DontRemoveOnUninst.DirId
> 3.274: DoInstallation: FetchSourceURL for
> c:\8fad019abf546f30a28749de562a5141\update\update. inf failed
> 3.274: CreateUninstall = 0,Directory = C:\WINNT\$NtUninstallKB891711$
> 3.384: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed:
> 0xe0000102
> 3.404: BuildCabinetManifest: update.url absent
> 3.424: Starting AnalyzeComponents
> 3.424: AnalyzePhaseZero used 0 ticks
> 3.485: OEM file scan used 0 ticks
> 6.148: AnalyzePhaseOne: used 2724 ticks
> 6.148: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> 6.148: AnalyzeComponents: Hotpatching is disabled.
> 6.148: AnalyzePhaseTwo used 0 ticks
> 6.148: AnalyzePhaseThree used 0 ticks
> 6.178: AnalyzePhaseFive used 0 ticks
> 6.178: Missing file cmd.exe
> 6.178: AnalyzePhaseSix used 0 ticks
> 6.178: AnalyzeComponents used 2754 ticks
> 6.178: Downloading 0 files
> 6.178: bPatchMode = FALSE
> 6.178: Inventory complete: ReturnStatus=2, 2904 ticks
> 6.178: Num Ticks for invent : 2904
> 6.188: The file cmd.exe is missing from the KB891711 installation.
> The file must be present for KB891711 Setup to continue.
>
> Press OK to cancel Setup.
> 6.279: VerifySize: Unable to verify size: Source = NULL: c:\winnt\oem11.cat
> 6.499: KB891711 Setup canceled.
> 6.499: Update.exe extended error code = 0xf00d
>
> etc etc
> ~~~~~~~~~~~~~~~
> does this give any clues ?

Yes. See my comments above.
A problem is that this isn't the log of the update that
should have updated cmd.exe. Where is it?
Did you search for files containing cmd
as I suggested?


>
> some (basic?) questions:
> 1. should I be in touch with MS support directly about this ?

If you prefer.


> 2. Is there a recent update (SP4 ?) that I can reinstall to
> reload missing files ?

Let's find cmd.exe first and find out what version it is.
The picture of the state of your system is not clear.


> 3. should I be looking to upgrade this mc to XP
> ( I see most posts here are to do with XP)

Unless you mean start fresh with a new OS
it would be a bad idea to try to update or upgrade
until you get your current system into a consistent
state. Updating when something is already broken
often results in a bigger mess to try to untangle than
one would have had if one had just stopped to repair
first.



>
> thanks
> for your help.
>
> seamus m


HTH

Robert
---

> >> >> > Previously all autoupdates had installed fine.
> >> >> > When installing any of the above updates from disc I get the error message:
> >> >> > " The file cmd.exe is missing from the KBB 41533 installation. The
> >> >> > file must be present for KB 41533 to continue ".
> >> >> > I can find cmd.exe at c:\WINNT\system32\ but nowhere else on the
> >> >> > system.........anyone any idea as to what is wrong here ?

> >> >> Do a search of your entire harddrive to find that module name
> >> >> and tell us what version you find where.
> >> > strangely a search with Explorer gives no results looking for
> >> > cmd.exe or even cmd.*....but Start, Run with cmd.exe brings up
> >> > a `dos window` C:\WINNT\system32\cmd.exe.
> >>
> >> That probably means that your Search tool isn't set up correctly.
> >> You may need to enable More settings... (or Advanced settings...
> >> etc.)...........
> > ok. I learned to use the search command properly !
( well. I hope I did.... )


> So, where is cmd.exe? What version is it? (Version#, Size, and Date)
I have used `search` and can find no ` cmd.exe` file anywhere on the system.
> If you have the Support Tools installed you can use filever.
I do not appear to have that. I checked on the Search Help which has no
mention of `filever`

> >> .......................Even so, if you can search those file
> >> types for containing strings you may get a clue about
> >> what files they contain and then use other tools to
> >> expand them to see if they really do contain the files
> >> you need. Etc.
> > I found this text file created on the day I tried the manual install:
>
> It looks as if it worked. Did you do the boot it wanted to do?
> BTW would you have had an Anti-virus app enabled then?
> Perhaps you should have disabled it first in case those
> delayed copy's were interfered with by the AV app.
> BTW was this really that long ago or is your computer's date wrong?
The date shown at the beginning of that log file does not make sense to me
and I did have McAfee turned off temporarly.
perhaps for now I should concentrate on finding the missing cmd.exe file.
otherwise things will get too complicated.

> A problem is that this isn't the log of the update that
> should have updated cmd.exe. Where is it?
> Did you search for files containing cmd
> as I suggested?
when I do a search for files containing `cmd.exe` I get 82 objects
mentioned. When I do a search for files containing `cmd.exe` on the dates I
attempted the manual update I find a single text file.

I guess I am stuck without any info on cmd.exe ?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > some (basic?) questions:
> > 1. should I be in touch with MS support directly about this ?
> If you prefer.
nope. just curious as I have never had any reason to get help before.
I saw this forum and jumped in.

> > 2. Is there a recent update (SP4 ?) that I can reinstall to
> > reload missing files ?

> Let's find cmd.exe first and find out what version it is.
> The picture of the state of your system is not clear.
ok. makes sense.

> > 3. should I be looking to upgrade this mc to XP
> > ( I see most posts here are to do with XP)
>
> Unless you mean start fresh with a new OS
> it would be a bad idea to try to update or upgrade
> until you get your current system into a consistent
> state. Updating when something is already broken
> often results in a bigger mess to try to untangle than
> one would have had if one had just stopped to repair
> first.
hmm...... bang goes my easy way out


Seamus

"seamusm" <> wrote in message
news:AD73B278-DF6E-4CB7-A25F-
....
>> BTW was this really that long ago or is your computer's date wrong?
> The date shown at the beginning of that log file does not make sense to me
> and I did have McAfee turned off temporarly.
> perhaps for now I should concentrate on finding the missing cmd.exe file.
> otherwise things will get too complicated.

You know where the cmd.exe is.
What we want to know is where is the update to it,
or the uninstall information for that update,
or the log for that update?

Try searching for 841533 instead and see what you get.

Also since your computer's date may be suspect
you had better not rely on that date range filter for now.
One additional filter which might be appropriate would be
*.log in the filename field.


Good luck

Robert
---

Hi Robert,

> >> BTW was this really that long ago or is your computer's date wrong?
> > The date shown at the beginning of that log file does not make sense to me
> > and I did have McAfee turned off temporarly.
> > perhaps for now I should concentrate on finding the missing cmd.exe file.
> > otherwise things will get too complicated.
>
> You know where the cmd.exe is.
> What we want to know is where is the update to it,
> or the uninstall information for that update,
> or the log for that update?
>
> Try searching for 841533 instead and see what you get.
I have had no luck in tracing the cdm.exe file. I can find
lots of files that contain it but no cmd.exe although I can run it
from Start >Run....
I think that I am a bit out of my depth plus I am away for a few days.
Once I get back I will contact MS ( for the first time) and see if they
have any ideas.


many, many thanks for your help and patience.

regards
Seamus