CBS.log error points to nonexistent folder

[Arakus]

I was looking at my CBS.log to see if my 80070002 errors were being caused by the same thing as this guy's (relevant bit after "What helped"), and it seems like it is, but the error points to a register I can't find with regedit.

Here's the error:
2015-05-21 22:13:36, Error CSI 00000029 (F) STATUS_OBJECT_NAME_NOT_FOUND #396097# from Windows::Rtl::SystemImplementation:irectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xd5d010->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[214]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-proquota.resources_31bf3856ad364e35_en-us_82e9c846a5200256\v!6.1.7600.16385"; aOBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14013400 (0x00d5d3d8))[gle=0xd0000034]

I looked in Regedit but the COMPONENTS folder and the folders inside it don't appear to exist. Help?

(NOTE: I wasn't sure where to put this thread, the mods can feel free to move it somewhere they think is more fitting.)

 

[NoelDP]

You need to load the COMPONENTS hive manually - it's only loaded by the system when required.

Open an Elevated Command Prompt, and run the following command

REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS

then try regedit again - or you can use the menu options in Regedit itself...
Highlight the HKLM Key then
File > Load Hive > C:\Windows\System32\config\COMPONENTS

 

[Arakus]

I'm not sure if this should be part of the same thread, but I was trying to keep following what the guy in that link did but couldn't get the import to work - not sure if the problem is with converting the txt file back to reg or the import itself. Regedit says it's not a reg file even though it's .reg and has the reg icon. (and yes, I saved it as "All Files")

 

[NoelDP]

upload the file - renamed as a txt file - and I'll take a look.

 

[Arakus]

Note: I get the distinct feeling from the things I'm looking up that I'm getting something really basic wrong, and the articles/threads aren't mentioning it because they assume everyone knows it. (I could be off base, this is just a nagging feeling I'm getting.)

...And after writing that I find out it's too big too attach (18MB). I'll attach a version with just the bit I've changed. I copied the replacement data from amd64_microsoft-windows-pshed.resources_31bf3856ad364e35_en-us_78bfe435c1c10417 because it had the same ...key name? (not sure if right term) inside it in regedit (v!6.1.7600.16385)

Oh, and I originally exported it to a text file just using the regedit export button, if that's important.

 

[NoelDP]

You don't have the Header in the file - and it's the wrong format.
The TXT output from Regedit is vastly different to the proper reg format.
Here's how the file should look... (Be careful, as this is NOT identical to yours!)

[SIZE=2]
Windows Registry Editor Version 5.00
 
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_microsoft-windows-proquota.resources_31bf3856ad364e35_en-us_82e9c846a5200256]
"SomeUnparsedVersionsExist"=hex:00
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_microsoft-windows-proquota.resources_31bf3856ad364e35_en-us_82e9c846a5200256\v!6.1.7600.16385]
　
[/SIZE][SIZE=2][/SIZE]

Note that you MUST have an empty line at the end.

What exactly are you trying to do - what error are you getting that makes you think this subkey is a problem?

 

[Arakus]

It's the error from the first post. (And when I try to open that register in regedit, it says "the system can't find the file specified") Also, how could I get an editable txt file in the proper reg format?

 

[NoelDP]

Export the fie from the registry in .reg format

Let's have a look at the detail of your errors.


Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

Please also post the C:\Windows\windowsudpate.log file

 

[Arakus]

I feel like an idiot for not figuring out exporting as .reg would work. Also, attached are the files you requested. I followed the rest of the steps the other guy took using said reg file and on one hand, it found an update to windows update itself it said it needed to install, but on the other hand, it then gave me a different error code when I tried to install it (800736B3). I'll research it myself, but help would be helpful.

EDIT: Just tried using the Try Again button after getting the error and it changed the code to 8024001B. Currently doing a scannow to see if that fixes anything.

 

[NoelDP]

There's no CheckSUR.log there??
There are a mess of errors in the CBS.log file - mostly repetitive - and Ican't deal with them until I see the full results from CheckSUR.

 

[Arakus]

I'm guessing from the name that CheckSUR is generated by the System Update Readiness Tool? I'm running it now. Also, when it's done, what folder does it go in?

 

[NoelDP]

The log is at C:\Windows\Logs\CBS\CheckSUR.log

 

[Arakus]

Here's the CheckSUR (and CheckSURpersist, just in case).

 

[NoelDP]

You have a number of problems with bitflips in the registry - possibly caused by bad RAM.
You need to check out the RAM using Memtest86+ http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run at least three full passes, and replace any sticks found bad.
Once that's done, post your COMPONENTS hive, and I'll see what I can do with it - but you may need to do a repair (or even a clean) install.


I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

 

[Arakus]

I think we've found the root of the problem. I have a bad RAM slot in this computer, which I used to have a card in, which I stopped using to stop a crash problem. I don't have RAM in that slot now, but I imagine the bitflips were created when it was there. Would having an empty bad RAM slot still do things? (and yes, I'm sure it's the slot and not the card I was using, I tested multiple RAM sticks in that slot and all of them made the crashing problem come back)

I'm going to edit the link to the components thing in in a bit, need to set up a fileshare account first since I don't actually have one.

EDIT: Here's the COMPONENTS hive: https://www.dropbox.com/s/7tjax2vannik78n/COMPONENTS.zip?dl=0

 

[NoelDP]

Yep - it could easily be a hangover from past problems.

Here's the detail - I'm not sure how much of it will come across in HTML, but we'll see!

Checking Component Store
(f) CSI Missing Identity 0x00000000 identity amd64{microsoät-windoWs-iis-aÄsicompaVibilityÙ31bf385ad364e3_6.1.760.16385]none_43022b0fb”c8466 
(f) CSI Could Not Open file 0x0000007B winsxs\Manifests\amd64{microsoät-windoWs-iis-aÄsicompaVibilityÙ31bf385ad364e3_6.1.760.16385]none_43022b0fb”c8466.manifest amd64{microsoät-windoWs-iis-aÄsicompaVibilityÙ31bf385ad364e3_6.1.760.16385]none_43022b0fb”c8466 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\amd64{microsoät-windoWs-iis-aÄsicompaVibilityÙ31bf385ad364e3_6.1.760.16385]none_43022b0fb”c8466.manifest amd64{microsoät-windoWs-iis-aÄsicompaVibilityÙ31bf385ad364e3_6.1.760.16385]none_43022b0fb”c8466 
(f) CSI Missing Deployment Key 0x00000000 averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_fedee0b0e2af1d43 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Identity 0x00000000 identity x86_netfx35linq-vb_compiler_oVcas_31bà3856ad364e35_6.³.7601.11514_nonG_9809beš24da2c13 
(f) CSI Could Not Open file 0x0000007B winsxs\Manifests\x86_netfx35linq-vb_compiler_oVcas_31bà3856ad364e35_6.³.7601.11514_nonG_9809beš24da2c13.manifest x86_netfx35linq-vb_compiler_oVcas_31bà3856ad364e35_6.³.7601.11514_nonG_9809beš24da2c13 
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_netfx35linq-vb_compiler_oVcas_31bà3856ad364e35_6.³.7601.11514_nonG_9809beš24da2c13.manifest x86_netfx35linq-vb_compiler_oVcas_31bà3856ad364e35_6.³.7601.11514_nonG_9809beš24da2c13 
(f) CSI C Mark Deployment Missing 0x00000000 c!win7-micros..anguagepack_31Bf3856ad564e35_7¬1.7601.—6492_6e60fb4adC23803 x86_microsoft-windows-p..age-codec.resources_31bf3856ad364e35_7.1.7601.16492_en-us_a29fc0a918aa884e 
Summary:
Seconds executed: 172
 Found 6 errors
  CSI Could Not Open file Total count: 2
  CSI Missing Deployment Key Total count: 1
  CSI Missing Identity Total count: 2
  CSI C Mark Deployment Missing Total count: 1
  CSI Replacement File: CreateFile Failed Total count: 34

 

[Arakus]

I googled around and did some ctrl-f-ing in regedit and an exported into .reg version of the COMPONENTS hive, but couldn't figure out what to do next. TBH, I'm starting to think fixing this stuff might not be worth our time since I was planning to upgrade to a new PC in a few months and... i don't know. I guess the gist of this post is that I'm not sure what to do at this point. Might do some more research later.

 

[NoelDP]

Simply COPY the file to the desktop and compress it-t hen upload it to a fileshare site (preferably either DropBox or OneDrive) and use the site tool to generate a link to the file which you can post in your response.

 

[Arakus]

Ummm... I already did that in my second last response. Are you confusing me for someone else you were helping?

 

[NoelDP]

Sorry - didn't see the edit!
I've edited out what corruption I could find, but there's still something that I'm not seeing - hopefully another run of CheckSUR on your machine with the amended hive in place will bring it out in the open.


I've uploaded a file - aksaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"]IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"]REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"]COPY "%userprofile%\desktop\aksaa\COMPONENTS" C:\Windows\System32\config[/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"] [/FONT][/COLOR]
[COLOR=black][FONT="Segoe UI"].

If you get an error with any command, STOP THERE - do not reboot! - post for instructions.

Assuming all commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.