fehlercode 0x80070032 führt zu beschädigte Dateien

Hallo,

ich wollte eine Sicherung anlegen und einen Ordner der Sicherung hinzufügen. Dann kam der fehlercode 0x80070032.

Darauf hin habe ich sfc/scannow als admin ausgeführt und folgende Nachricht zum Schluss erhalten:


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".
Hinweis: Bei der Offlinewartung wird die Protokollierung derzeit nicht unterstützt.


Darauf hin habe ich die sfcdetails.txt Datei erstellt und folgende nicht reparierbare Dateien erhalten:


2015-12-30 12:20:53, Info CSI 00003de8 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, ... pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-30 12:20:53, Info CSI 00003df1 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, ... pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-30 12:20:53, Info CSI 00003df2 [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-12-30 12:20:53, Info CSI 00003df5 [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-12-30 12:23:22, Info CSI 00004ffb [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, ... pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-30 12:23:22, Info CSI 00004ffe [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, ... pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-30 12:23:22, Info CSI 00004fff [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-12-30 12:23:22, Info CSI 00005002 [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-12-30 12:54:26, Info CSI 00003e12 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, ... pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-30 12:54:26, Info CSI 00003e1b [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, ... pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-30 12:54:26, Info CSI 00003e1c [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-12-30 12:54:26, Info CSI 00003e1f [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-12-30 12:56:51, Info CSI 00005025 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, ... pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-30 12:56:51, Info CSI 00005028 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, ... pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-12-30 12:56:51, Info CSI 00005029 [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-12-30 12:56:51, Info CSI 0000502c [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted


Was kann ich jetzt tun?

Ich habe ein surface 3 pro, welches kostenlos auf win10 geupdated wurde...


Vielen Dank für die Hilfe schon im Voraus.

LG Tobias

Weiterlesen...