[SOLVED] [7SP1 x64] Security Monthly Quality Rollup 8007000D

G

Guuge

Member
Joined
Jan 22, 2018
Posts
6
For a few months I try to get this fixed already. The monthly Security Quality Rollup keeps on failing with Error 0x8007000D

OS Version: 6.1.7601.22471

SFCSCAN finds no issues

System Update Readiness Tool is installed without Errors

SFCFix ran and found issues in CBS.log

CBS Folder can be found here: https://1drv.ms/u/s!AkhQbvhX2WThgqdiEyBnXKZrKBIyjg

SFCFix Output:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-01-22 13:10:04.612
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
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: 4
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-01-22 13:11:52.772
----------------------EOF-----------------------
Click to expand...

CheckSUR.log
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-01-22 12:45

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist
(f) CBS Registry Error 0x8007000D Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23862.1.6 Enumerating child package failed, index: 0
(f) CBS Registry Error 0x8007000D Package_for_KB4025341_SP1~31bf3856ad364e35~amd64~~6.1.1.6 Enumerating child package failed, index: 1
(f) CBS Registry Error 0x8007000D Package_207_for_KB4025341~31bf3856ad364e35~amd64~~6.1.1.6 Enumerating child package failed, index: 2
(f) CBS Registry Error 0x8007000D Package_567_for_KB4025341~31bf3856ad364e35~amd64~~6.1.1.6 Enumerating child package failed, index: 3

Checking Packages

Checking Component Store

Summary:
Seconds executed: 247
Found 4 errors
CBS Registry Error Total count: 4
Click to expand...
 
Yes please, because I am still unable to install this update on my machines.
 
I see some corruption in your registry. Please do the following.

1. Download this file and save to your desktop. The file is named ExportCBSRegistry2.cmd
2. Right-click on this file and choose Run as Administrator
3. Please attach the SoftwareCBS.zip file that is on your desktop.

Thanks.
 
I found the corruption. Please do the following.

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. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. 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).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 27.01.2018
Ran by itsadmin (30-01-2018 08:17:15) Run:1
Running from C:\Temp
Loaded Profiles: itsadmin & CitrixTelemetryService (Available Profiles: itsadmin & Admin & CitrixTelemetryService)
Boot Mode: Normal
==============================================

fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-lua_31bf3856ad364e35_0.0.0.0_none_2642ee635d5318e4]
StartRegEdit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-lua_31bf3856ad364e35_0.0.0.0_none_2642ee635d5318e4]
"Package_40_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.2918614-113_neutral_LDR"="6.1.7601.22708@2"
"Package_40_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.2918614-114_neutral_LDR"="6.1.7601.22708@4"
"Package_40_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.2918614-115_neutral_GDR"="6.1.7601.18493@2"
"Package_48_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.Trigger_1"="6.1.7601.22708@@2"
"Package_78_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.Trigger_1"="6.1.7601.22708@@2"
"Package_79_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.Trigger_1"="6.1.7601.22708@@2"
"Package_40_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.3000988-113_neutral_LDR"="6.1.7601.22813@2"
"Package_40_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.3000988-114_neutral_LDR"="6.1.7601.22813@4"
"Package_40_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.3000988-115_neutral_GDR"="6.1.7601.18493@2"
"Package_41_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.Trigger_1"="6.1.7601.22813@@2"
"Package_48_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.Trigger_1"="6.1.7601.22813@@2"
"Package_78_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.Trigger_1"="6.1.7601.22813@@2"
"Package_79_for_KB3000988~31bf3856ad364e35~amd64~~6.1.1.1.Trigger_1"="6.1.7601.22813@@2"
"Package_40_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.3008627-113_neutral_LDR"="6.1.7601.22843@2"
"Package_40_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.3008627-114_neutral_LDR"="6.1.7601.22843@4"
"Package_40_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.3008627-115_neutral_GDR"="6.1.7601.18493@2"
"Package_41_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.22843@@2"
"Package_42_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.22843@@2"
"Package_78_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.22843@@2"
"Package_79_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.22843@@2"
"Package_40_for_KB3072630~31bf3856ad364e35~amd64~~6.1.1.0.3072630-113_neutral_LDR"="6.1.7601.23099@2"
"Package_40_for_KB3072630~31bf3856ad364e35~amd64~~6.1.1.0.3072630-114_neutral_LDR"="6.1.7601.23099@4"
"Package_40_for_KB3072630~31bf3856ad364e35~amd64~~6.1.1.0.3072630-115_neutral_GDR"="6.1.7601.18896@2"
"Package_41_for_KB3072630~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23099@@2"
"Package_42_for_KB3072630~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23099@@2"
"Package_78_for_KB3072630~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23099@@2"
"Package_79_for_KB3072630~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23099@@2"
"Package_40_for_KB3075249~31bf3856ad364e35~amd64~~6.1.1.0.3075249-113_neutral_LDR"="6.1.7601.23109@2"
"Package_40_for_KB3075249~31bf3856ad364e35~amd64~~6.1.1.0.3075249-114_neutral_LDR"="6.1.7601.23109@4"
"Package_40_for_KB3075249~31bf3856ad364e35~amd64~~6.1.1.0.3075249-115_neutral_GDR"="6.1.7601.18906@2"
"Package_41_for_KB3075249~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23109@@2"
"Package_77_for_KB3075249~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23109@@2"
"Package_40_for_KB3139923~31bf3856ad364e35~amd64~~6.1.1.0.3139923-113_neutral_LDR"="6.1.7601.23342@2"
"Package_40_for_KB3139923~31bf3856ad364e35~amd64~~6.1.1.0.3139923-114_neutral_LDR"="6.1.7601.23342@4"
"Package_40_for_KB3139923~31bf3856ad364e35~amd64~~6.1.1.0.3139923-115_neutral_GDR"="6.1.7601.19142@2"
"Package_41_for_KB3139923~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23342@@2"
"Package_42_for_KB3139923~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23342@@2"
"Package_78_for_KB3139923~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23342@@2"
"Package_79_for_KB3139923~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1"="6.1.7601.23342@@2"
"Package_40_for_KB3139923~31bf3856ad364e35~amd64~~6.1.2.0.3139923-39_neutral_LDR"="6.1.7601.23432@4"
"Package_101_for_KB3161608~31bf3856ad364e35~amd64~~6.1.1.1.3161608-134_neutral_LDR"="6.1.7601.23446@4"
"Package_118_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.3172605-210_neutral_LDR"="6.1.7601.23446@4"
"Package_118_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.4.3172605-210_neutral_LDR"="6.1.7601.23446@4"
"Package_68_for_KB3205394~31bf3856ad364e35~amd64~~6.1.1.3.3205394-102_neutral_LDR"="6.1.7601.23593@4"
EndRegEdit:

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-lua_31bf3856ad364e35_0.0.0.0_none_2642ee635d5318e4 => could not remove key. ErrorCode1: 0x00000002

====> Registry

==== End of Fixlog 08:17:23 ====
 
Should I delete the mentioned key manually?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-lua_31bf3856ad364e35_0.0.0.0_none_2642ee635d5318e4 => could not remove key. ErrorCode1: 0x00000002
Click to expand...
 
It did let me delete the key without any issues. I didn't even have to take ownership or anything like that. Just select and delete worked fine.
And guess what, the Windows Update installs all updates fine now! Thanks a lot!
 
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