Windows 8 Curious : Only 8/12 updates shown on my View Installed Updates window.

davidhk129

Senior Member
After installing Ag. 12th updates, my View Installed Updates window shows only Aug 12th items. All the previous updates are gone.
Is that normal ?

Image 2.png



Correction I should say...... " my view update history shows only Aug 12th items."
 
Last edited:
Very abnormal, david. Never heard of it before. Googling the problem comes up with Zero!
 
It's getting interesting.
As I stated previously, I opened Windows Updates > clicked View Update History > only Aug 12th updates were listed. All previous updates were gone.

BUT..... I went to Programs and Features > View Installed Updates > ALL updates were listed, past and present.

What the .......
 
I'm following you on this one, David. Fascinating. If (?) you do find the reason, please post
 
It has always been the case, if something was done to clean up the Update Data, possibly metadata, the Update History listing would be cleaned, but the Installed Updates listing would remain.

I don't know if running the DSIM command would do this, but removing the SoftwareDistribution folder will show the same results.

My update history still goes back to the first of May and all updates are installed. I saw something in the WindowsUpdate.log about a request to clean up the data, but I cannot find it right now. You might check that log around the time of the change to see if it shows anything.
 
Disk Clean will not delete the update history. As far as I know, there is not a way to clean individual files in the history list, as they are all stored in a dbase.
You can find this in C:\WINDOWS\SoftwareDistribution\DataStore, called DataStore.edb

You can test this by renaming the file, say DataStore.edb.bak. You history will vanish.Of course, this does not affect the actual updates, which are still shown in the Programs and features -"View installed Updates"
 
I tried to delete the sfcdetails.txt but found no option to do so.
 

Attachments

  • sfcdetails.txt
    36.6 KB · Views: 370
Last edited:
sfc found corrupt files but unable to repair.

cbs log.posted.

I never get to learn how to read the log and do the repair myself.
If someone takes the trouble to help me, I will be most grateful.
Based on the fact that everything has been running smoothly, I must say those un-reparable corrupt files cannot be important files. I can live with that dark cloud over my head.
 

Attachments

  • CBS.log.txt
    379 KB · Views: 745
Last edited:
00000498 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

Then why did it tell me "found corrupt files but unable to repair" ?
 
Code:
2014-08-16 13:27:18, Info                  CSI    0000048e [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-08-16 13:27:19, Info                  CSI    0000048f Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_39721ee11d5bae43\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
  Found: {l:32 b:0Kws+dKgHiRLgGXZI26hkVEMo4Z55K+c24dJln/WWmA=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-08-16 13:27:19, Info                  CSI    00000490 [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch



Try running this command. Any files the SFC couldn't repair this usually does it:

Similar to the System File Checker is the DISM Tool. This will, if possible, download files to repair missing or corrupt data. Open the admin command prompt and type:
DISM /Online /Cleanup-Image /RestoreHealth
Press enter and await results.
 
As Kemical indicates, the file CNBJ2530.DPB is a file that causes the same indications for, I would guess, about 80% of folks with Windows 8. Running the DSIM command he suggests should replace that file and allow the SFC to complete.

It does seem the thread is missing some posts, not sure how it went from missing Update History entries to an SFC situation.
 
Code:
2014-08-16 13:27:18, Info                  CSI    0000048e [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-08-16 13:27:19, Info                  CSI    0000048f Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_39721ee11d5bae43\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
  Found: {l:32 b:0Kws+dKgHiRLgGXZI26hkVEMo4Z55K+c24dJln/WWmA=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-08-16 13:27:19, Info                  CSI    00000490 [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch



Try running this command. Any files the SFC couldn't repair this usually does it:

Similar to the System File Checker is the DISM Tool. This will, if possible, download files to repair missing or corrupt data. Open the admin command prompt and type:
DISM /Online /Cleanup-Image /RestoreHealth
Press enter and await results.


Thank you.
That means the repair has been successful, I presume.

Image 3.jpg
 
HOWEVER, it does not shed light on the mystery of why my View Updates History list was wiped out except Aug 12 and 13th updates.
 
RE Update history list wiped out
Is it possible that restoring the system by way of System Image Backup can accidentally delete the updates history from Software Distribution\Download folder ?

I ask this question because I did restore the system via System Image Backup ( for unrelated reason ) before I installed the Aug 12th updates.
 
Last edited:
As Kemical indicates, the file CNBJ2530.DPB is a file that causes the same indications for, I would guess, about 80% of folks with Windows 8. Running the DSIM command he suggests should replace that file and allow the SFC to complete.

It does seem the thread is missing some posts, not sure how it went from missing Update History entries to an SFC situation.

LOL. Yes. I got a bit confused when post #7 popped up!

But. Most certainly, if you restored an older system image, it would only show the updates prior to the time the image was made. Could be the sole answer to the original question
 
It still does not make sense to me.

OK. A brief story...... On Aug 11th and 12th, I was experiencing IE11 failure. IE11 would " stop working" but switching to FireFox would work fine.
I first did a browser cleanup, that did not help. So, I did a IE reset. That did not work either.
I wanted to make sure the system was working correctly first before I would install the "update 2 ".
So, I restore the system using System Image Backup done on August 10th which had all the updates I installed, up to August 10th.
After that, I installed the " August updates ".

So, you see, where are my updates prior to August 10th ?
 
Back
Top