Here's the detail from CheckSUR
Code:
Checking Package Watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_ec28f2d1b4aabfd4 Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-os-kernel_31bf3856ad364e35_0.0.0.0_none_900a574dfc4d4e9e Package_3_for_KB2799494~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
Checking Packages
(f) CBS Registry Error 0x80070002 Package_114_for_KB2661254~31bf3856ad364e35~amd64~~6.1.1.3 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Package_114_for_KB2661254~31bf3856ad364e35~amd64~~6.1.1.3 failed to get Visibility
...and from SFC -
Code:
Line 27825: 2014-05-19 13:19:21, Info CSI 00000338 [SR] Repairing 2 components
Line 27826: 2014-05-19 13:19:21, Info CSI 00000339 [SR] Beginning Verify and Repair transaction
Line 27829: 2014-05-19 13:19:21, Info CSI 0000033b [SR] Cannot repair member file [l:22{11}]"bootres.dll" of Microsoft-Windows-BootRes, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
Line 27832: 2014-05-19 13:19:23, Info CSI 0000033d [SR] Cannot repair member file [l:38{19}]"NlsLexicons0020.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
...and from the background CBS log data...
Code:
Line 99169: 2014-05-19 13:26:03, Error CBS Failed to create CSI transaction with id: TI5.30372743_1758105622:1/. A pending repair transaction already exists, reboot is required [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
Line 99181: 2014-05-19 13:26:03, Error CBS Failed to call external evaluate applicability on package: Package_1_for_KB2584146~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2584146-1_neutral_LDR [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
Line 99183: 2014-05-19 13:26:03, Error CBS Failed to call external evaluate applicability on package: Package_for_KB2584146_SP1~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2584146-9_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
Line 99185: 2014-05-19 13:26:03, Error CBS Failed to call external evaluate applicability on package: Package_for_KB2584146~31bf3856ad364e35~amd64~~6.1.1.3, Update: 2584146-13_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]
S
I think it's time to break the general rule about the order of repairs, and attempt to fix the SFC problems first.
With any luck this will allow the reboot to do the job it's trying to, and in the process, fix the problems showing in CheckSUR
I'll post a fix protocol (hopefully) fairly soon.