931836: CORRUPT PATCH - Windows Server 2003

Usage and Config Patch
1

(imported topic written by Shawn_Jefferson)

Hi,

I have 7 systems that are relevant for this fixlet, but when I initiated it, all of them failed. All lines in the fixlet however, say completed.

Completed: download http://download.microsoft.com/download/8/0/c/80c07410-9f85-4ca9-8d94-cd33d985c624/WindowsServer2003-KB931836-x86-ENU.exe

Completed: continue if {(size of it = 530312 and sha1 of it = “a2a7adf182587f5478e7ed603d77dff03078df6f”) of file “WindowsServer2003-KB931836-x86-ENU.exe” of folder “__Download”}

Completed: wait __Download\WindowsServer2003-KB931836-x86-ENU.exe /passive /quiet /norestart

Completed: run “{pathname of client folder of site “BESSupport” & “\RunQuiet.exe”}” “{pathname of client folder of site “BESSupport” & “\qchain.exe”}”

Completed: action may require restart

What does this mean exactly? Is the patch installed properly, or not?

Thanks,

Shawn

2

(imported comment written by BenKus)

Hey Shawn,

A CORRUPT PATCH means that the patch has been installed, but the files are not updated properly. See http://support.bigfix.com/cgi-bin/kbdirect.pl?id=68 for a description of your issue.

We were working with another customer the other day with a similar issue with this patch… Is it correct that you have a Windows 2003 Server SP1, but if you check the version of Tzchange.exe and compare it to the version that it is supposed to be as stated here http://support.microsoft.com/kb/931836 you see that it has the no-SP version and not the SP1 version?

If so, according to the security bulletin, your patch is corrupted. You will need to check with Microsoft why their patch is broken. Let us know what you find.

Ben

3

(imported comment written by Shawn_Jefferson)

Ben Kus

We were working with another customer the other day with a similar issue with this patch… Is it correct that you have a Windows 2003 Server SP1, but if you check the version of Tzchange.exe and compare it to the version that it is supposed to be as stated here http://support.microsoft.com/kb/931836 you see that it has the no-SP version and not the SP1 version?

If so, according to the security bulletin, your patch is corrupted. You will need to check with Microsoft why their patch is broken. Let us know what you find.

Hi,

The version is 5.2.3790.2872 which isn’t even in the list in that KB article.

4

(imported comment written by chenbr91)

Ben,

I have about 294 machines with this same issue.

Is there a workaround?

5

(imported comment written by BenKus)

Hi chenbr,

This is an issue between the published documentation of Microsoft and the results you are seeing in the patch… Unfortunately, this is beyond our ability to help because only Microsoft can answer your question.

If MS is unhelpful, I guess you can choose to ignore the corrupted Fixlet or try to reapply it and see if it takes, or maybe uninstall and reinstall the patch and see what happens.

Ben

6

(imported comment written by SystemAdmin)

One of my great dissatisfactions with BigFix. You guys should be going to bat for us and fixing these kinds of issues. This impacts all your customers.

7

(imported comment written by BenKus)

Hi jspanitz,

Unfortunately, the reality is that Microsoft won’t listen to us… They will not even take our call (we have tried)…

It is our experience that the most effective way of dealing with Microsoft is to have the customers convey their requirements to Microsoft because “independent software vendors” such as ourselves have pretty much no sway at Redmond.

Ben

8

(imported comment written by taltrade91)

Is this still not resolved? I’ve noticed this happening when installing SP2 for Windows Server 2003 via Bigfix. However, if I manually install SP2 by downloading and installing it on a machine, there are no reports of “corrupt” patches.

9

(imported comment written by jeremylam)

Hi taltrade,

I’m not sure what Fixlet message you are referring to - the Windows 2003 Server SP2 Fixlet does not have a corrupt patch. The title of the Corrupt Patch does not really describe the source of the problem, only the OS it refers to.

Do you know the Fixlet ID# of the Corrupt Patch you are referring to? It’s located at the bottom right of the Fixlet description.