Windows Updates and SFC not Working

A

AnitaHandle

Contributor
Joined
Jun 11, 2018
Posts
21
I have read reams of material and suggested fixes for my broken Windows Updates and broken "sfc /scannow"on Windows 7 Home Premium 64 bit machine. Either a faulty update
or a power failure I experienced near the beginning of April 2018 may be to blame - don't know. I keep getting "Windows Resource Protection could not start the repair. I tried an in place reinstall
from a disk I made from the Microsoft site but it couldn't continue without updates from windows - catch 22, since Windows updates doesn't work. I have an error code involving RC_Datastore error 0x8007370B.
I have renamed software distribution folders, restarted services, used elevated commands, etc., to no avail. I am at my wits end. I may end up doing a fresh install but for several reasons, I want to try to fix this problem first. Thanks​
 
Here is the results from niemiro SFCFix
I will read notes about posting log files linking to my Google Drive - please stay tuned as I have an emergency to tend to. Back in a few hours!

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-06-12 11:40:36.164
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_11.2.9600.18124_none_88<239b7fe6b124d






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








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-06-12 11:54:41.075
----------------------EOF-----------------------
 
0x8007370b : The error code I keep getting shows in this most recent partial from a cab file. Possible bit flop in "~ersionScope" (highlighted in red)

PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2018-06-12 06:43:08, Error CSI 0000001d (F) Invalid attribute name found: [l:24{12}]"~ersionScope"[gle=0x80004005]
2018-06-12 06:43:08, Error CSI 0000001e@2018/6/12:13:43:08.554 (F) d:\w7rtm\base\wcp\identity\id_baseidentity.cpp(1263): Error STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME originated in function Windows::Identity::Rtl::Implementation::CRtlIdentityBase::CRtlIdentityBase_Initialize expression: pBAI != 0
[gle=0x80004005]
2018-06-12 06:43:08, Error CSI 0000001f (F) STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME #1136667# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:312{156}]"6bee1a949<eaca11e64a1e9171624a39, Culture=neutral, Version=9.4.8112.20551, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, ~ersionScope=NonSxS")
[gle=0xd0150017]
2018-06-12 06:43:08, Info CBS Scavenge: Failed to get CSI store for scavenging. [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2018-06-12 06:43:08, Info CBS Warning: Failed to scavenge CSI store. [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2018-06-12 06:43:09, Info CBS Reboot mark refs: 0
2018-06-12 06:43:09, Info CBS Warning: Failed while executing service idle processing. [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2018-06-12 06:43:09, Info CBS Warning: Failed to execute service idle processing. Error code: 0X8007370b [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2018-06-12 06:43:09, Info CBS Idle processing thread terminated normally
2018-06-12 06:43:09, Info CBS Ending the TrustedInstaller main loop.
2018-06-12 06:43:09, Info CBS Starting TrustedInstaller finalization.
2018-06-12 06:43:10, Info CBS Ending TrustedInstaller finalization.
 
I need your CheckSUR.log as indicated in the Windows Update Posting instructions +

Retrieve Components Hive
 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload toa file sharing service and just provide the link here.
 
Thank you. Can you now run SURT again to check what errors remain? The last time you ran it, the tool has sucessfully fixed most of the errors.
 
Last edited:
Defender has no problem automatically downloading and installing its updates which always show up in installed updates.
SURT installs hotfix KB947821 and installs it AGAIN next time I run it. I don't get that part. Only Defender security updates show up in
installed windows Updates. When I run SURT tool, all I get is a duplicate KB947821.
WUD_installed2.jpg
 

Attachments

  • WUD_installed.jpg
    WUD_installed.jpg
    60.6 KB · Views: 3
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-06-13 12:13


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f) CSI Corrupt Identity 0xC0150017 6bee1a949<eaca11e64a1e9171624a39, Culture=neutral, Version=9.4.8112.20551, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, ~ersionScope=NonSxS amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764 Bad identity
(f) CSI Manifest Missing 0x00000002 amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764.manifest amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764
(f) CSI Corrupt Component Keyform 0x00000000 identity x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_11.2.9600.18124_none_88<239b7fe6b124d identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_4a20511b0dfd7d14946f4c6332ed3d74_31bf38=6ad364e35_11.2.9600.18015_none_471e3a9fb9ac04ea identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_4f608aeda651643b09e23535b297c7c5_31bf38=6ad364e35_11.2.9600.18015_none_b8635a48cd82cd0f identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_2397a474c34e90329756d8eabdf00d83_31bf3856ad364e35_11.2.9600.18015_none_f7caf56b?2259c93 identity and keyform do not match; keyform is wrong.
(f) CSI C Mark Deployment Missing 0x00000000 c!a95f17ffebf..67a9b3d14cf_31bf3856ad;64e35_10.2.9200.16736_d0ecb739f11d22ce x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_10.2.9200.16736_none_694996f444aa2e2e
(f) CSI C Mark Deployment Missing 0x00000000 c!992cdbdc808..fbe7e108878_31bf3856ad;64e35_10.2.9200.20848_43f8f6e608836c27 amd64_992cdbdc808394915a98bfbe7e108878_31bf3856ad364e35_10.2.9200.20848_none_43f8f6e600836c27
(f) CSI C Mark Deployment Missing 0x00000000 c!d84fc5a0fc3..0a0c80cf8fa_31bf3856ad;64e35_10.2.9200.20848_2a0addd96f01b048 amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_10.2.9200.20848_none_6612c379bf2c562f


Summary:
Seconds executed: 2360
Found 9 errors
CSI Manifest Missing Total count: 1
CSI Corrupt Component Keyform Total count: 4
CSI Corrupt Identity Total count: 1
CSI C Mark Deployment Missing Total count: 3


Unavailable repair files:
winsxs\manifests\amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764.manifest


(w) Unable to open Event Log 0x000006B5 Application OpenEventLog failed: 0x000006B5 - The interface is unknown.
.
(w) Unable to open Event Log 0x000006B5 System OpenEventLog failed: 0x000006B5 - The interface is unknown.
.
 
Step 1 - Replace Components Hive Manually

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 COMPONENTS.ZIP and save to your desktop.
  2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
  3. Now we have the COMPONENTS file that we will be using to replace your current one.
  4. Navigate to C:\Windows\System32\config
  5. Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  6. Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config
Afterwards, please run SURT again and attach CheckSUR.log.
 
Still having same problems. I have about 5 duplicates of KB947821, the same Windows Defender updates, and nothing else. And, SFC /scannow gives the same "Windows Resource Protection could not start repair..." error.
Here's the log:



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-06-13 20:34


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f) CSI Missing Pinned Component Key 0x00000000 amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e35_9.4.8112.20551_none_c0834074618c9764 HKLM\Components\DerivedData\Components
(fix) CSI Missing Pinned Component Key CSI Registry Item Repaired Key created. There will be more reports as values are replaced.
(f) CSI Missing Identity 0x00000000 identity amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e35_9.4.8112.20551_none_c0834074618c9764
(fix) CSI Missing Identity CSI Registry Item Repaired amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e35_9.4.8112.20551_none_c0834074618c9764
(f) CSI Corrupt Identity 0xC0150017 6bee1a949<eaca11e64a1e9171624a39, Culture=neutral, Version=9.4.8112.20551, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, ~ersionScope=NonSxS amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764 Bad identity
(f) CSI Manifest Missing 0x00000002 amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764.manifest amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764
(f) CSI Missing C Mark 0x00000000 c!6bee1a9494e..e9171624a39_31bf3856ad364e35_9.4.8112.20551_c0834074618c9764 amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e35_9.4.8112.20551_none_c0834074618c9764 Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!6bee1a9494e..e9171624a39_31bf3856ad364e35_9.4.8112.20551_c0834074618c9764 successfully added to amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e35_9.4.8112.20551_none_c0834074618c9764


Summary:
Seconds executed: 3203
Found 4 errors
Fixed 2 errors
CSI Manifest Missing Total count: 1
CSI Missing Pinned Component Key Total count: 1
Fixed: CSI Missing Pinned Component Key. Total count: 1
CSI Missing Identity Total count: 1
Fixed: CSI Missing Identity. Total count: 1
CSI Corrupt Identity Total count: 1
CSI Missing C Mark Total count: 1
Fixed: CSI Missing C Mark. Total count: 1


Unavailable repair files:
winsxs\manifests\amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764.manifest


(w) Unable to open Event Log 0x000006B5 Application OpenEventLog failed: 0x000006B5 - The interface is unknown.
.
(w) Unable to open Event Log 0x000006B5 System OpenEventLog failed: 0x000006B5 - The interface is unknown.
.
 
These fixes take time, so please be patient.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
5. Run SURT again and attach CheckSUR.log.
 

Attachments

Fixlog: (will run and post SURT log)
Fix result of Farbar Recovery Scan Tool (x64) Version: 06.06.2018 01
Ran by Owner (14-06-2018 08:48:19) Run:1
Running from C:\Users\Owner\Desktop
Loaded Profiles: Owner (Available Profiles: Owner)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764


*****************


Restore point was successfully created.


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========


The operation completed successfully.




========= End of CMD: =========


[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_6bee1a9494eaca11e64a1e9171624a39_31bf3856ad364e;5_9.4.8112.20551_none_c0834074698c9764 => could not remove. ErrorCode1: 0xC000003A


==== End of Fixlog 08:48:45 ====
 
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