MMC Snap in Issues and SFC

G

getoffmypatch

New member
Joined
Aug 15, 2014
Posts
2
Hello -

I am new to this forum so thanks in advance for the wonderful help...

I am trying to fix a friends machine. After cleaning it up a bit I have tried to update to Win 8.1.

The update failed - at least didnt boot up after it restarted and subsequently reverted back to Win8.

After this happened I tried to review the Event log to gets specifics around what happened.

I found that the snap in for event viewer is not working and doesnt fireup.

Reading that this maybe related to .net, I have attempted to reinstall to no success.

I ran SFC /scannow and found a problem with CNBJ2530.DPB and prncacla.inf and ran SFCFix from your website.

This appeared to fix the one issue but one corruption remains according to the logs (results below)

========================================================================

FCFix version 2.3.0.0 by niemiro.
Start time: 2014-08-14 22:46:25.108
Not using a script file.








AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.2.9200.16430.






SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 1
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.3.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-08-14 23:05:54.293
Script hash:
----------------------EOF-----------------------
=======================================================================
CBS Files will follow shortly - to large to upload here

Thanks,
Shane
 
Hello Shane and welcome to the forum.

All the files appear to be fixed now from reading of the CBS logs. If you take a look at the timestamps below:

File was identified by SFC /SCANNOW

Code: 
[B][COLOR="#FF0000"]2014-08-14 22:12:20[/COLOR][/B], Info                  CSI    000006e6 Hashes for file member [B][COLOR="#0000FF"]\SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB[/COLOR][/B] do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:RHfO0sq7nkwGDJ4dRRrsanAGt1Z2njYTSu6JfFJKM14=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-08-14 22:12:20, Info                  CSI    000006e7 [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

One file was repaired by SFCFix. (this other indication that SFCFix reported was most likely a file that was repaired previously)

Code: 
SFCFix version 2.3.0.0 by niemiro.
Start time: [B][COLOR="#FF0000"]2014-08-14 22:46:25.108[/COLOR][/B]
Not using a script file.


AutoAnalysis::
FIXED: Performed DISM repair on file [COLOR="#0000FF"][B]Amd64\CNBJ2530.DPB[/B][/COLOR] of version 6.2.9200.16430.

Then it looks like the System Update Readiness was ran and repaired the following

Code: 
[B][COLOR="#FF0000"]2014-08-14 22:59:14[/COLOR][/B], Info                  CBS    
=================================
Checking System Update Readiness.

[B][COLOR="#0000FF"](p)	CSI Payload Corrupt	(Fixed)	amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16384_none_fd9c01be8b864efc\Amd64\CNBJ2530.DPB
(p)	CSI Payload Corrupt	(Fixed)	amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB
(p)	CSI Payload Corrupt	(Fixed)	amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.20531_none_fe58af2da47e1433\Amd64\CNBJ2530.DPB[/COLOR][/B]

From these indicates everything should be alright.

If you would like to double check can you please run SFC /SCANNOW again and post submit a new CBS log?

Thanks
 
Go The Power said:
Hello Shane and welcome to the forum.

All the files appear to be fixed now from reading of the CBS logs. If you take a look at the timestamps below:

File was identified by SFC /SCANNOW

Code: 
[B][COLOR=#FF0000]2014-08-14 22:12:20[/COLOR][/B], Info                  CSI    000006e6 Hashes for file member [B][COLOR=#0000FF]\SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB[/COLOR][/B] do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:RHfO0sq7nkwGDJ4dRRrsanAGt1Z2njYTSu6JfFJKM14=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-08-14 22:12:20, Info                  CSI    000006e7 [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

One file was repaired by SFCFix. (this other indication that SFCFix reported was most likely a file that was repaired previously)

Code: 
SFCFix version 2.3.0.0 by niemiro.
Start time: [B][COLOR=#FF0000]2014-08-14 22:46:25.108[/COLOR][/B]
Not using a script file.


AutoAnalysis::
FIXED: Performed DISM repair on file [COLOR=#0000FF][B]Amd64\CNBJ2530.DPB[/B][/COLOR] of version 6.2.9200.16430.

Then it looks like the System Update Readiness was ran and repaired the following

Code: 
[B][COLOR=#FF0000]2014-08-14 22:59:14[/COLOR][/B], Info                  CBS    
=================================
Checking System Update Readiness.

[B][COLOR=#0000FF](p)    CSI Payload Corrupt    (Fixed)    amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16384_none_fd9c01be8b864efc\Amd64\CNBJ2530.DPB
(p)    CSI Payload Corrupt    (Fixed)    amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\Amd64\CNBJ2530.DPB
(p)    CSI Payload Corrupt    (Fixed)    amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.20531_none_fe58af2da47e1433\Amd64\CNBJ2530.DPB[/COLOR][/B]

From these indicates everything should be alright.

If you would like to double check can you please run SFC /SCANNOW again and post submit a new CBS log?

Thanks
Click to expand...

Thanks - Im running that now. Any ideas on why the Event viewer wont open/load?
 
Do you get an error message from trying to launch event log?

Are you able to open other MMC Snap In? For example Task Scheduler, Component Services etc
 
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