Corrupt Windows File

[Skeltor]

So i was looking to download a new game called Hearthstone, but after i had installed and tried to play it it gave me an error saying it count write in the registry. So i went to the help link and it told me to open a command prompt and run sfc scanner. I did and followed the steps and it told me it found a corrupt file it couldn't fix. So i opened the sfc details and scrolled throught to find the corrupt files. I found this:

2014-02-26 17:53:24, Info CSI 000006da [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-02-26 17:53:27, 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-02-26 17:53:27, Info CSI 000006dd [SR] This component was referenced by [l:164{82}]"Package_86_for_KB2769165~31bf3856ad364e35~amd64~~6.2.1.0.2769165-12166_neutral_GDR"

I tried to look up a fix for the prncacla.inf file but the guide had something slightly different than what i had. I would really appreaciate help replacing the corrupted file.

 

[xilolee]

Hi skeltor! :smile9:
From an elevated command prompt, launch: dism /online /cleanup-image /restorehealth
:wave:

 

[usasma]

There's an article in the Windows Update forum that mentions these files: CNBJ2530.DPB and prncacla.inf

Have a look at it and see if it applies to you. Here's a link to it: https://www.sysnative.com/forums/wi...prncacla-inf-corruptions-windows-8-8-1-a.html

Do Repair Method 1 - it's easier than the other method and may fix things without the need for any additional work (and it shouldn't hurt anything).
xilolee's post is the first part of Method 1
The second part is to run SFC.EXE /SCANNOW again.