Windows Update error: Code 80070BC9

J

jnj

Member
Joined
Jan 10, 2015
Posts
6
Hi.
I've been experiencing Windows Update errors for awhile now. I get this error: Code 80070BC9.

I'm trying to apply the Security Update for .NET Framework 3.5.1 on Windows 7 for x64-based Systems (KB2446710)

I've tried using the Windows Update troubleshooter, but that hasn't fixed the problem.

I suspect there's a registry problem of some sort, but I'm not sure how to go about cleaning up those errors.

I ran SFCFix and didn't run into any errors.

I've attached the contents of my CBS folder in two attachments (I had to break it up due to its size).

Let me know what other details I need to provide. Thanks!

-J
 
Hello and welcome to the forum.

There errors shown so far are a result of two manifest files that can no be found on your system.
Code: 
2015-01-09 03:01:26, Info                  CSI    0000001a Begin executing advanced installer phase 32 (0x00000020) index 3 (sequence 33)
    Old component: [l:0]""
    New component: [ml:350{175},l:348{174}]"Microsoft-Windows-Application-Experience-Inventory, Culture=neutral, Version=6.1.7601.18683, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {4f9da785-7ffc-4a7d-9e7e-b1a67ad8b508}
    Installer name: [12]"Directory SD"
2015-01-09 03:01:26, Info                  CSI    0000001b Performing 1 operations; 1 are not lock/unlock and follow:
  LockComponentPath (10): flags: 0 comp: {l:16 b:62c0cf77e22bd00118000000fc1cd01d} pathid: {l:16 b:62c0cf77e22bd00119000000fc1cd01d} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-a..xperience-inventory_31bf3856ad364e35_6.1.7601.18683_none_e822d0c3e5b060cb" pid: 1cfc starttime: 130652640286400578 (0x01d02be2553ce042)
2015-01-09 03:01:28, Info                  CSI    0000001c Cannot fetch manifest for Microsoft-Windows-CmiTrustInfoInstallers, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:1122334455667788}, Type neutral, TypeName neutral, PublicKey neutral, the component is not staged
2015-01-09 03:01:28, Error                 CSI    0000001d@2015/1/9:08:01:28.015 (F) d:\win7sp1_gdr\base\wcp\library\manifestcache.cpp(102): Error HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) originated in function CManifestCache::FetchManifestFromStore expression: HRESULT_FROM_WIN32(14003L)
[gle=0x80004005]
2015-01-09 03:01:28, Error                 CSI    00000001@2015/1/9:08:01:28.696 (F) CMIADAPTER: Exiting with HRESULT code = c0150004 [Error,Facility=(0015),Code=4].
[gle=0x80004005]
2015-01-09 03:01:28, Error                 CSI    0000001e@2015/1/9:08:01:28.696 (F) d:\win7sp1_gdr\base\wcp\cmiadapter\installers.cpp(123): Error c0150004 [Error,Facility=(0015),Code=4] originated in function Windows::WCP::CmiAdapter::CMIWrapperBasicInstaller::Install expression: hr
[gle=0x80004005]
2015-01-09 03:01:29, Info                  CSI    0000001f@2015/1/9:08:01:29.406 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{4f9da785-7ffc-4a7d-9e7e-b1a67ad8b508};Microsoft-Windows-Application-Experience-Inventory, Version = 6.1.7601.18683, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;3112081
2015-01-09 03:01:29, Info                  CSI    00000020 Cannot fetch manifest for Microsoft.Windows.ServicingStack.Reconfiguration.BadComponents, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, the component is not staged
2015-01-09 03:01:29, Error                 CSI    00000021@2015/1/9:08:01:29.406 (F) d:\win7sp1_gdr\base\wcp\library\manifestcache.cpp(102): Error HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) originated in function CManifestCache::FetchManifestFromStore expression: HRESULT_FROM_WIN32(14003L)
[gle=0x80004005]
2015-01-09 03:01:29, Info                  CSI    00000022 ERROR MAPPING HRESULT - No proper NTSTATUS mapping available.  Error is: "c0150004 [Error,Facility=(0015),Code=4]".

2015-01-09 03:01:29, Error                 CSI    00000023 (F) c00000e5 [Error,Facility=(0000),Code=229 (0x00e5)] #25004# from Windows::COM::CQueueExecutor::ExecuteSingle(item = Installer: Directory SD ({4f9da785-7ffc-4a7d-9e7e-b1a67ad8b508}))
[gle=0xd00000e5]
2015-01-09 03:01:29, Error                 CSI    00000024 (F) STATUS_INTERNAL_ERROR #25003# from Windows::COM::CQueueExecutor::ExecutePhase(Flags = 00000000, Progress = NULL, Phase = 32, NextIndex = 3, TotalItems = 6)
[gle=0xd00000e5]
2015-01-09 03:01:29, Error                 CSI    00000025 (F) STATUS_INTERNAL_ERROR #21803# from Windows::COM::CComponentStore::ApplyTransactionNow(...)[gle=0xd00000e5]
2015-01-09 03:01:29, Error                 CSI    00000026 (F) HRESULT_FROM_WIN32(ERROR_INTERNAL_ERROR) #21795# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Apply(...)[gle=0x8007054f]
2015-01-09 03:01:29, Error                 CSI    00000027 (F) HRESULT_FROM_WIN32(ERROR_INTERNAL_ERROR) #3233# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 102 (0x00000066), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x8007054f]
2015-01-09 03:01:29, Error                 CSI    00000028 (F) HRESULT_FROM_WIN32(ERROR_INTERNAL_ERROR) #3232# 21961442 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000066, pSink = NULL, disp = 0)
[gle=0x8007054f]
2015-01-09 03:01:29, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone
2015-01-09 03:01:29, Info                  CBS    Setting RollbackFailed flag to 0

I would like to see if we can use another tool to repair these manifest files first.

Please follow the instructions Here to run the System Update Readiness Tool. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
C:\Windows\Logs\CBS\CheckSUR.log
C:\Windows\Logs\CBS\CheckSUR.persist.log
 
Thanks so much for responding and helping out.

I ran the SURT, and got two VERY large .log files. Each is around 43 Mb! I've attached zipped versions of the log files. Apparently there were a ton of problems found and purportedly fixed. Shall I try to run my Windows update again, or do I need to take additional steps first?
 
This is the largest amount of corruptions I have ever seen on a machine!

Code: 
Summary:
Seconds executed: 1744
 Found 113524 errors
 Fixed 113524 errors

Now it may look good that all 113,524 errors were fixed. but the major concern here, is why their was that many corruptions to start off with. My first guess would either be a missing COMPONENTS registry hive or a servilely corrupt hive. My recommendation here would be to do a a fresh install of Windows or repair install of Windows at a minimum.

With this many corruptions we really have to look out hardware failure. What I recommend from here is to run some HDD diagnostics. Please follow the steps here for SeaTools HDD Diagnostics. Run a Long test and a Short test, then report back the results to this thread.

chkdsk /f scan

Warning:: This fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Warning:: Before doing anything it is a good idea to back up any data/files that are important to you, in case your hard drive is dying. Please see Here

  1. Right click on the Start button and select Run as administrator
  2. When command prompt opens, copy and paste the following commands into it, press enter after each

    chkdsk /f
  3. Reboot
  4. Download ListChkdskResult.exe (by SleepyDude) from Here
  5. Double click on it to run it. It will take a few seconds to scan, then it will open a Notepad window with the log. Copy and paste the contents of this into your next post please!

Please follow the instructions for MemTest86+, for atleast 10 passes. Let me know the results.
 
Thanks for the information. Looks like I'll have to pick up some CD-Rs for the HDD diagnostics. I'll do so and let you know the results.

Overnight, my machine was finally able to successfully update. So I'm glad to be making some progress. I'm keeping my fingers crossed that the diagnostics give my system a clean bill of health.
 
Overnight, my machine was finally able to successfully update. So I'm glad to be making some progress. I'm keeping my fingers crossed that the diagnostics give my system a clean bill of health.
Click to expand...

It is good that the updates are now installing, but with the large amount of corruptions there will most likely still be a large amount of files missing. I still recommended a fresh install or a repair install.
 
So I ran all of the tests.

The SeaTools for DOS yielded errors, but I wasn't sure where it stored its logfile(s). I'll post the results if I can find where the results are stored. If needed, I can run the SeaTools tests again.

The MemTest86+ test yielded zero errors after running more than 10 times.

The ListChkdskResults are as follows:
Code: 
ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013
------< Log generate on 1/11/2015 7:34:55 PM >------
Category: 0
Computer Name: Jones-HP
Event Code: 1001
Record Number: 203252
Source Name: Microsoft-Windows-Wininit
Time Written: 01-12-2015 @ 00:31:42
Event Type: Information
User: 
Message: 
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.                         
CHKDSK is verifying files (stage 1 of 3)...
Cleaning up instance tags for file 0x27bc4.
  551168 file records processed.                                         
File verification completed.
  1466 large file records processed.                                   
  0 bad file records processed.                                     
  0 EA records processed.                                           
  91 reparse records processed.                                      
CHKDSK is verifying indexes (stage 2 of 3)...
  672806 index entries processed.                                        
Index verification completed.
  0 unindexed files scanned.                                        
  0 unindexed files recovered.                                      
CHKDSK is verifying security descriptors (stage 3 of 3)...
  551168 file SDs/SIDs processed.                                        
Cleaning up 2112 unused index entries from index $SII of file 0x9.
Cleaning up 2112 unused index entries from index $SDH of file 0x9.
Cleaning up 2112 unused security descriptors.
Security descriptor verification completed.
  60820 data files processed.                                           
CHKDSK is verifying Usn Journal...
  33948536 USN bytes processed.                                            
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
 954083327 KB total disk space.
 296433356 KB in 488652 files.
    250624 KB in 60821 indexes.
         0 KB in bad sectors.
    684171 KB in use by the system.
     65536 KB occupied by the log file.
 656715176 KB available on disk.
      4096 bytes in each allocation unit.
 238520831 total allocation units on disk.
 164178794 allocation units available on disk.
Internal Info:
00 69 08 00 6b 62 08 00 3e f3 0e 00 00 00 00 00  .i..kb..>.......
df 28 00 00 5b 00 00 00 00 00 00 00 00 00 00 00  .(..[...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Windows has finished checking your disk.
Please wait while your computer restarts.
-----------------------------------------------------------------------
 
Go The Power said:
Those results look good.

Did all the updates install correctly?
Click to expand...

Yes, the updates installed correctly. So other than the hard-drive errors I got with the SeaTools diagnostics tests, everything seems to be running okay.
 
Go The Power said:
When you run the tool you should get the option to view the log, if you can do this and save it that would be good.
Click to expand...

So I re-ran the Long Test, and this time there were zero errors. I'm not sure why I got errors the first time but not this second time. So far everything appears to be running smoothly.

Should this topic be regarded as Solved?
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top