Can't install MS04-024 (QFE Desktop Installer)

[Eberhard Schefold]

We have the QFE Desktop Installer component included in our image, and we
are able to successfully install the XPPro patches

840374 MS04-015
839643 MS04-016

as well as three of the four XPPro patches from yesterdays "patch day",
i.e.

823353 MS04-018
841873 MS04-022
840315 MS04-023

However, we are not able to install

839645 MS04-024

Installation yields the error

KB839645 Setup Error
-----------------------
Setup could not verify the integrity of the file Update.inf. Make sure
the Cryptographic service is running on this computer.

Now I'm aware that this is the error that you get when you haven't fixed
the Service Pack information ("CSDVersion" etc.) properly, but this is done
on our system.

I also tried the general troubleshooting suggestions described in KB
article 822798, but that didn't help.

Has anybody of you managed to install MS04-024? Is there a known issue with
this particular patch?

 

[JC]

I am confused... are you trying to install XPE QFE's from the embedded site,
or are you simply trying to apply the WU Patches into your image?

 

[Eberhard Schefold]

JC schrieb/wrote:

I am confused... are you trying to install XPE QFE's from the embedded
site, or are you simply trying to apply the WU Patches into your
image?

I'm not using Windows Update, but yes, I am "simply" testing whether these
XP Pro patches will install on our devices. As I've written, we've included
the Desktop QFE Installer component in our image, which in principle
supports installation of XP Pro patches issued after May 11.

Microsoft doesn't guarantee that installation will work with every XP Pro
patch. But now that we have a problem with this particular patch, we need
information whether this patch is not expected to install generally, or
whether we have a problem with our particular image.

 

[Eberhard Schefold]

George schrieb/wrote:

Most of the QFEs after 2004-5-11 can install on the XPE, if you XPE
with the desktop installer tools.

Thank you, I understand that too. The problem is now that I have a problem
with a particular "new" patch, and I need to find out whether it is
supposed to work or not.

You may check the document about the desktop installer tools again.

George, thanks for your input, but I honestly don't understand what you are
trying to tell me. It may well be that I've missed something, but I checked
the documentation to the tool again, and I could find no hint that helps me
to find out what is wrong when a particular patch fails. Could you please
be more specific what passage in what document you are referring to?

for example:
WindowsXP-KB840374-x86-ENU.EXE
WindowsXP-KB839643-x86-ENU.EXE
These two run ok.

Yes, as I've written, these run for us as well.

WindowsXP-KB820291-x86-ENU.exe
WindowsXP-KB822603-x86-ENU.exe
These two failed.

These two were issued on 5-Jun-2003 and 15-Jan-2004, respectively, both
before 11-May-2004. They are therefore not documented to be supported by
the QFE Installer tool. What exactly is it that you are trying to tell me?

 

[George]

Most of the QFEs after 2004-5-11 can install on the XPE, if you XPE with the
desktop installer tools.
You may check the document about the desktop installer tools again.

for example:
WindowsXP-KB840374-x86-ENU.EXE
WindowsXP-KB839643-x86-ENU.EXE
These two run ok.

WindowsXP-KB820291-x86-ENU.exe
WindowsXP-KB822603-x86-ENU.exe
These two failed.

 

[Eberhard Schefold]

I too am unable to install: 839645 MS04-024 [...]

Thanks for the confirmation and posting about your investigations.

Although I am unsure if this information will help, it appears to me
that this could be part of the problem. Perhaps someone from MS can
comment here?

We really would appreciate it, too, if someone from Microsoft could
comment on this matter.

 

[Guest]

Eberhard,

I just visited the OEM site for QFE updates. They have recently posted patch. I tried installing it and it WORKS.

Link:

https://microsoft.embeddedoem.com/content.asp?path=/downloads/winxp/qfe/winxppro

-PjS

I too am unable to install: 839645 MS04-024 [...]

Thanks for the confirmation and posting about your investigations.

Although I am unsure if this information will help, it appears to me
that this could be part of the problem. Perhaps someone from MS can
comment here?

We really would appreciate it, too, if someone from Microsoft could
comment on this matter.

 

[Jon Fincher]

here?

No problem at all. Glad to help.


Perhaps the theory that this QFE does not have the enabling code is
true. After all MS states that the enabling code for XPe is not
guaranteed in all XP QFEs.

You're right - MS04-024 uses an earlier version of the package
installer, so the versions from the Download Center won't install on XPE
runtimes.

However, we do have a version of this package that has the newer, XPE
aware, package installer that's being released on the Restricted Access
Site later today. That package works fine.

 

[Guest]

You're right - MS04-024 uses an earlier version of the package
installer, so the versions from the Download Center won't install on XPE
runtimes.

However, we do have a version of this package that has the newer, XPE
aware, package installer that's being released on the Restricted Access
Site later today. That package works fine.

Jon,

Thank you forthe clarification. Is it safe to assume that all QFE's from this point on should be obtained from the embedded restricted site and forget about the "normal" XP QFEs from the Download Center?

PjS

 

[Eberhard Schefold]

You're right - MS04-024 uses an earlier version of the package
installer, so the versions from the Download Center won't install on XPE
runtimes.

However, we do have a version of this package that has the newer, XPE
aware, package installer that's being released on the Restricted Access
Site later today. That package works fine.

Thank you Jon, for the clarification. The terminology gets a bit
confusing at this point, since the documentation on the Desktop QFE
Installer Tool referred to XP Professional patches. Therefore I had been
under the impression that both sites (MS Download and OEM Restricted)
would provide the same patches, just with different NDAs, but now I
learn that the patches can be different. I think that the documentation
should use a different term for the patches on the OEM restricted site,
in order to avoid misunderstandings.

Anyway, we're glad to hear that there is a solution. Thanks for the
information.

 

[Eberhard Schefold]

would provide the same patches, just with different NDAs, but now I

.... not "NDAs", I meant "license agreements". But you guessed that.

 

[Eberhard Schefold]

Jon Fincher schrieb/wrote:

However, we do have a version of this package that has the newer, XPE
aware, package installer that's being released on the Restricted Access
Site later today. That package works fine.

Jon,

I installed this new version on our device, and in fact it appears to
install fine. However, according to Security Bulletin MS04-024, the file

shlwapi.dll

is supposed to be replaced by a version

6.0.2800.1514

This is not the case on our system. The file remains with a version
6.0.2800.1400.

The following files were replaced as documented:

6.0.2800.1515 Fldrclnr.dll
6.0.2800.1514 Shlwapi.dll
5.1.2600.1515 Sxs.dll
5.1.2600.1515 Xpsp2res.dll ,

however, I'm not sure from the documentation what is supposed to happen
with

17-Apr-2004 00:56 6.0.2800.1515 921,600 Comctl32.dll SP2 \Asms\60
\Msft\Windows\Common\Controls

The comctl32.dll in directory System32 remains at a version 6.0.2800.1106,
but I'm not sure if this is a problem, since there is no "Asms\..."
directory on XPE.

Could you please help to clear up the confusion?

 

[Jon Fincher]

Jon Fincher schrieb/wrote:


Jon,

I installed this new version on our device, and in fact it appears to
install fine. However, according to Security Bulletin MS04-024, the
file

shlwapi.dll

is supposed to be replaced by a version

6.0.2800.1514

This is not the case on our system. The file remains with a version
6.0.2800.1400.

I'll need a day or two to verify - we're short-handed this week. Let me
see if I can repro this here and get back to you.

 

[Jon Fincher]

I'll need a day or two to verify - we're short-handed this week. Let
me see if I can repro this here and get back to you.

Sorry for the long delay - I've been out sick for a few days, had
trouble with my test machine for a few days, and have had massive
amounts of trouble reproing this issue for you, Eberhard.

Anyway, the practical upshot is that shlwapi doesn't need to be updated.
It was added to the package to provide an upgrade path to SP2 -
apparently, on desktop systems, there could have been a problem causing
a shell failure if you upgraded to SP2 with a previous shell QFE
installer, but no updated shlwapi file.

I wan't able to repro your steps, but the e-mails I've been seeing tell
me it's unnecessary for this particular update, as it doesn't have any
effect on the security issue itself, and upgrading using the standard
SP2 installer isn't going to happen on an XPE device.

 

[Eberhard Schefold]

Jon Fincher schrieb/wrote:

Anyway, the practical upshot is that shlwapi doesn't need to be
updated.

Jon,

thanks for the information. Have you been able to find out what is supposed
to happen to the comctl32.dll as well?

In any event, I feel uncomfortable about the behavior on our system. Next
time we might no be able to get away with it so easily. It's a pity that
the problem can't be reproduced on your side. I have to keep an eye on this
issue with the next patches.

Thank you for your help!