We’ve run into this issue with KB978601 also.
The key issue here is that MS stepped up enforcement in the signature validation subsystem in such a way that previously valid signatures now don’t validate.
It’s a simple test:
1. Uninstall KB978601
2. Validate the signature (look in file properties). It’s okay.
3. Install KB978601
4. Validate the signature again. Now it’s invalid. Same file. Nothing changed except for WinTrust.dll (the core Authenticode DLL in Windows that is updated by KB978601).
For our situation, the cab files that fail post-KB978601 validation are all similar: they all contain only 1 zero-length file. So essentially these cabs are empty (just a file list with no real contents). As soon as we put some dummy data in the cab file (20 characters in our case), the signature validated just fine.