Windows 10: RE : Win 10 10586.218

I am wondering if someone else has this issue as I have.......................
Sfc reported corrupt files found but unable to repair.
I ran dism command with the Source extension.
It reported operation successful.
I ran sfc again and same report..................... corrupt files found but unable to repair.
I ran it 4 times. No change.

I don't detect any unusual behaviour in my computer. So, I don't worry too much.

I am not going to bother you people with my cbs log.
I just wonder if someone else is facing the same situation.
That's all.


:)

 

Unable to open photo app in Windows 10.

geraldsimmpkins - try settings/updates, once your in updates tap learn more. updates for win 10 version 1511, april 12, 2016 kb3147458 (os build 10586.218) is highlighted, tap it.. tommyblock

 

W10 + Miracast

Using WIN+R I get as follows:

Windows 10 Professional (x64) Version 1511 (build 10586.218)

I got the same using Belarc..

I may not deserve to be an Insider, I am 82 years old. Sorry!

 

No idea but with that CBS.log, seem like won't help much, may i see its content ?

 

Everytime you ran sfc you should reboot, then check again....other than that, no idea. could be a small bug since our last update, but sfc runs fine for me.

 

Hi.
Why don't you go ahead and run the comand
Code: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"[/quote] and we'll have a look. SFC should be working fine in 10586.

 

davidhk:

Good observation. I am on Win 10 Pro 10586.218.
Recently, I also noticed that sfc /scannow returned some errors - unable to repair corrupted files. I rerun this morning to produce a fresh listing. I noticed that:

Other than Opencl.dll which is a known problem with Nvidia driver, most of them are links.
I have no problem and Hyper-V works like a charm!
So, I just ignore them so far! May be this is a calm before the storm...*Wink

 

Interesting because I have a Nvidia card installed and after every new update, when I run sfc /scannow it finds those errors and REPAIRS them (Opencl.dll)

 

They're all hash mismatches; nothing to be concerned about I think. As long as everything is working, I wouldn't worry about it.

 

Yes, Nvidia has give me some problem. The Graphic driver works fine under Normal Windows 10. But when running with Hyper-V that is where my problem found. It took me about 2-3 months of debugging, experimentation before I narrowed it down. The version in Programs files\NVidia corporation\Opencl is version 1.2.11.0 with a file size 190KB but the version in my windows\system32 is version 1.2.11.0 with a file size of 118 KB.

Anyway, will do some more work in this area later when my work slow down a little in a few weeks! Maybe It is just a hash mismatches?

 

Yes as simrick posted does not look like anything to worry about. Besides sooner or later in one of the upcoming updates from MS this should be fixed, as MS does have this fixed from what I hear on the insider builds. *Smile