pomroy24

All other LUP deployments work fine (Firefox, Java, Adobe Flash). Acrobat has two .cab files, 394 mb and 83 mb. It's much larger than the others and works fine in all cases except Windows 7 SP1. It looks like Microsoft is on the case per the last message in this thread: One particular software package no longer installs on Windows 7 after upgrade to SP1 - error 80070570 (file corrupt)

I can't speak for AngryTechnician. I'm troubleshooting Adobe Acrobat deployed by Local Update Publisher (no SCE or SCCM involved). It just so happens it's the same error message in Windows Update, seemingly from the same root cause. Both are large .cab files that appear to fail the digital signature test after download. I suspect there's something wrong with the way Windows 7 SP1 verifies the signatures.

Went through all the possible fixes here: You cannot install some updates or programs No luck finding anything wrong so I ran the "Fix it" tool and that didn't work either (it tries methods #1 through 5). The others don't seem to apply, most are attempts to fix corruption that occurs over time; this issue is plainly demonstrated with a very fresh installation of Windows 7 + SP1. This registry key doesn't appear to exist in Windows 7: "Error 0x80092026: The cryptographic operation failed due to a local security option setting." Thank you for the links all the same, have a nice weekend.

In brief, Local Update Publisher is an open source project that allows you to publish 3rd party updates (MSI, MSP, EXE) to a WSUS server for consumption with the built-in Windows Update client. A few changes need to be made to make it possible (like allowing 3rd party signed updates to be consumed and publishing a certificate to sign them) but it can all be accomplished in one quiet afternoon. It provides an interface very similar to WSUS (though stripped down) for monitoring the success of your deployments and can be installed on the same server as WSUS without causing problems. It solves the Acrobat/Flash/Java/Firefox updating issue effectively for admins without the time and/or resources to implement SCCM deployment. Local Update Publisher | Download Local Update Publisher software for free at SourceForge.net http://sourceforge.net/apps/mediawiki/localupdatepubl/index.php?title=Main_Page The wiki page is temporarily down - it should work soon.

Thanks for that. I've since re-searched WSUS which now magically found the updates. Last time it found no results for either KB number.

Today's test: Apply the two patches from this vulnerability (which seem not to be present on my WSUS server or clients) on a pre-SP1 machine: CVE-2010-0486 : The WinVerifyTrust function in Authenticode Signature Verification 5.1, 6.0, and 6.1 in Microsoft Windows 2000 SP4, Wind Microsoft Security Bulletin MS10-019 - Critical: Vulnerabilities in Windows Could Allow Remote Code Execution (981210) They are rolled into SP1 according to the documentation but have never appeared as Critical Updates in my WSUS for some reason.

Yup, already tried it and I can verify same. Upgrading WSUS server to Windows 2008 R2 + SP1 does *not* fix the issue.

Thread on the LUP forum here: SourceForge.net: Local Update Publisher: Topic: Windows 7 SP1 seems to break Acrobat X LUP

For what it's worth I've had the exact same problem with Adobe Acrobat Pro. We deploy it using Local Update Publisher to WSUS and consume it with Windows Update on the clients. In all cases it works flawlessly until you introduce Windows 7 SP1.