Re: KB978601 causes "invalid digital signature" error with a CAB file

Is the digital signature valid?

For home users (only), no-charge support is available by calling
1-866-PCSAFETY (and/or 1-866-234-6020 and/or 1-800-936-5700) in the United
States and in Canada or by contacting your local Microsoft subsidiary.
There is no-charge for support calls that are associated with security
updates. When you call, clearly state that your problem is related to a
Security Update and cite the update's KB number (e.g., KB978601).

Or you can...

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

Customers who experience issues installing Microsoft security updates also
can visit the following pages for assistance:
https://consumersecuritysupport.microsoft.com/
http://support.microsoft.com/ph/6527#tab3

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.


J wrote:
> Customers with KB978601 installed are unable install one of our
> software products. They get the error "invalid digital signature" when
> the installer reaches the last cab file. I was able to reproduce the
> problem on Windows 7 and XP (both with the latest updates), and also
> verified the problem goes away after uninstalling KB978601.
>
> The following error message was logged: "Error 1330. A file that is
> required cannot be installed because the cabinet file setup11.cab has
> an invalid digital signature. This may indicate that the cabinet file
> is corrupt. Error 24592 was returned by WinVerifyTrust."
>
> Our product comes with 11 cab files. Only the last one gives the
> error. When you right-click on the cab file and view the certificate,
> the message is "This digital signature is not valid."
>
> This problem just started happening yesterday (4/15/10).
>
> Any ideas or similar experiences?