Windows Update failure

L

lruskin

Well-known member
Joined
Feb 19, 2015
Posts
109
Location
Arizona
This computer (Win7 Pro/64) has not applied updates in quite some time. Will not apply updates pushed by WSUS, cannot search for updates online. Get error 80070246. Have scanned for malware and rootkits, have tried various fixes. Had wanted to go back to last updates installed, remove them and see if problem was resolved, but in Control Panel/Programs, clicking on "View installed updates" returned blank.

After finding this wonderful site, I did the following: ran SFCFix, ran SURT, did Windows Update Reset as found on sevenforums. Currently attempting to run MS Fixit from kb971058; it has been stuck on "checking for updates online" for over half an now. Results as requested are below and attached:


SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-02-19 08:51:49.647
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.


AutoAnalysis::
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amÈ64_microsoft-windows-m..al-backcompat-tlb28_31bf3856ad364e35_6.A.7601.22012_none_088d5b80806913d8
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windÖws-keymgr_31bf3856ad364e35_6.1.7600.16385_none_1035859c6656c89a
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\x86_microsoft-windows-keymgr.resources_31bf3856ad364e35_6.v.7600.16385_en-us_ee31a958a16bbbad.
FIXED: Successfully repaired missing store directory C:\Windows\winsxs\x86_microsoft.vc90vatl_1fc8b3b9a1e18e3b_9.0.30729.6161_none_51cd0a7abbe4e19b.


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 2
SURT total detected corruption count: 16
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-02-19 09:03:49.909
----------------------EOF-----------------------


Thanks in advance,
Lynn
 
Hi Lynn, welcome to Sysnative. :)

One of the things we aim to do when dealing with a Windows Update thread is to consider the root cause of the problem. Unfortunately, I don't think yours was just bad luck. In actual fact, this type of corruption is typically caused by hardware failure, specifically bad RAM. To know for sure, please follow these instructions to test your RAM: Test RAM With Memtest86+ - Sysnative Forums. Memtest86+ will need to run for at least 8 passes - this will take a few hours so it's best to run it overnight.

Fortunately, RAM is one of the cheaper PC components to replace and it is often possible to return the RAM if it is fairly new. Before I can make a fix, we need to work out if it is or isn't a hardware fault and replace any failed components, otherwise the errors will continue to occur faster than I can fix them. However, if in the last couple of months you have already found and removed a failed RAM stick, then of course the above doesn't apply :)

Stephen
 
Thanks Stephen. I never considered hardware, especially not RAM. Already have memtest, will start it shortly. Good news is that system is still under warranty, not that RAM is all that expensive anyway.

Will report back to you tomorrow.
 
Stephen,
memtest ran over night and was on pass 13 when I checked it this morning. 0 errors found, so I ended the program. This system came with pre-boot diagnostics installed by manufacturer. Ran those after memtest, just completed with no errors, everything passed.

This system applied updates fine for several months then just stopped. Stopped contacting WSUS, unable to download updates from MS online. Apparently problem has existed longer than I remembered, looks like last updates were April 2013, based on what I see in WSUS report. What's interesting is that WSUS shows that the computer reported in yesterday. So maybe that is some progress.
 
Stephen, I will not be around this system until Tuesday. Any further ideas/fixes will need to wait until then. Thanks for your continued assistance! L
 
Hi,

Hmm, since Memtest is passing the next component to check is the HDD. Let's try running check disk and see what it says about the health of the drive.

chkdsk /f

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.


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    chkdsk /f
  4. Reboot
  5. Download ListChkdskResult.exe (by SleepyDude) from the link below:

    https://dl.dropboxusercontent.com/u/12354842/My Tools/ListChkdskResult.exe
  6. 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!


Stephen
 
Stephen, I haven't forgotten you. I've been ill the past few days, haven't had a chance to run this yet. Hope to get to it some time today, depending when I can get access to the system for an hour or so. I will run as requested above, but want to point out that the pre-boot system assessment I ran last week performed diagnostic testing on all hardware - HDD, RAM, optical drive, NIC, graphics card - don't have entire list in front of me and there was no way to generate a report that I saw, but there were no failures noted.
 
Stephen, first off here is chkdsk log:

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013
------< Log generate on 2/26/2015 4:38:17 PM >------
Category: 0
Computer Name: PM2013-1.haci.local
Event Code: 1001
Record Number: 157535
Source Name: Microsoft-Windows-Wininit
Time Written: 02-26-2015 @ 23:23:23
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)...
242688 file records processed.
File verification completed.
848 large file records processed.
0 bad file records processed.
2 EA records processed.
140 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
298692 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
242688 file SDs/SIDs processed.
Cleaning up 1358 unused index entries from index $SII of file 0x9.
Cleaning up 1358 unused index entries from index $SDH of file 0x9.
Cleaning up 1358 unused security descriptors.
CHKDSK is compacting the security descriptor stream
28003 data files processed.
CHKDSK is verifying Usn Journal...
36280736 USN bytes processed.
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
487571455 KB total disk space.
112112380 KB in 209014 files.
131516 KB in 28006 indexes.
0 KB in bad sectors.
359463 KB in use by the system.
65536 KB occupied by the log file.
374968096 KB available on disk.
4096 bytes in each allocation unit.
121892863 total allocation units on disk.
93742024 allocation units available on disk.
Internal Info:
00 b4 03 00 e5 9d 03 00 7a ba 06 00 00 00 00 00 ........z.......
4b 03 00 00 8c 00 00 00 00 00 00 00 00 00 00 00 K...............
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.
-----------------------------------------------------------------------


Additional info: When logging off primary user today, I noticed that there were updates to be installed. It said it installed 2 updates. So, I went back in to Windows Update and told it to check for updates manually. After 15-20 minutes it came back with the same error, 80070246. Checking the update log again, it shows the same two updates installed repeatedly today - KB2871997 and KB3011780 - 4 times each. However, even though it errored and said it could not contact the update server, those 2 updates were waiting to install on shutdown again. WSUS shows the first as installed on this system, the second as Not Applicable.
 
Just checking to make sure my responses were received, as I've not received any communication from Tekno Venus in 10 days.
 
Whoops, been really busy with school and forgot about this.

This is why I suspect hardware:

Code: 
Summary:
Seconds executed: 695
 Found 40685 errors
 Fixed 40669 errors
  CSI Could Not Open file Total count: 1
  CSI Manifest Missing Total count: 4
  CSI Catalog Missing Total count: 1
  Fixed: CSI Catalog Missing.  Total count: 1
  CSI Missing Component Key Total count: 6865
  Fixed: CSI Missing Component Key.  Total count: 6865
  CSI Missing Pinned Component Key Total count: 1155
  Fixed: CSI Missing Pinned Component Key.  Total count: 1155
  CSI Corrupt Component Keyform Total count: 1
  CSI Missing Identity Total count: 8021
  Fixed: CSI Missing Identity.  Total count: 8020
  CSI Corrupt Identity Total count: 8
  Fixed: CSI Corrupt Identity.  Total count: 2
  CSI Missing C Mark Total count: 9377
  Fixed: CSI Missing C Mark.  Total count: 9377
  CSI C Mark Deployment Missing Total count: 3
  CSI C Mark Wrong Type Total count: 1
  Fixed: CSI C Mark Wrong Type.  Total count: 1
  CSI Replacement File: CreateFile Failed Total count: 13
  CSI F Mark Missing Total count: 16403
  Fixed: CSI F Mark Missing.  Total count: 16403

Unavailable repair files:
    winsxs\manifests\woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170.manifest
    winsxs\manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest
    winsxs\manifests\amÈ64_microsoft-windows-m..al-backcompat-tlb28_31bf3856ad364e35_6.A.7601.22012_none_088d5b80806913d8.manifest
    winsxs\manifests\x86_microsoft-windows-keymgr.resources_31bf3856ad364e35_6.v.7600.16385_en-us_ee31a958a16bbbad.manifest
    winsxs\manifests\wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb.manifest

40,000+ errors do not occur by chance. The very nature of some of the corruptions (i.e bitflips) is an almost guarantee of hardware problems. Hence why I was pushing memtest so hard.

I'm going to need your COMPONENTS hive to look at.

SFCFix COMPONETS Collection


  1. Download SFCFix.exe using the following link and save the tool to your Desktop: [sfcfixdownload]Download SFCFix[/sfcfixdownload]
  2. Download SFCFixScript.txt and save this to your Desktop as well: https://dl.dropboxusercontent.com/u...eric/Collect/COMPONENTS/SFCFixScript.txt?dl=1
  3. On your Desktop, you should now see two files: SFCFix.exe and SFCFixScript.txt.
  4. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  5. SFCFix will now begin to upload your COMPONENTS hive to our server.


Stephen
 
Stephen,
Ran as instructed, you should have results. I had to run under a user with admin rights, not the regular user of this system. But, hardware is hardware so hoping that does not affect results. I can give other user admin rights and run under his login if needed. Just let me know.
 
Hi,

Thanks for that, it's perfect :)

It seems there are a few bitshifts I need to take care of:

Key: HKEY_LOCAL_MACHINE\COMPONENTS\ccpinterface
Value: Progress
Data: *�****

Key: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\am*È*64_microsoft-windows-m..al-backcompat-tlb28_31bf3856ad364e35_6.A.7601.22012_none_088d5b80806913d8
Value: identity
Data: Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-ADO-Multi-dimensional-Backcompat-Tlb28, Culture=neutral, Version=6.1.7601.22012, PublicKeyTo2en=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=*�*onSxS

Key: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non*”*_869876c170825cdb
Value: identity
Data: Micros*�*ft-Windows-Cdosys, Culture=neutral, Version=6.1.7601.17857, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=wow64, versionScope=NonSxS

Key: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wo*Ž*64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non*£*_874829ec89844170
Value: identity
Data: Micros[ft-Windows-Cdosys, Culture=neutral, Version=6.1.7601.22012, Pub*�*icKeyToken=31bf3856ad364e35, ProcessorArchitecture=wow64, versionScope=NonSxS

Key: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-keymgr.resources_31bf3856ad364e35_6.v.7600.16385_en-us_ee31a958a16bbbad
Value: S2**6H
Data: a*�****�*zf~***�*!*�*v4**k***Ӄ**�**�*5*�*Av.*�**�*r*�*X@O

Key: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-keymgr.resources_31bf3856ad364e35_6.v.7600.16385_en-us_ee31a958a16bbbad
Value: c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7601.17514*°*60259c6fd6373717
Data:

Key: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-wind*Ö*ws-keymgr_31bf3856ad364e35_6.1.7600.16385_none_1035859c6656c89a
Value: f!keymgr.d*Ž*l
Data: k*

There are a few more not in red that I can see manually, those are just the ones my tool found.

I might be able to do this tomorrow :) If not, I'm away Friday to Sunday so I'll get to it next week. Hopefully tomorrow though.

-Stephen
 
Hi lruskin,

I am really sorry for not getting back to you sooner. Stephen asked me to take a look at this one for you a few days back.

SFCFix script

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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Go to your desktop and right click on the background -> Select New -> Text Document -> Name this file SFCFixScript.txt.
  3. Open up SFCFixScript.txt and copy all of the following text inside the code box below and paste it into SFCFixScript.txt.
    Code: 
    BitShift::
  4. Click on File -> Save. Close out of SFCFixScript.txt.
  5. Save any open documents and close all open windows.
  6. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  7. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  8. SFCFix will now process the script.
  9. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  10. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Alex
 
Alex, Thanks for the next step. I'll find out when that user is headed to lunch and will get on his system then to run this. Will get back to you (hopefully within 4 hours)!
 
Alex,
Here's the resultant file.

Code: 
SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-03-13 11:05:29.540
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\networkadmin\Desktop\SFCFixScript.txt [0]
 

BitShift::
Corrupt Registry Key Detected: HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.Îc90.atl_1fc8b3b9a1e18e3b_9.0.30729.6161_51cd0a7abbe4e19b
Corrupt Registry Key Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75
Corrupt Registry Key Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amÈ64_microsoft-windows-m..al-backcompat-tlb28_31bf3856ad364e35_6.A.7601.22012_none_088d5b80806913d8
Corrupt Registry Key Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb
Corrupt Registry Key Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170
Corrupt Registry Key Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windÖws-keymgr_31bf3856ad364e35_6.1.7600.16385_none_1035859c6656c89a
Corrupt Registry Value Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-keymgr.resources_31bf3856ad364e35_6.v.7600.16385_en-us_ee31a958a16bbbad:S2?6H
Corrupt Registry Value Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-keymgr.resources_31bf3856ad364e35_6.v.7600.16385_en-us_ee31a958a16bbbad:c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7601.17514?60259c6fd6373717
Corrupt Registry Value Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windÖws-keymgr_31bf3856ad364e35_6.1.7600.16385_none_1035859c6656c89a:f!keymgr.d?l
Corrupt Registry Value Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windÖws-keymgr_31bf3856ad364e35_6.1.7600.16385_none_1035859c6656c89a:c!windowsf?undation_31bf3856ad364e35_6.1.7601.17514_615fdfe2a739474c
BitShift:: directive completed successfully.
 

Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-03-13 11:05:31.646
Script hash: hBI6Mql4H4Bclpn1EppfVE6OvuMnGbPTS9YilWvhfmA=
----------------------EOF-----------------------

Thanks!
 
Thanks, lets try and get these removed now.

SFCFix script

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.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Go to your desktop and right click on the background -> Select New -> Text Document -> Name this file SFCFixScript.txt.
  3. Open up SFCFixScript.txt and copy all of the following text inside the code box below and paste it into SFCFixScript.txt.
    Code: 
    ::
[-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.Îc90.atl_1fc8b3b9a1e18e3b_9.0.30729.6161_51cd0a7abbe4e19b]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amÈ64_microsoft-windows-m..al-backcompat-tlb28_31bf3856ad364e35_6.A.7601.22012_none_088d5b80806913d8]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-keymgr.resources_31bf3856ad364e35_6.v.7600.16385_en-us_ee31a958a16bbbad]
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windÖws-keymgr_31bf3856ad364e35_6.1.7600.16385_none_1035859c6656c89a]
  4. Click on File -> Save. Close out of SFCFixScript.txt.
  5. Save any open documents and close all open windows.
  6. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  7. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  8. SFCFix will now process the script.
  9. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  10. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Please run SURT again and post a new CheckSur.log
 
Alex,
Next round of results:
SFCFix results:

Code: 
SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-03-16 08:01:57.869
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\networkadmin\Desktop\SFCFixScript.txt [0]
 

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.Îc90.atl_1fc8b3b9a1e18e3b_9.0.30729.6161_51cd0a7abbe4e19b.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amÈ64_microsoft-windows-m..al-backcompat-tlb28_31bf3856ad364e35_6.A.7601.22012_none_088d5b80806913d8.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-keymgr.resources_31bf3856ad364e35_6.v.7600.16385_en-us_ee31a958a16bbbad.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windÖws-keymgr_31bf3856ad364e35_6.1.7600.16385_none_1035859c6656c89a.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft.Îc90.atl_1fc8b3b9a1e18e3b_9.0.30729.6161_51cd0a7abbe4e19b.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amÈ64_microsoft-windows-m..al-backcompat-tlb28_31bf3856ad364e35_6.A.7601.22012_none_088d5b80806913d8.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-keymgr.resources_31bf3856ad364e35_6.v.7600.16385_en-us_ee31a958a16bbbad.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windÖws-keymgr_31bf3856ad364e35_6.1.7600.16385_none_1035859c6656c89a.
Failed to find stored datablock for registry key -HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.
RegistryScript:: directive failed to complete successfully.
 

Failed to process all directives successfully.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2015-03-16 08:01:58.150
Script hash: HCLfepxetiSK0cQEOFrzk51n5+ZyfG5eJPSwgZPKxr0=
----------------------EOF-----------------------

And SURT, not very large file so included inline instead of attaching. Let me know if that isn't ok for next time:

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-03-16 08:03
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Corrupt Identity 0xC0000161 (not UTF8) woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170 Bad identity
(f) CSI Manifest Missing 0x00000002 woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170.manifest woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170 
(f) CSI Corrupt Identity 0xC0150016 Microsoft.VC90.ATL, Culture=neutral, Type=win32, Version=9.0.30729.6161, PublicKeyToken=1fc8b3}9a1e18e3b, ProcessorArchitecture=x86 x86_microsoft.vc90vatl_1fc8b3b9a1e18e3b_9.0.30729.6161_none_51cd0a7abbe4e19b Bad identity
(f) CSI Corrupt Identity 0x00000000 identity amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 identity and keyform do not match; identity is wrong.
(f) CSI Could Not Open file 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75 
(f) CSI Corrupt Identity 0xC0000161 (not UTF8) wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb Bad identity
(f) CSI Manifest Missing 0x00000002 wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb.manifest wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb 
Summary:
Seconds executed: 575
 Found 7 errors
  CSI Could Not Open file Total count: 1
  CSI Manifest Missing Total count: 2
  CSI Corrupt Identity Total count: 4
  CSI Replacement File: CreateFile Failed Total count: 17
Unavailable repair files:
 winsxs\manifests\woŽ64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non£_874829ec89844170.manifest
 winsxs\manifests\amd64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.22012_non_7cf37f9a55237f75.manifest
 winsxs\manifests\wow64_microsoft-windows-cdosys_31bf3856ad364e35_6.1.7601.17857_non”_869876c170825cdb.manifest

Thanks once again,
L
 
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