SFC /Scannow Results

Be4stElectrjc · 25 Mar 2016

Have i problems in my OS?

SFC Details.txt

Evol · 25 Mar 2016

You can attempt to fix it
http://serverfault.com/questions/741487/how-to-fix-corrupted-opencl-dll-in-windows-10-if-sfc-and-dism-are-failing
These guys have the right idea

If you have a windows 10 disc or image you can basically use it to fix and replace any corrupt or broken file. Give that a try

Some times this command works
Dism /Online /Cleanup-Image /RestoreHealth

If it doesnt then i would try to restore the health with an image or a windows 10 disc

simrick · 25 Mar 2016

Be4stElectrjc said:

Have i problems in my OS?

Hi.
I see one problem in your scan:

Code:

2016-03-25 16:15:02, Info                  CSI    000026ef [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-25 16:15:03, Info                  CSI    00002728 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-25 16:15:03, Info                  CSI    00002729 [SR] This component was referenced by [l:80]"Package_1353_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.3140768-3193_neutral"
2016-03-25 16:15:03, Info                  CSI    0000272c [SR] Could not reproject corrupted file [l:78 ml:79]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC"\[l:19]"Windows Journal.lnk"; source file in store is also corrupted
2016-03-25 16:15:04, Info                  CSI    00002760 [SR] Verify complete

Have you tried the DISM tool yet?

Please post your results of:
Dism /Online /Cleanup-Image /CheckHealth -or- Dism /Online /Cleanup-Image /ScanHealth
and
Dism /Online /Cleanup-Image /RestoreHealth

Be4stElectrjc · 25 Mar 2016

simrick said:

Hi.
I see one problem in your scan:

Code:

2016-03-25 16:15:02, Info                  CSI    000026ef [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-25 16:15:03, Info                  CSI    00002728 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-25 16:15:03, Info                  CSI    00002729 [SR] This component was referenced by [l:80]"Package_1353_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.3140768-3193_neutral"
2016-03-25 16:15:03, Info                  CSI    0000272c [SR] Could not reproject corrupted file [l:78 ml:79]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC"\[l:19]"Windows Journal.lnk"; source file in store is also corrupted
2016-03-25 16:15:04, Info                  CSI    00002760 [SR] Verify complete

Have you tried the DISM tool yet?

Please post your results of:
Dism /Online /Cleanup-Image /CheckHealth -or- Dism /Online /Cleanup-Image /ScanHealth
and
Dism /Online /Cleanup-Image /RestoreHealth

Yes, i use IMAGE_HEALTH from this forum because it has all the commands i need without losing time.

No component store corruption detected. The operation completed successfully.

Used with source option and completed successfully.

In the past of my PC repair DISM = repair SFC, today not.

simrick · 25 Mar 2016

Be4stElectrjc said:

Yes, i use IMAGE_HEALTH from this forum because it has all the commands i need without losing time.

No component store corruption detected. The operation completed successfully.

Used with source option and completed successfully.

In the past of my PC repair DISM = repair SFC, today not.

I think you're okay. It's just a hash mismatch. I wouldn't worry about it, unless you start seeing updates that fail to install. You haven't moved the pointer for that journal have you?

Be4stElectrjc · 25 Mar 2016

simrick said:

I think you're okay. It's just a hash mismatch. I wouldn't worry about it, unless you start seeing updates that fail to install. You haven't moved the pointer for that journal have you?

Never touched.

simrick · 25 Mar 2016

Be4stElectrjc said:

Never touched.

Okay. I wouldn't worry about it. :)