CSI Unable to Query Store Version Total count: 1

Everything worked perfectly. All updates installed perfect and system is rock hard once again. Thanks you NoelDP and Tom982 for the advise. I decided to chance an unsafe route to get system workable and I got lucky. I hope maybe it can help someone with this same senario, though I would not suggest doing surgery on your registry as I did.

I removed my posted .zip system logs from thread for security reasons only in my prior post.

Hello sjhonan, welcome to the forums!

You really don't want to perform that fix, it's not good at all and was very much a last resort. The COMPONENTS is a registry hive containing all the information Windows Update requires to determine whether a component needs updating or not. It is also incredibly cross linked with the files on your computer, in one of the subkeys, each registry key is the name of a manifest file on your computer so if you use another COMPONENTS hive in place of your corrupt one, they will almost certainly not line up and Windows Update will get very, very confused and will almost certainly fail with a lot more errors than you have at the moment!


If you could post your CheckSUR log and CBS log, we will be able to establish whether it's possible to fix this :)


C:\Windows\Logs\CBS\CheckSUR.persist.log
C:\Windows\Logs\CBS\CBS.log (if you get an access denied error, copy it to your Desktop first)


Zip them up and attach them to your next post please.


Tom

Hi Sheena,

You're most welcome! Us being in the same time zone really helps speed things up because whenever I help someone from the states, or anywhere else with a fair time zone difference, there really isn't that much time when both of us are online and it tends to go into a loop of one of two posts a day, then the really bad threads stretch over several weeks!


Windows Update isn't very well documented at all so it's a good job you found us! There aren't many of us who deal almost exclusively with it, I guess it's a bit of an acquired taste, or maybe no one else is mad enough to go near these thousand line logs!


Thanks for the logs! You did it all perfectly. All in all, the logs aren't pointing to any particular culprits and both have very generic errors in them. Your CBS log is full of ERROR_SXS_COMPONENT_STORE_CORRUPT errors:

Code:

2013-05-24 20:40:39, Info                  CBS    NonStart: Failed to get store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-05-24 20:40:39, Info                  CBS    Failed to ensure no startup processing was required. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-05-24 20:40:39, Info                  CBS    Failed during startup processing, continuing with Trusted Installer execution [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-05-24 20:40:39, Info                  CBS    Startup processing thread terminated normally
2013-05-24 20:40:39, Info                  CSI    00000006 No store version format found; DLL store format 0.0.0.6
2013-05-24 20:40:39, Error                 CSI    00000007@2013/5/24:19:40:39.913 (F) d:\w7rtm\base\wcp\componentstore\storelayout.cpp(6636): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::OpenCanonicalDataKey expression: (null)
[gle=0x80004005]
2013-05-24 20:40:40, Info                  CBS    Failed to get CSI store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-05-24 20:40:40, Error                 CBS    Failed to initialize store parameters with boot drive:  and windows directory:  [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-05-24 20:50:40, Info                  CBS    Reboot mark refs incremented to: 1
2013-05-24 20:50:40, Info                  CBS    Scavenge: Starts
2013-05-24 20:50:40, Info                  CSI    00000008 No store version format found; DLL store format 0.0.0.6
2013-05-24 20:50:40, Error                 CSI    00000009@2013/5/24:19:50:40.442 (F) d:\w7rtm\base\wcp\componentstore\storelayout.cpp(6636): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::OpenCanonicalDataKey expression: (null)
[gle=0x80004005]
2013-05-24 20:50:40, Info                  CBS    Scavenge: Failed to get CSI store for scavenging. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-05-24 20:50:40, Info                  CBS    Warning: Failed to scavenge CSI store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-05-24 20:50:40, Info                  CBS    Reboot mark refs: 0
2013-05-24 20:50:40, Info                  CBS    Warning: Failed while executing service idle processing. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-05-24 20:50:40, Info                  CBS    Warning: Failed to execute service idle processing. Error code: 0X80073712 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-05-24 20:50:40, Info                  CBS    Idle processing thread terminated normally
2013-05-24 20:50:40, Info                  CBS    Ending the TrustedInstaller main loop.
2013-05-24 20:50:40, Info                  CBS    Starting TrustedInstaller finalization.
2013-05-24 20:50:40, Info                  CBS    Ending TrustedInstaller finalization.

I would like you to upload your COMPONENTS hive for me please, this is where the corruption lies and I'll be able to assess the extent of the problem.


Upload a file to Dropbox


Note: If you prefer, the same techniques can be applied to your Skydrive however these instructions may not necessarily work for Skydrive.

1. If you haven't already created a Dropbox account, please do so Here
2. Although this procedure can be done directly through the website, it is much easier to do so via the Windows client which can be downloaded from the Dropbox website:
   
   
   https://www.dropbox.com/install
   
   
3. After you have downloaded and installed that, you should now see Dropbox in your Favourites box in Windows Explorer. This is the folder that will be synchronised with the Dropbox servers, anything that you wish to back up online can be put in here, but today we will be using it to transfer files.
   
   
   
   
   
   
   
4. To access your Dropbox folder, just click on the link in the top left hand corner of Windows Explorer (accessible from any location - Documents etc.). Alternatively, you can double click on the icon found in your system tray (next to the time). If you are still having issues locating this folder, unless otherwise specified, it can be found under this location: C:\Users\{Your username}\Dropbox
5. Copy all of the following files to the Public folder in your Dropbox:
   
   
   
   • C:\Windows\system32\config\components (it has no file extension)
     
     
     
     
     
     
6. Select all files by pressing Ctrl+A then right-click and select Send to > Compressed (zipped) folder
7. This will create a .zip file in your Public folder.
8. Right-click on this file and select Dropbox > Copy Public Link then Paste (Ctrl + V) this link into your next post for me please

Tom

Replies concerning the fix to this issue are as follows.
I have found no fix and I have searched exhaustedly. Apparently it is one of those event errors that is not a big deal, though it machine guns the heck out of the event logs and takes up system time and memory. I have contacted tech support and checked other forums with no fix yet. As common as this nuisance is, you would think it gets more attention and be fixed. I know ATI, aka AMD has explained it is a Windows error. I can bet calling Microsoft would give you the same answer but visa versa towards AMD as the reason. I have lived with it through 3 different cards now and it just keeps logging along. If you don't want the logs to happen with this error, shut them off in the event options log reporting. Unseen, unheard. :.)

Hi Sheena,

Fortunately that won't be the problem, it will just be hidden or something because if you were missing your system32 folder, Windows wouldn't start at all!


Command Prompt


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 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
   
   
   attrib -s -h C:\Windows\system32
   
   
   

Now see if the folder is there :)


Tom

Hi Sheena,

One more to finish it off:


Command Prompt


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 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
   
   
   attrib -s -h C:\Windows\system32\config /s
   
   
   

Tom