I have a trouble with Windows 8.1

To load Network and Sharing Center the OS is spending 2 min.

I am unable to connect with my VPN connection, which I used normally previously.

As Admnistrator in the PowerShell Terminal I tryed the following commands (also with the Windows 8.1 in the Safe Mode):

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /CheckHealth

sfc /scannow

Unfortunatelly the result was the impossibility of SFC to fix the trouble, as can be seen in its output message:

"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios."

Looking for my Log file using:

findstr /C:"[SR] Cannot repair member file" \Windows\Logs\CBS\CBS.log > \Users\NickName\Desktop\sfcdetails.txt. 

The trouble pointed by SFC looks like similar to that found in:

http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/hash-mismatch/08ef49a6-84e8-47ad-bd69-48b829d495c9 

How could I fix it? How to get a cleaned execution of sfc /scannow ?

The result in sfcdetails.txt details is:

2015-06-29 21:26:08, Info CSI 00000671 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, 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

2015-06-29 21:26:08, Info CSI 00000673 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, 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

2015-06-29 21:29:41, Info CSI 00000a43 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, 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

2015-06-29 21:29:41, Info CSI 00000a45 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, 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

The complete history follows below:

"

Windows PowerShell
Copyright (C) 2014 Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The component store is repairable.
The operation completed successfully.
PS C:\WINDOWS\system32> Dism /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

The component store is repairable.
The operation completed successfully.
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

"

• Edited by JuracyEmanuel 5 hours 56 minutes ago

I found the solution to use normally the Network in:

http://community.spiceworks.com/topic/561037-can-t-use-a-vpn-on-windows-8-1?page=1#entry-4766752

Thanks Nicholas Craig (ncraig).

However the issue in the use of SFC continues. 

• Edited by JuracyEmanuel 5 hours 58 minutes ago

Dism and sfc does not solve the trouble in which the Network and Sharing Center freeze and VPN does not connect. The origin was WAM miniport drivers pointed by DavidLW in a post at Spiceworks and solved by Nicholas Criag (ncraig) in a easy way. About the SFC message about the inability to fix corrupted files is a issue related with the "Amd64\CNBJ2530.DPB" of prncacla.inf. I have not yet obtained a cleaned execution of sfc /scannow , but my trouble with the Netowrk was fixed.