I have one Windows 7 update in more than one site that fails to install, generating:
"Installation Failure: Windows failed to install the following update with error 0x80070057: Security Update for Windows 7 for x64-based Systems (KB2660649)"
The WindowsUpdate.log content is:
2013-06-07 05:00:10:517 1084 1328 AU #############
2013-06-07 05:00:10:517 1084 1328 AU ## START ## AU: Install updates
2013-06-07 05:00:10:517 1084 1328 AU #########
2013-06-07 05:00:10:517 1084 1328 AU # Initiating scheduled install
2013-06-07 05:00:10:517 1084 1328 AU # Approved updates = 1
2013-06-07 05:00:10:579 1084 1328 AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {FB764F9D-589A-4AB3-97D5-E65314A74673}]
2013-06-07 05:00:10:579 1084 1194 Agent *************
2013-06-07 05:00:10:579 1084 1194 Agent ** START ** Agent: Installing updates [CallerId = AutomaticUpdates]
2013-06-07 05:00:10:579 1084 1194 Agent *********
2013-06-07 05:00:10:579 1084 1194 Agent * Updates to install = 1
2013-06-07 05:00:10:611 1084 1194 Agent * Title = Security Update for Windows 7 for x64-based Systems (KB2660649)
2013-06-07 05:00:10:611 1084 1194 Agent * UpdateId = {48993210-7C75-4DC4-917C-0BF6CCA5C60D}.106
2013-06-07 05:00:10:611 1084 1194 Agent * Bundles 1 updates:
2013-06-07 05:00:10:611 1084 1194 Agent * {29F0E274-AD1D-4599-BF3D-0C8FA9064E76}.104
2013-06-07 05:00:12:405 1084 1194 Agent WARNING: failed to calculate prior restore point time with error 0x80070002; setting restore point
2013-06-07 05:00:12:748 1084 1194 DnldMgr Preparing update for install, updateId = {29F0E274-AD1D-4599-BF3D-0C8FA9064E76}.104.
2013-06-07 05:00:12:763 3668 1258 Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0400) ===========
2013-06-07 05:00:12:763 3668 1258 Misc = Process: C:\Windows\system32\wuauclt.exe
2013-06-07 05:00:12:763 3668 1258 Misc = Module: C:\Windows\system32\wuaueng.dll
2013-06-07 05:00:12:763 3668 1258 Handler :::::::::::::
2013-06-07 05:00:12:763 3668 1258 Handler :: START :: Handler: CBS Install
2013-06-07 05:00:12:763 3668 1258 Handler :::::::::
2013-06-07 05:00:12:763 3668 1258 Handler Starting install of CBS update 29F0E274-AD1D-4599-BF3D-0C8FA9064E76
2013-06-07 05:00:12:763 3668 1258 Handler CBS package identity: Package_for_KB2660649~31bf3856ad364e35~amd64~~6.1.1.3
2013-06-07 05:00:12:763 3668 1258 Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\426da88de3960977fc8cbf31e52a5193\windows6.1-kb2660649-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\426da88de3960977fc8cbf31e52a5193\inst
2013-06-07 05:00:21:952 3668 d30 Handler FATAL: CBS called Error with 0x80070057,
2013-06-07 05:00:23:418 3668 1258 Handler FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80070057
2013-06-07 05:00:23:418 1084 77c AU >>## RESUMED ## AU: Installing update [UpdateId = {48993210-7C75-4DC4-917C-0BF6CCA5C60D}]
2013-06-07 05:00:23:418 1084 77c AU # WARNING: Install failed, error = 0x80070057 / 0x80070057
2013-06-07 05:00:23:418 3668 1258 Handler :::::::::
2013-06-07 05:00:23:418 3668 1258 Handler :: END :: Handler: CBS Install
2013-06-07 05:00:23:418 3668 1258 Handler :::::::::::::
2013-06-07 05:00:23:621 1084 1194 Agent *********
2013-06-07 05:00:23:621 1084 1194 Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
2013-06-07 05:00:23:621 1084 77c AU Install call completed.
2013-06-07 05:00:23:621 1084 1194 Agent *************
2013-06-07 05:00:23:621 1084 77c AU # WARNING: Install call completed, reboot required = No, error = 0x00000000
2013-06-07 05:00:23:621 1084 77c AU #########
2013-06-07 05:00:23:621 1084 77c AU ## END ## AU: Installing updates [CallId = {FB764F9D-589A-4AB3-97D5-E65314A74673}]
2013-06-07 05:00:23:621 1084 77c AU #############
The clients reporting this error are configured to use a common downstream WSUS server. All machines are laptops, but different manufacturers. This same update has installed successfully on desktop computers using the same WSUS server as the source, and on laptop computers that are in other sites (using a different WSUS server, but a common upstream WSUS server) so I don't suspect that it's a corrupted MSI.
I'm guessing it's something specific to the clients, but don't know where to begin to look. Any suggestions would be appreciated.