Ich habe heute mal nach einer Clean-Installation von Windows 10 Prof. 64-bit das Systemdatei-Überprüfungsprogramm SFC mit "sfc /scannow" laufen lassen. Das Ergebnis war "Vom Windows-Ressourcenschutz wurden beschädigte Dateien gefunden, und einige davon konnten nicht repariert werden. Weitere Informationen finden Sie in der Datei "CBS.Log" unter "windir\Logs\CBS\CBS.log", z.B. "C:\Windows\Logs\CBS\CBS.log"."
Die Frage ist wie soll man diese Datei reparieren wenn die Datei angeblich auch in "SysWOW64" fehlerhaft ist und beide 86.528 Bytes haben.
Um das ganze noch etwas verwirrender zu machen gibt es den Dateinamen auch unter
C:\Windows\System32\DriverStore\FileRepository\rdvgwddmdx11.inf_amd64_c43edca0d0f250bb
C:\Windows\WinSxS\amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586.0_none_5fcf2a87752df0d7
mit 34.816 Bytes und als "OpenCL.DLL" unter
C:\Windows\System32
mit 82.432 Bytes. Die Datei ist von einer Firma Khronos Group Inc.
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
habe ich das Ergebnis besser sichtbar gemacht. Wenn ich das Protokoll richtig lese, dann ist nur eine Datei betroffen:
2015-11-25 22:34:47, Info CSI 000039b9 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-25 22:34:47, Info CSI 000039c3 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-25 22:34:47, Info CSI 000039c4 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2015-11-25 22:34:47, Info CSI 000039c7 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
,,,
2015-11-25 22:35:57, Info CSI 00004a10 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-25 22:35:57, Info CSI 00004a13 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-25 22:35:57, Info CSI 00004a14 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2015-11-25 22:35:57, Info CSI 00004a17 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2015-11-25 22:35:57, Info CSI 00004a19 [SR] Repair complete
2015-11-25 22:35:57, Info CSI 00004a1a [SR] Committing transaction
2015-11-25 22:35:57, Info CSI 00004a1f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
habe ich das Ergebnis besser sichtbar gemacht. Wenn ich das Protokoll richtig lese, dann ist nur eine Datei betroffen:
2015-11-25 22:34:47, Info CSI 000039b9 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-25 22:34:47, Info CSI 000039c3 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-25 22:34:47, Info CSI 000039c4 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2015-11-25 22:34:47, Info CSI 000039c7 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
,,,
2015-11-25 22:35:57, Info CSI 00004a10 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-25 22:35:57, Info CSI 00004a13 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-25 22:35:57, Info CSI 00004a14 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2015-11-25 22:35:57, Info CSI 00004a17 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2015-11-25 22:35:57, Info CSI 00004a19 [SR] Repair complete
2015-11-25 22:35:57, Info CSI 00004a1a [SR] Committing transaction
2015-11-25 22:35:57, Info CSI 00004a1f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
Um das ganze noch etwas verwirrender zu machen gibt es den Dateinamen auch unter
C:\Windows\System32\DriverStore\FileRepository\rdvgwddmdx11.inf_amd64_c43edca0d0f250bb
C:\Windows\WinSxS\amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586.0_none_5fcf2a87752df0d7
mit 34.816 Bytes und als "OpenCL.DLL" unter
C:\Windows\System32
mit 82.432 Bytes. Die Datei ist von einer Firma Khronos Group Inc.
Zuletzt bearbeitet von einem Moderator:
