0x800f0906 error from sfc /scannow, w8.1, cloned drive with moved recovery partition

[sixpack]

Hi, have run sfcfix.exe due to errors with corrupt files not able to be fixed under sfc /scannow . Windows 8 originally, upgraded to win8.1 last year.

New drive in notebook. this sshd Disk cloned using Macrium Reflect from previous disk (which is fine). Other partitions moved (not win8 C: partition) using Minitool Partition Wizard - recovery partition moved to "end of drive" as this disk is larger so had unallocated space at the end.

Some pc settings options in win8.1 not working but otherwise computer works just fine. Also has a small win10 partition for testing, UEFI screens allows boot choice on startup.

Hope you can help with the sfc error.View attachment dism.zipView attachment CBS.zipView attachment SFCFix.txt

thank you in advance.

 

[Aura]

Hi sixpack :)

My name is Aura and I'll be assisting you with your issue. Your CBS.log doesn't contain traces of a SFC scan, and your DISM.log doesn't contain traces of a DISM scan. As for the files reported as corrupt by SFCFix, they are false positives caused by a telemetry update on Windows. Microsoft is aware of this and disclosed it in their KB for the update.

To sum it up, there's no corrupt files that needs attention based on the logs I've seen :)

 

[sixpack]

Hi sixpack :)

My name is Aura and I'll be assisting you with your issue. Your CBS.log doesn't contain traces of a SFC scan, and your DISM.log doesn't contain traces of a DISM scan. As for the files reported as corrupt by SFCFix, they are false positives caused by a telemetry update on Windows. Microsoft is aware of this and disclosed it in their KB for the update.

To sum it up, there's no corrupt files that needs attention based on the logs I've seen :)

hi Aura, thank you for your response. I have re-run sfc scan to convince myself of my own sanity and it continues to report an issue:
>>
C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\WINDOWS\system32>
<<

I have attached the new CBS file (CBS2.zip) so I hope this helps. If it is also due to MS telemetry then that is fine but I'm not sure how to identify that.
Thank you.

 

[Aura]

SFC will continue to throw that error message because of the two false positives from the telemetry update. Also, I don't see any traces from a SFC scan in your current CBS.log.

 

[sixpack]

Hi sixpack :)

My name is Aura and I'll be assisting you with your issue. Your CBS.log doesn't contain traces of a SFC scan, and your DISM.log doesn't contain traces of a DISM scan. As for the files reported as corrupt by SFCFix, they are false positives caused by a telemetry update on Windows. Microsoft is aware of this and disclosed it in their KB for the update.

To sum it up, there's no corrupt files that needs attention based on the logs I've seen :)

hi Aura, thank you for your response. I have re-run sfc scan to convince myself of my own sanity and it continues to report an issue:
>>
C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\WINDOWS\system32>
<<

I have attached the new CBS file (CBS2.zip) so I hope this helps. If it is also due to MS telemetry then that is fine but I'm not sure how to identify that.
Thank you.

Thank you for that. The fact that you are not seeing the sfc scan in the cbs log, does that indicate a problem or something I haven't "turned on" ?

 

[Aura]

Most likely the fact that you uploaded the CBS.log too late after running the SFC scan. Since that log is very volatile, the information can disappear in a matter of minutes. Hence why we ask to upload the log right away after a scan :)