Solved W7-64bit Feb-2013 Updates; KB2799494 Failed, Error Code 80070057

[thekochs]

The TrustedInstaller service cannot run in Safe Mode - so you can't install updates that way.

Their error code implies that there is another update pending which needs to complete prior to attempting to install this one - a very different situation.

Tried the clean boot...no luck....install still fails.
As you said....F8 does not work....service not running....just checked to omit that.

On your comment above at least the error is not around some corruption of instrusion but Windows is mixed up on install. Too bad we don't know which update this KB needs and we could go into Program & Features and uninstall it...re-install, then try this failed KB.

What next ? Thx very much !!!!

 

[NoelDP]

I'll do some research and get back to you - probably not until tomorrow, now.
If you haven't heard by Friday a.m. - SHOUT!

 

[thekochs]

I also tried this FixIt link.
How do I reset Windows Update components?
It said it disome repairs but when I tried to re-install no luck.
I attached HTML log/results in ZIP.

Thx for the help....hope your research comes up with something....really want to ge this fixed and I'm out of ideas.

 

[Kaktussoft]

For computers that are running Windows Vista, Windows 7, and Windows Server 2008:

1. Click the Start button, and then Run...
2. In the Run window, type notepad.
3. Type the following command lines into the Notepad window:
   
   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
   "Logging"=dword:voicewarmupx
   "Debug"=dword:00000007
4. On the File menu, click Save As.
5. In the Save in list, click Desktop.
6. In the File name box, type EnableLogging.reg, click All Files in the Save as type list, and then click Save.
7. On the desktop, double-click the EnableLogging.reg file to add the registry values to the Windows registry.
   Note: If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
8. In the confirmation dialog box, click Yes, and then click OK.
9. Run the installation you would like logged. Windows will capture the complete installation information in the Microsoft Installer .log file.

Note: Collecting these logs can take several minutes, and the installation process may seem not to be functioning correctly. Please take the necessary time for the process to finish.

Important: As soon as the installation process has finished, disable Microsoft Installer logging. If you leave logging enabled, this will slow down your computer and create large log files that require large amounts of disk space every time that you install applications or updates.

To disable Microsoft Installer logging, follow these steps:

1. Click the Start button, and then Run...
2. In the Run window, type notepad.
3. Type the following command lines into the Notepad window:
   
   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
   "Logging"=-
   "Debug"=-
4. On the File menu, click Save As.
5. In the Save in list, click Desktop.
6. In the File name box, type DisableLogging.reg, click All Files in the Save as type list, and then click Save.
7. On the desktop, double-click the DisableLogging.reg file to remove the registry values from the Windows registry.
   Note: If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
8. In the confirmation dialog box, click Yes, and then click OK.
9. Delete the EnableLogging.reg and DisableLogging.reg files from the desktop.

Technical Information:To add the Installer registry key if it does not exist

1. Exit all open programs.
2. On the Windows taskbar, click Start > Run.
3. In the Open box, type the following text:
   
   regedit
4. Click OK.
5. Go to the following key:
   
   HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows
6. In the left pane, right-click the Windows key, and then click New > Key.
7. For the new key's name, type Installer
8. Press Enter.
9. Exit the Registry Editor.

To view the installation log file

1. Confirm that Windows is configured to show hidden and system folders.
   To show hidden and system folders, read How to make Windows show all files.
2. On the Windows taskbar, click Start > Run.
3. In the Open box, type one of the following text strings:
   
   %TEMP%
   %TMP%
4. Press Enter.
   Windows Explorer opens the temporary folder.
5. Find the log file.
   The file name starts with the letters MSI and ends with the extension .log.
6. Use Notepad to open the log file.

 

[thekochs]

For computers that are running Windows Vista, Windows 7, and Windows Server 2008:

1. Click the Start button, and then Run...
2. In the Run window, type notepad.
3. Type the following command lines into the Notepad window:
   
   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
   "Logging"=dword:voicewarmupx
   "Debug"=dword:00000007
4. On the File menu, click Save As.
5. In the Save in list, click Desktop.
6. In the File name box, type EnableLogging.reg, click All Files in the Save as type list, and then click Save.
7. On the desktop, double-click the EnableLogging.reg file to add the registry values to the Windows registry.
   Note: If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
8. In the confirmation dialog box, click Yes, and then click OK.
9. Run the installation you would like logged. Windows will capture the complete installation information in the Microsoft Installer .log file.

Note: Collecting these logs can take several minutes, and the installation process may seem not to be functioning correctly. Please take the necessary time for the process to finish.

Important: As soon as the installation process has finished, disable Microsoft Installer logging. If you leave logging enabled, this will slow down your computer and create large log files that require large amounts of disk space every time that you install applications or updates.

To disable Microsoft Installer logging, follow these steps:

1. Click the Start button, and then Run...
2. In the Run window, type notepad.
3. Type the following command lines into the Notepad window:
   
   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
   "Logging"=-
   "Debug"=-
4. On the File menu, click Save As.
5. In the Save in list, click Desktop.
6. In the File name box, type DisableLogging.reg, click All Files in the Save as type list, and then click Save.
7. On the desktop, double-click the DisableLogging.reg file to remove the registry values from the Windows registry.
   Note: If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
8. In the confirmation dialog box, click Yes, and then click OK.
9. Delete the EnableLogging.reg and DisableLogging.reg files from the desktop.

Technical Information:To add the Installer registry key if it does not exist

1. Exit all open programs.
2. On the Windows taskbar, click Start > Run.
3. In the Open box, type the following text:
   
   regedit
4. Click OK.
5. Go to the following key:
   
   HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows
6. In the left pane, right-click the Windows key, and then click New > Key.
7. For the new key's name, type Installer
8. Press Enter.
9. Exit the Registry Editor.

To view the installation log file

1. Confirm that Windows is configured to show hidden and system folders.
   To show hidden and system folders, read How to make Windows show all files.
2. On the Windows taskbar, click Start > Run.
3. In the Open box, type one of the following text strings:
   
   %TEMP%
   %TMP%
4. Press Enter.
   Windows Explorer opens the temporary folder.
5. Find the log file.
   The file name starts with the letters MSI and ends with the extension .log.
6. Use Notepad to open the log file.

Thanks for the steps about but I have no idea of what you are asking to do and why.
Please provide more explanation and if you want the log files ?

Thx.

 

[Kaktussoft]

KB2799494 fails to install. Why .... hmm enable logging, try to install KB2799494 and then post logfile. Disable logging afterwards

 

[thekochs]

KB2799494 fails to install. Why .... hmm enable logging, try to install KB2799494 and then post logfile. Disable logging afterwards

Thx...I followed your instructions....still have the registry notepad (enable & disable) on my desktop.
I did the enable, ran the installer got the installer error, disabled logging.
Looked in temp and no MSI****.log file......take a look at JPEG of explorer.

So, I went ahead and re-ran the logging registry file and then took a snaphot of that section in my registry....see attached. I don't see the "logging" dword....issue ?
Just so you can see I zipped the enable logging and delete logging files I created.....both in ZIP attachment.

Thx !

 

[Kaktussoft]

EnableLogging.reg should be:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmupx"
"Debug"=dword:00000007


Sorry.

 

[Kaktussoft]

How to Enable Microsoft Installer logging and Verbose logging to gather additional troubleshooting Information

 

[thekochs]

EnableLogging.reg should be:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmupx"
"Debug"=dword:00000007


Sorry.

I tried this and still did not work....then read your link to MS.
I'm running W7-64bit so used the Vista instructions for enable.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmupx"
"Debug"=dword:00000007
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Trace]
"Flags"=dword:00000016
"Level"=dword:00000004
As FYI, the log file I could not find in my C:\{UserName} \Local Settings\Temp\ so I did a search on my HDD for MSI*.log and found the attached log and I attached JPEG of location.

I ran the KB MSI that I had dowloaded to my Desktop few days ago when it came out. (fail)
I ran the installer for the "download/online". (fail)

I've disabled logging.

Thx.

 

[NoelDP]

Please run the following commands in an Elevated Command Prompt and post the results

DIR C:\Windows\msiexec.exe /S
REG QUERY HKLM\System\CurrentControlSet\Services\MSIServer /S

 

[thekochs]

Please run the following commands in an Elevated Command Prompt and post the results

DIR C:\Windows\msiexec.exe /S
REG QUERY HKLM\System\CurrentControlSet\Services\MSIServer /S

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd\
C:\>DIR C:\Windows\msiexec.exe /S
Volume in drive C is Eric's HDD
Volume Serial Number is 8E33-161D
Directory of C:\Windows\System32
11/20/2010 08:24 AM 128,000 msiexec.exe
1 File(s) 128,000 bytes
Directory of C:\Windows\SysWOW64
11/20/2010 07:17 AM 73,216 msiexec.exe
1 File(s) 73,216 bytes
Directory of C:\Windows\winsxs\amd64_microsoft-windows-installer-executable_31bf3856ad364e35_6.1.7600.16385_none_a57666739fc
ae94c
07/13/2009 08:39 PM 127,488 msiexec.exe
1 File(s) 127,488 bytes
Directory of C:\Windows\winsxs\amd64_microsoft-windows-installer-executable_31bf3856ad364e35_6.1.7601.17514_none_a7a77a3b9cb
96ce6
11/20/2010 08:24 AM 128,000 msiexec.exe
1 File(s) 128,000 bytes
Directory of C:\Windows\winsxs\x86_microsoft-windows-installer-executable_31bf3856ad364e35_6.1.7600.16385_none_4957caefe76d7
816
07/13/2009 08:14 PM 73,216 msiexec.exe
1 File(s) 73,216 bytes
Directory of C:\Windows\winsxs\x86_microsoft-windows-installer-executable_31bf3856ad364e35_6.1.7601.17514_none_4b88deb7e45bf
bb0
11/20/2010 07:17 AM 73,216 msiexec.exe
1 File(s) 73,216 bytes
Total Files Listed:
6 File(s) 603,136 bytes
0 Dir(s) 468,217,217,024 bytes free
C:\>REG QUERY HKLM\System\CurrentControlSet\Services\MSIServer /S
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSIServer
DisplayName REG_SZ @%SystemRoot%\system32\msimsg.dll,-27
ImagePath REG_EXPAND_SZ %systemroot%\system32\msiexec.exe /V
Description REG_SZ @%SystemRoot%\system32\msimsg.dll,-32
ObjectName REG_SZ LocalSystem
ErrorControl REG_DWORD 0x1
Start REG_DWORD 0x3
Type REG_DWORD 0x10
DependOnService REG_MULTI_SZ rpcss
ServiceSidType REG_DWORD 0x1
RequiredPrivileges REG_MULTI_SZ SeTcbPrivilege\0SeCreatePagefilePrivilege\0SeLockMemoryPrivilege\0SeIncreaseBasePri
orityPrivilege\0SeCreatePermanentPrivilege\0SeAuditPrivilege\0SeSecurityPrivilege\0SeChangeNotifyPrivilege\0SeProfileSinglePr
ocessPrivilege\0SeImpersonatePrivilege\0SeCreateGlobalPrivilege\0SeAssignPrimaryTokenPrivilege\0SeRestorePrivilege\0SeIncreas
eQuotaPrivilege\0SeShutdownPrivilege\0SeTakeOwnershipPrivilege\0SeLoadDriverPrivilege
FailureActions REG_BINARY 840300000000000000000000030000001400000001000000C0D4010001000000E09304000000000000000000


****************************************************************
Also, since I did not understand "Server" I thought this was some Server I was connecting to....but I see MSIServer in your command string.....thus, did some Googling and found this thread.
what is MSIServer not found? - Microsoft Community

I went into my Services and the Windows Installer service was stopped.
I started it (successful) and also changed start mode to Automatic....was set to Manual.
I then tried to do the update (web & local .msu file)....same error.
I then unregistered & registered the MSIEXEC as shown.
I then tried to do the update (web & local .msu file)....same error.
I even logged off (no reboot) and checked to see if the Windows Installer was running, YEs, then tried update...no luck, same error.

Windows installer helps in installing programs\updates, mutiple issues.
Method 1:
You can check whether the Windows Installer service is running or not and try to re-register the Windows Installer.

Step 1:
a. Click Start, in the start search box, type Services and press Enter.
b. Scroll down and find the Windows Installer. Double-click “Windows Installer” in the Services list.
c. On the General tab, make sure the service is started under “Service status”.
d. If the service is not already running, under Service status, click Start, and then click OK.

Step 2: Unregister and re-register the Windows Installer
a. Click Start, on “search programs and files” type “cmd” right click on “cmd” and select “Run as Administrator”
b. Type “MSIEXEC /UNREGISTER” on cmd prompt and press enter.
c. Type “MSIEXEC /REGSERVER” press enter.

******************************************************************
I also went back and tried/ran the FIXIT for the MSI software update corruption issues on this KB
Error codes
See the pic from the report....it says..........
Potential Windows Update Database error detected 0x80070057 Fixed
Possible issues may prevent Windows Update from keeping your system up to date.
Repair Windows Update Database Corruption Completed
Rebuild the Windows Update Database and restart Windows Update services
I then tried to do the update (web & local .msu file)....same error.
I attached the windowsupdate.log for this FIXIT......look almost at end.......not sure what all this means....but.........
2013-02-16 20:56:33:209 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:224 608 174c Agent WARNING: Failed to evaluate Installed rule, updateId = {DDFE1B13-A595-459A-BFE2-94428E47D449}.201, hr = 80070057
2013-02-16 20:56:33:240 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:240 608 174c Agent WARNING: Failed to evaluate Installable rule, updateId = {DDFE1B13-A595-459A-BFE2-94428E47D449}.201, hr = 80070057
2013-02-16 20:56:33:256 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:271 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:271 608 174c Agent WARNING: Failed to evaluate Installed rule, updateId = {C75D596C-1D7C-49B3-BB83-A4904BB8DBAC}.201, hr = 80070057
2013-02-16 20:56:33:287 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:287 608 174c Agent WARNING: Failed to evaluate Installable rule, updateId = {C75D596C-1D7C-49B3-BB83-A4904BB8DBAC}.201, hr = 80070057
2013-02-16 20:56:33:302 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:318 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:318 608 174c Agent WARNING: Failed to evaluate Installed rule, updateId = {8C01D188-A701-4F2D-BF07-5B8C3EBA763E}.200, hr = 80070057
2013-02-16 20:56:33:334 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:334 608 174c Agent WARNING: Failed to evaluate Installable rule, updateId = {8C01D188-A701-4F2D-BF07-5B8C3EBA763E}.200, hr = 80070057
2013-02-16 20:56:33:349 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:365 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:365 608 174c Agent WARNING: Failed to evaluate Installed rule, updateId = {35196586-BBFB-4A94-9B15-83A3B120346D}.201, hr = 80070057
2013-02-16 20:56:33:380 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:380 608 174c Agent WARNING: Failed to evaluate Installable rule, updateId = {35196586-BBFB-4A94-9B15-83A3B120346D}.201, hr = 80070057
2013-02-16 20:56:33:396 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:412 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:412 608 174c Agent WARNING: Failed to evaluate Installed rule, updateId = {A4AE4079-E11E-4320-8BBF-42B3926D1E11}.202, hr = 80070057
2013-02-16 20:56:33:427 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:427 608 174c Agent WARNING: Failed to evaluate Installable rule, updateId = {A4AE4079-E11E-4320-8BBF-42B3926D1E11}.202, hr = 80070057
2013-02-16 20:56:33:443 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:973 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:973 608 174c Agent WARNING: Failed to evaluate Installed rule, updateId = {FDA6F846-DE00-4886-8E00-8119B78CDB19}.102, hr = 80070057
2013-02-16 20:56:33:989 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:33:989 608 174c Agent WARNING: Failed to evaluate Installable rule, updateId = {FDA6F846-DE00-4886-8E00-8119B78CDB19}.102, hr = 80070057
2013-02-16 20:56:34:004 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:34:675 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:34:675 608 174c Agent WARNING: Failed to evaluate Installed rule, updateId = {2BE69C49-7C56-4F9A-8C10-86A4C94BAF8F}.102, hr = 80070057
2013-02-16 20:56:34:691 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:34:691 608 174c Agent WARNING: Failed to evaluate Installable rule, updateId = {2BE69C49-7C56-4F9A-8C10-86A4C94BAF8F}.102, hr = 80070057
2013-02-16 20:56:34:706 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:34:753 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:34:753 608 174c Agent WARNING: Failed to evaluate Installed rule, updateId = {C39FC94E-B976-41C9-8B8E-01AD700D8BE2}.104, hr = 80070057
2013-02-16 20:56:34:784 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:34:784 608 174c Agent WARNING: Failed to evaluate Installable rule, updateId = {C39FC94E-B976-41C9-8B8E-01AD700D8BE2}.104, hr = 80070057
2013-02-16 20:56:34:816 608 174c Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 20:56:37:390 608 174c Agent WARNING: Failed to evaluate Installed rule, updateId = {818701AF-1182-45C2-BD1E-17068AD171D6}.101, hr = 80242013

****************************************************************
My last comment then I'm calling it a night.....exhausted from this.....been trying to figure out for hours and hours. Anyway, I went ahead and did a UNINSTALL of KB2797052 & KB2742599. These were secutiry updates previously installed on PC. I chose them at ramdon. I then saw them show up on the available updates in Control Panel > Windows Update along with the failed KB2799494. I selected all three and the two (KB2797052 & KB2742599) installed fine....the other still failed. So, what this tells me is it seems my "system" may be OK ?......but something went wrong during the KB2799494 original install try and now it is hung....perhaps some psuedo semi install and it is lost ? Not sure how "techy" that answer is but perhaps there is a way instead of these automated "fixits" to go and search for the KB2799494 update "partials" in my system and clean those out ? Just a thought.

 

[NoelDP]

Thanks for the detail!
I think enough has happened that we need to refresh the two basic logs - please run SFC /SCANNOW and a new CheckSUR scan and post the new CBS and CheckSUR logs.

 

[thekochs]

I'm SO Frustrated on this.

Thanks for the detail!
I think enough has happened that we need to refresh the two basic logs - please run SFC /SCANNOW and a new CheckSUR scan and post the new CBS and CheckSUR logs.

OK...I ran the SURT (~10 minutes) and also the SFC /SCANNOW. I don't see any "logs" for SFC but it ran fine and said no issue when it completed. I've attached all the logs. I did re-run the KB installer over MS Updator and also using downloaded .msu.......still fails.

I have been re-reading the thread and you had asked if I intended to have System Restore off.
Yes, I use Horizon RollBack RX on all my PCs....I've found MS system restore does poor job on restore.
While you have to be careful with RX it has long/good history...been using for years.
It is a much better version of the "idea" of the old Roxio/Symantec GoBack....which bogged down your machine. It only takes snapshots of your system when you ask/schedule and you can roll back to any prior state. I use this in combo with Macrium Reflect for bare metal imaging. Unfortunately, I do not have a snapshot state prior to doing these new Feb 12th updates....I only keep few days worth at a time....keeps machine running fast. If I had been smart I would have rolled machine back prior to the original installes of the MS Updates....but not sure the issue was not there waiting for an update....but to be honest I think the issue is centered around this particular KB update. Anyway, SysRestore if turned off as part of the RX install since a system restore would be within a snapshot. The real nice thing about RX is that it has a command console that comes up prior to Windows Start....so you can opt in a roll back to a good snapshot. This is extremely usefull for a bad driver bluescreen install or even a virus removal since you can get to recovery console on boot POST prior to O/S. Also, since the physical system is the baseline and snapshots build on top of that things are firewalled for corruption. When you recover/roll to a previous snapshot you can revover files by mounting snapshots and pull some of your data files for example forward. It works very well and really allows you to try all these things...I just set a snapshot and if something we try goes wrong I roll back to the previous good point.
https://www.horizondatasys.com/products_and_solutions.aspx?ProductId=1

Lastly, I am by far no expert but sounds like "if" the log files are OK, the Fixits did not work then perhaps the origonal install attempt had an issue and things are mucked up from there. I have no idea how to fix but thought you may want to see any of the items on my PC than are referenced to KB2799494. So, did a unhide of all directories and a SEARCH for *KB2799494*.* and the PDF attached is result. I really do not want to take the system and do a bare-metal restore for few weeks back then copy back my data files since then.....that is a BIG process and since it has been a month or so since last MS Update not sure this guarantees it would resolve problem. The other is what I see as a in place update ?.....never done this but if I do this then I would need to uninstall RollBack RX since this would be a low-level operation and probably would hose RX. Thus, I could do this and take a bare-metal image but I've never been thru this process and wondering if truly needed ? Some big issues for me (show stopper) I only have a Windows Repair CD/DVD....not an O/S disc....I also am running SP1 so I would have to downgrade the system prior assuming I found a Retail disk...which I have no access too anyway since this is a OEM (HP) machine.

OK, one more item........I've done alot of digging and looks like there are two Microsoft "Fixits" for Updating.
How do I reset Windows Update components?
Automatically diagnose and fix common problems with Windows Update

Windows Update or Microsoft Update repeatedly offers the same update
Reset Windows Update components and then try updating your computer
Note This Fix it Solution has two modes: Default and Aggressive....I only ran in Default mode.

.......I ran both and fixes some things but not the Error Code 80070057.
However, the log is interesting that one of them generates....scroll almost to end.
Below is excerpt........does it indicate where issue may be ?
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installed rule, updateId = {DDFE1B13-A595-459A-BFE2-94428E47D449}.201, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installable rule, updateId = {DDFE1B13-A595-459A-BFE2-94428E47D449}.201, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installed rule, updateId = {C75D596C-1D7C-49B3-BB83-A4904BB8DBAC}.201, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installable rule, updateId = {C75D596C-1D7C-49B3-BB83-A4904BB8DBAC}.201, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installed rule, updateId = {8C01D188-A701-4F2D-BF07-5B8C3EBA763E}.200, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installable rule, updateId = {8C01D188-A701-4F2D-BF07-5B8C3EBA763E}.200, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
2013-02-16 10:47:42:414 536 de8 Agent WARNING: Failed to evaluate Installed rule, updateId = {35196586-BBFB-4A94-9B15-83A3B120346D}.201, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installable rule, updateId = {35196586-BBFB-4A94-9B15-83A3B120346D}.201, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installed rule, updateId = {A4AE4079-E11E-4320-8BBF-42B3926D1E11}.202, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installable rule, updateId = {A4AE4079-E11E-4320-8BBF-42B3926D1E11}.202, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installed rule, updateId = {FDA6F846-DE00-4886-8E00-8119B78CDB19}.102, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installable rule, updateId = {FDA6F846-DE00-4886-8E00-8119B78CDB19}.102, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installed rule, updateId = {2BE69C49-7C56-4F9A-8C10-86A4C94BAF8F}.102, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installable rule, updateId = {2BE69C49-7C56-4F9A-8C10-86A4C94BAF8F}.102, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installed rule, updateId = {C39FC94E-B976-41C9-8B8E-01AD700D8BE2}.104, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installable rule, updateId = {C39FC94E-B976-41C9-8B8E-01AD700D8BE2}.104, hr = 80070057
Handler FATAL: UH: 0x80070057: EvaluateApplicability failed in CCbs::EvaluateApplicability
Agent WARNING: Failed to evaluate Installed rule, updateId = {818701AF-1182-45C2-BD1E-17068AD171D6}.101, hr = 80242013

 

[NoelDP]

From your CBS.log

 Line 165: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778344-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 167: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778344-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 169: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778344-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 228: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778344-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 230: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778344-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 232: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778344-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 291: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778344-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 293: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778344_SP1~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778344-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 295: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778344~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778344-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 354: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2778930~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778930-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 356: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778930_SP1~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778930-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 358: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778930~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778930-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 417: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2778930~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778930-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 419: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778930_SP1~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778930-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 421: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778930~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778930-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 480: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2778930~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778930-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 482: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778930_SP1~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778930-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 484: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2778930~31bf3856ad364e35~amd64~~6.1.1.0, Update: 2778930-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 543: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2779030~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2779030-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 545: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2779030_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2779030-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 547: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2779030~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2779030-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 606: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2779030~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2779030-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 608: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2779030_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2779030-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 610: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2779030~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2779030-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 669: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2779030~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2779030-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 671: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2779030_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2779030-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 673: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2779030~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2779030-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 732: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2761226-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 734: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2761226_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2761226-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 736: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2761226-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 795: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2761226-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 797: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2761226_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2761226-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 799: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2761226-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 858: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2761226-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 860: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2761226_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2761226-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 862: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2761226~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2761226-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 921: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2731847~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2731847-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 923: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2731847_SP1~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2731847-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 925: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2731847~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2731847-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 984: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2731847~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2731847-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 986: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2731847_SP1~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2731847-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 988: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2731847~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2731847-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1047: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2731847~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2731847-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1049: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2731847_SP1~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2731847-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1051: 2013-02-17 11:08:38, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2731847~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2731847-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1120: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2718523~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2718523-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1122: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2718523_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2718523-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1124: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2718523~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2718523-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1183: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2718523~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2718523-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1185: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2718523_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2718523-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1187: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2718523~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2718523-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1246: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2718523~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2718523-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1248: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2718523_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2718523-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1250: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2718523~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2718523-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1339: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2709162~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2709162-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1341: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2709162_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2709162-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1343: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2709162~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2709162-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1402: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2709162~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2709162-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1404: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2709162_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2709162-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1406: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2709162~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2709162-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1465: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2709162~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2709162-3_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1467: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2709162_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2709162-26_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1469: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2709162~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2709162-30_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1744: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-5_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1746: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2676562_SP1~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-53_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 1748: 2013-02-17 11:08:39, Error                 CBS    Failed to check whether package is partially installed, package: Package_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3 [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 2022: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-5_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 2024: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2676562_SP1~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-53_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 2026: 2013-02-17 11:08:39, Error                 CBS    Failed to check whether package is partially installed, package: Package_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3 [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 2300: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_2_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-5_neutral_LDR [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 2302: 2013-02-17 11:08:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2676562_SP1~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2676562-53_neutral_PACKAGE [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 2304: 2013-02-17 11:08:39, Error                 CBS    Failed to check whether package is partially installed, package: Package_for_KB2676562~31bf3856ad364e35~amd64~~6.1.1.3 [HRESULT = 0x80070057 - E_INVALIDARG]
 Line 2564: 2013-02-17 11:08:42, Error                 CBS    Failed to shred identity: Microsoft-Windows-InternetExplorer-LanguagePack [HRESULT = 0x80070057 - E_INVALIDARG]

I suspect that this is caused by registry problems - but I'm not sure where, and CheckSUR is obviously not finding them.

I need to do some research!

 

[thekochs]

From your CBS.log
I suspect that this is caused by registry problems - but I'm not sure where, and CheckSUR is obviously not finding them.

I need to do some research!

I did some research and found that KB2724197 in October 2012 was another similiar security update as KB2799494.
MS12-068: Vulnerability in Windows Kernel could allow elevation of privilege: October 9, 2012
MS13-017: Vulnerabilities in Windows kernel could allow elevation of privilege: February 12, 2013
I did some digging and found out many people had problems installing it.
Unable to install Windows update KB2724197 - Help, my PC is infected! - Emsisoft Support Forums
However, most/all of these were because of a rootkit virus.
So, just to be sure I ran TDSKiller and while couple items came up a low threat they were only unsigned files. TDS said to skip and I also confirmed these files were legit.
To make double sure I re-booted into safe mode and ran MalwareBytes.....all clean.
My Avast A/V runs daily and is clean....FULL SCAN....I even did a boot time scan....all clean.
My last thing I tried was to go into the Program Files and view the update installations.
While KB2799494 was not there, obviously,.....KB2724197 was previously installed.
For grins I tried to uninstall and got an error......hmmm....went to two other machines that had no problem with all the recent updates and I could uninstall the KB2724197 there.

So, I REALLY appreciate all the help. To help I went into RegEdit and ZIP my registry.
I did an EXPORT with All Branches marked.....and zipped. Thought this might help during your registry research but the ZIP file is 32MB so cannot upload. I can put on YOUSENDIT and send you a link to download but would need your email to do so.

 

[NoelDP]

You could upload it to your SkyDrive or other favoured fileshare site and post a link - it may be interesting to see.

 

[thekochs]

You could upload it to your SkyDrive or other favoured fileshare site and post a link - it may be interesting to see.

I forgot I could create a link.. I have a YOUSENDIT account so I posted there. I'll PM you link.

 

[NoelDP]

looking at the .reg file (all 400+MB of it!), it's fairly obvious that the errors arise from the COMPONENTS registry hive - which isn't loaded.
Please zip it (C:\Windows\System3\config\COMPONENTS ) and attach it (with luck it will attach to a reply here).

 

[thekochs]

looking at the .reg file (all 400+MB of it!), it's fairly obvious that the errors arise from the COMPONENTS registry hive - which isn't loaded.
Please zip it (C:\Windows\System3\config\COMPONENTS ) and attach it (with luck it will attach to a reply here).

it's fairly obvious that the errors arise from the COMPONENTS registry hive
Glad to hear that it is obvious to you....you are now WAY beyond my tech expertise in Windows.

I zipped what I could....whden I tried to do with the config directory from itself to "send to zip" it gave me error "file not found or no read permission". I then copied the directory to MyDocs to zip....some of the files it could not copy since it says was in use by O/S. So I zipped what did copy and I also am posting a PDF pic of the C:\Windows\System32\config\ directory with it's contents. I hope the combo of the two give you insight on the exact issue.....once again, thx !!!!! The zip fiel is 11MB and looks like the limit is 8MB so I will send you another YOUSENDIT link via PM.