scansione file os windows

pcfree1

Utente Attivo
898
41
CPU
Pentium dual core G3450
Salve,

ho scansionato i file di sistema tramite il programma sfc /Scannow, e mi ha rilevato dei file danneggiati, come faccio a risolvere se non è stato in grado windows di ripararli? da cosa dipendono questi errori comunemente?
PROMPT.png

- - - Updated - - -

nessuno riesce a darmi supporto per questo problema?
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,208
6,219
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
Salve,

ho scansionato i file di sistema tramite il programma sfc /Scannow, e mi ha rilevato dei file danneggiati, come faccio a risolvere se non è stato in grado windows di ripararli? da cosa dipendono questi errori comunemente?
Visualizza allegato 197967

- - - Updated - - -

nessuno riesce a darmi supporto per questo problema?

difficile darti aiuto senza leggere il file di log...
 

pcfree1

Utente Attivo
898
41
CPU
Pentium dual core G3450
difficile darti aiuto senza leggere il file di log...

Codice:
2016-03-07 22:32:00, Info                  CSI    00005216 [SR] Verify complete
2016-03-07 22:32:00, Info                  CSI    00005217 [SR] Repairing 1 components
2016-03-07 22:32:00, Info                  CSI    00005218 [SR] Beginning Verify and Repair transaction
2016-03-07 22:32:00, Info                  CSI    00005219 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-07 22:32:00, Info                  CSI    0000521a [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
2016-03-07 22:32:00, Info                  CSI    0000521b@2016/3/7:21:32:00.814 Primitive installers committed for repair
2016-03-07 22:32:00, Info                  CSI    0000521c Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-07 22:32:00, Info                  CSI    0000521d [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
2016-03-07 22:32:00, Info                  CSI    0000521e [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"
2016-03-07 22:32:00, Info                  CSI    0000521f Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-07 22:32:00, Info                  CSI    00005220 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-07 22:32:00, Info                  CSI    00005221 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-03-07 22:32:00, Info                  CSI    00005222@2016/3/7:21:32:00.846 Primitive installers committed for repair
2016-03-07 22:32:00, Info                  CSI    00005223 [SR] Repair complete
2016-03-07 22:32:00, Info                  CSI    00005224 [SR] Committing transaction
2016-03-07 22:32:00, Info                  CSI    00005225 Creating NT transaction (seq 2), objectname [6]"(null)"
2016-03-07 22:32:00, Info                  CSI    00005226 Created NT transaction (seq 2) result 0x00000000, handle @0x460
2016-03-07 22:32:00, Info                  CSI    00005227@2016/3/7:21:32:00.894 Beginning NT transaction commit...
2016-03-07 22:32:00, Info                  CSI    00005228@2016/3/7:21:32:00.904 CSI perf trace:
CSIPERF:TXCOMMIT;11456
2016-03-07 22:32:00, Info                  CSI    00005229 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,208
6,219
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows10x64pro
Codice:
2016-03-07 22:32:00, Info                  CSI    00005216 [SR] Verify complete
2016-03-07 22:32:00, Info                  CSI    00005217 [SR] Repairing 1 components
2016-03-07 22:32:00, Info                  CSI    00005218 [SR] Beginning Verify and Repair transaction
2016-03-07 22:32:00, Info                  CSI    00005219 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-07 22:32:00, Info                  CSI    0000521a [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
2016-03-07 22:32:00, Info                  CSI    0000521b@2016/3/7:21:32:00.814 Primitive installers committed for repair
2016-03-07 22:32:00, Info                  CSI    0000521c Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-07 22:32:00, Info                  CSI    0000521d [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
2016-03-07 22:32:00, Info                  CSI    0000521e [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"
2016-03-07 22:32:00, Info                  CSI    0000521f Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-07 22:32:00, Info                  CSI    00005220 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-07 22:32:00, Info                  CSI    00005221 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-03-07 22:32:00, Info                  CSI    00005222@2016/3/7:21:32:00.846 Primitive installers committed for repair
2016-03-07 22:32:00, Info                  CSI    00005223 [SR] Repair complete
2016-03-07 22:32:00, Info                  CSI    00005224 [SR] Committing transaction
2016-03-07 22:32:00, Info                  CSI    00005225 Creating NT transaction (seq 2), objectname [6]"(null)"
2016-03-07 22:32:00, Info                  CSI    00005226 Created NT transaction (seq 2) result 0x00000000, handle @0x460
2016-03-07 22:32:00, Info                  CSI    00005227@2016/3/7:21:32:00.894 Beginning NT transaction commit...
2016-03-07 22:32:00, Info                  CSI    00005228@2016/3/7:21:32:00.904 CSI perf trace:
CSIPERF:TXCOMMIT;11456
2016-03-07 22:32:00, Info                  CSI    00005229 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

ma noti problemi di instabilità? parla solo di una dll opencl...
 

pcfree1

Utente Attivo
898
41
CPU
Pentium dual core G3450
Io sinceramente non vedo problemi gravi nel log.

beh però allora non è chiaro perché windows rilevi dei file danneggiati. Può dipendere anche da programmi installati? Che cosa succede ai file di sistema quando si iinstallano programmi non lo so...
 
M

Mursey

Ospite
In realta' non sono file danneggiati ma file che non corrispondono rispetto a quelli che lui usa come riferimento, non e' detto che sono danneggiati.
 

pcfree1

Utente Attivo
898
41
CPU
Pentium dual core G3450
In realta' non sono file danneggiati ma file che non corrispondono rispetto a quelli che lui usa come riferimento, non e' detto che sono danneggiati.

ok, ma per quale motivo un file non dovrebbe corrispondere rispetto a quello originale? Perchè viene modificato se windows non giudica corretta questa sostituzione? E' un errore dei programmatori di software o della microsoft?
 
M

Mursey

Ospite
ok, ma per quale motivo un file non dovrebbe corrispondere rispetto a quello originale? Perchè viene modificato se windows non giudica corretta questa sostituzione? E' un errore dei programmatori di software o della microsoft?

Potrebbero essere file cambiati da aggiornamenti o da rilasci di librerie c++ o simili, come anche errori durante queste operazioni.

In generale quello che conta e' il risultato finale dell'operazione e nel tuo caso dice "All files and registry keys listed in this transaction have been successfully repaired"
 

Entra

oppure Accedi utilizzando

Hot: E3 2021, chi ti è piaciuto di più?

  • Ubisoft

    Voti: 36 22.8%
  • Gearbox

    Voti: 3 1.9%
  • Xbox & Bethesda

    Voti: 101 63.9%
  • Square Enix

    Voti: 13 8.2%
  • Capcom

    Voti: 7 4.4%
  • Nintendo

    Voti: 21 13.3%
  • Altro (Specificare)

    Voti: 15 9.5%

Discussioni Simili