SFC error messages

These were in CBS.log.

A LOT of these:

2014-04-09 17:16:33, Info CSI 00000400 [SR]
Beginning Verify and Repair transaction
2014-04-09 17:16:41, Info CSI 00000403 [SR] Verify
complete

Then there were these:

2014-04-09 17:16:41, Info CSI 00000404 [SR]
Verifying 100 (0x0000000000000064) components
2014-04-09 17:16:41, Info CSI 00000405 [SR]
Beginning Verify and Repair transaction
2014-04-09 17:16:49, Info CSI 00000407 [SR] Cannot
repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf,
Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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-04-09 17:16:58, Info CSI 00000409 [SR] Cannot
repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf,
Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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-04-09 17:16:58, Info CSI 0000040a [SR] This
component was referenced by
[l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~ 6.2.1.0.2769165-12166_neutral_GDR"
2014-04-09 17:16:58, Info CSI 0000040b [SR] Verify
complete
2014-04-09 17:24:07, Info CSI 000006d6 [SR]
Verifying 33 (0x0000000000000021) components
2014-04-09 17:24:07, Info CSI 000006d7 [SR]
Beginning Verify and Repair transaction
2014-04-09 17:24:08, Info CSI 000006d8 [SR] Verify
complete
2014-04-09 17:24:08, Info CSI 000006d9 [SR]
Repairing 1 components
2014-04-09 17:24:08, Info CSI 000006da [SR]
Beginning Verify and Repair transaction
2014-04-09 17:24:09, Info CSI 000006dc [SR] Cannot
repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf,
Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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-04-09 17:24:09, Info CSI 000006de [SR] Cannot
repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf,
Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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-04-09 17:24:09, Info CSI 000006df [SR] This
component was referenced by
[l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~ 6.2.1.0.2769165-12166_neutral_GDR"
2014-04-09 17:24:09, Info CSI 000006e0 [SR] Repair
complete
2014-04-09 17:24:09, Info CSI 000006e1 [SR]
Committing transaction
2014-04-09 17:24:09, Info CSI 000006e6 [SR] Verify
and Repair Transaction completed. All files and registry keys listed in
this transaction have been successfully repaired


How do I fix this?

On 04/09/2014 07:18 PM, Alek Trishan wrote:
These were in CBS.log.

A LOT of these:

2014-04-09 17:16:33, Info CSI 00000400 [SR]
Beginning Verify and Repair transaction



1) Exactly what problem do you have that makes you think you need to run
SFC?


2) If your SFC repository has not been updated and it asks you to insert
your DVD to replace "corrupt" files you will do considerably more harm
than good. A great deal of your files have been updated and you may end
up replacing the updated files with older versions and corrupt your
entire system.

Alek Trishan wrote:
These were in CBS.log.

A LOT of these:

2014-04-09 17:16:33, Info CSI 00000400 [SR]
Beginning Verify and Repair transaction
2014-04-09 17:16:41, Info CSI 00000403 [SR] Verify
complete

Then there were these:

snip

Package_86_for_KB2769165


How do I fix this?

http://support.microsoft.com/kb/2769165

"An update is available for certain Microsoft files that contain
an incorrect digital signature in Windows 8 and Windows Server 2012"

"The digital signature on certain files that are produced and signed
by Microsoft expires prematurely on a computer that is running
Windows 8 and Windows Server 2012."

I have no idea how that fits into an SFC run :-(

SFC is probably using more than one source for the files
it checks against. The installer DVD is good for original files.
The folders kept when a security update comes in, perhaps
those have copies of files as well. But exactly what
SFC checks (file hash or security certificate), I'm not sure
of all the details. If it was just a file hash, a certificate
expiring would not be a problem. Whereas, if you were attempting
to install a security update with an expired certificate,
the installer would probably whine about that.

Since the KB is being references in the CBS, either that KB is
already installed, or, CBS is attempting to use that KB to fix
things. Purely a guess on my part.

*******

So I tried a search on "SFC KB2769165" and found someone with
a similar issue.

http://answers.microsoft.com/en-us/w...3-5b4b77414813

DISM /Online /Cleanup-Image /RestoreHealth

And then I suppose you'll be asking where you can find DISM :-)

http://technet.microsoft.com/en-us/l.../hh824821.aspx

"DISM is installed with Windows 8.1, and it is also
distributed in the Windows Assessment and Deployment Kit
(Windows ADK)."

The "RestoreHealth" is described here. What bothers me, is again,
what are we fixing here ? Is this actually the same thing
as SFC, or something different ?

http://technet.microsoft.com/en-us/l.../hh824869.aspx

Windows ADK is a later version of WAIK. Just with a new name.

So either you already have a "dism" on C: to use, or,
you've got a DVD to download. One or the other.

Paul

On 4/9/2014 8:36 PM, philo wrote:
On 04/09/2014 07:18 PM, Alek Trishan wrote:
These were in CBS.log.

A LOT of these:

2014-04-09 17:16:33, Info CSI 00000400 [SR]
Beginning Verify and Repair transaction



1) Exactly what problem do you have that makes you think you need to run
SFC?

It all began when I tried to install the 8.1 update. First, I could not
get in to the store because the user I was logged in to was local. So I
created a user with a MS account and I was able to download and begin
the installation.

But it failed with an 0x80070004 error.

Googling that led me to running sfc /scannow in Safe Mode (and that was
a trip and a half getting to Safe Mode!) which failed with a bunch of
stuff logged to CBS.log.


2) If your SFC repository has not been updated and it asks you to insert
your DVD to replace "corrupt" files you will do considerably more harm
than good.

I was not asked for my DVD.

On 4/9/2014 10:07 PM, Paul wrote:
Alek Trishan wrote:
These were in CBS.log.

A LOT of these:

2014-04-09 17:16:33, Info CSI 00000400 [SR]
Beginning Verify and Repair transaction
2014-04-09 17:16:41, Info CSI 00000403 [SR] Verify
complete

Then there were these:

snip

Package_86_for_KB2769165


How do I fix this?

http://support.microsoft.com/kb/2769165

"An update is available for certain Microsoft files that contain
an incorrect digital signature in Windows 8 and Windows Server 2012"

"The digital signature on certain files that are produced and signed
by Microsoft expires prematurely on a computer that is running
Windows 8 and Windows Server 2012."

I have no idea how that fits into an SFC run :-(

SFC is probably using more than one source for the files
it checks against. The installer DVD is good for original files.
The folders kept when a security update comes in, perhaps
those have copies of files as well. But exactly what
SFC checks (file hash or security certificate), I'm not sure
of all the details. If it was just a file hash, a certificate
expiring would not be a problem. Whereas, if you were attempting
to install a security update with an expired certificate,
the installer would probably whine about that.

Since the KB is being references in the CBS, either that KB is
already installed, or, CBS is attempting to use that KB to fix
things. Purely a guess on my part.

*******

So I tried a search on "SFC KB2769165" and found someone with
a similar issue.

http://answers.microsoft.com/en-us/w...3-5b4b77414813

DISM /Online /Cleanup-Image /RestoreHealth

And then I suppose you'll be asking where you can find DISM :-)

http://technet.microsoft.com/en-us/l.../hh824821.aspx

"DISM is installed with Windows 8.1, and it is also
distributed in the Windows Assessment and Deployment Kit
(Windows ADK)."

The "RestoreHealth" is described here. What bothers me, is again,
what are we fixing here ? Is this actually the same thing
as SFC, or something different ?

http://technet.microsoft.com/en-us/l.../hh824869.aspx

Windows ADK is a later version of WAIK. Just with a new name.

So either you already have a "dism" on C: to use, or,
you've got a DVD to download. One or the other.

I'll follow up in the AM. BTW, this all happened because the update to
8.1 failed.

On 04/09/2014 10:43 PM, Alek Trishan wrote:
snip

0x80070004 error



http://answers.microsoft.com/en-us/w...7-e2c182368ed7

Paul said on 4/9/2014 10:07 PM:
Alek Trishan wrote:
These were in CBS.log.

A LOT of these:

2014-04-09 17:16:33, Info CSI 00000400 [SR]
Beginning Verify and Repair transaction
2014-04-09 17:16:41, Info CSI 00000403 [SR] Verify
complete

Then there were these:

snip

Package_86_for_KB2769165


How do I fix this?

http://support.microsoft.com/kb/2769165

"An update is available for certain Microsoft files that contain
an incorrect digital signature in Windows 8 and Windows Server 2012"

"The digital signature on certain files that are produced and signed
by Microsoft expires prematurely on a computer that is running
Windows 8 and Windows Server 2012."

I have no idea how that fits into an SFC run :-(

SFC is probably using more than one source for the files
it checks against. The installer DVD is good for original files.
The folders kept when a security update comes in, perhaps
those have copies of files as well. But exactly what
SFC checks (file hash or security certificate), I'm not sure
of all the details. If it was just a file hash, a certificate
expiring would not be a problem. Whereas, if you were attempting
to install a security update with an expired certificate,
the installer would probably whine about that.

Since the KB is being references in the CBS, either that KB is
already installed, or, CBS is attempting to use that KB to fix
things. Purely a guess on my part.

*******

So I tried a search on "SFC KB2769165" and found someone with
a similar issue.

http://answers.microsoft.com/en-us/w...3-5b4b77414813


DISM /Online /Cleanup-Image /RestoreHealth

And then I suppose you'll be asking where you can find DISM :-)

http://technet.microsoft.com/en-us/l.../hh824821.aspx

"DISM is installed with Windows 8.1, and it is also
distributed in the Windows Assessment and Deployment Kit
(Windows ADK)."

The "RestoreHealth" is described here. What bothers me, is again,
what are we fixing here ? Is this actually the same thing
as SFC, or something different ?

http://technet.microsoft.com/en-us/l.../hh824869.aspx

Windows ADK is a later version of WAIK. Just with a new name.

So either you already have a "dism" on C: to use, or,
you've got a DVD to download. One or the other.

Paul



I'd just add that I too had issues with the 8.1 install and got around
to seeing the sfc /scan now suggestion and it didn't work.
The DISM Command line did work as shown above, and a 2nd SFC was
unnecessary, but I did do it. 8.1 installed clean after that.

One of lifes mysteries as how I got there, I'm pretty good at keeping
the system clean and haven't had any virus attacks, course I
install/uninstall a lot of software. Oh well, onward and upward.

On 4/10/2014 12:58 AM, philo wrote:
On 04/09/2014 10:43 PM, Alek Trishan wrote:
snip

0x80070004 error

http://answers.microsoft.com/en-us/w...7-e2c182368ed7

Wow! You're a much better googler than I am! Thanks.

On Thu, 10 Apr 2014 12:10:02 -0400, Alek Trishan wrote:

On 4/10/2014 12:58 AM, philo wrote:
On 04/09/2014 10:43 PM, Alek Trishan wrote:
snip

0x80070004 error

http://answers.microsoft.com/en-us/w...7-e2c182368ed7

Wow! You're a much better googler than I am! Thanks.

That remark reminded me of me...

I am a much better Googler than I used to be, but it became clear to me
that the improvement was with Google, not with me. And I'm still not as
good as some others I know :-)

--
Gene E. Bloch (Stumbling Bloch)