sfc /scannow problem. Windows 8.1 [Version 6.3.9600]

RMAF

New member
Joined
Apr 16, 2021
Posts
3
The other day moved C:\Users\{username}\AppData\Local to E:\Users\{username}\AppData\Local (an HDD). I found a strange behavior so I put it back in its original place. To be sure that nothing bad occurred I ran sfc /scannow.

sfc /scannow gave me the message (1) "resource protection found corrupt files and successfully repaired them". So I run it again and I got (2) "resource protection found corrupt files but was unable to fix some of them". Maybe the order was instead (2) - (1). I don't remember.

Then I tried to use DISM.exe /Online /Cleanup-image /Restorehealth, but found DISM error 193.
After some research I was able to get rid of error 193. The problem was related to the environment variables TEMP and TMP. They were pointing to the drive E:\.

Once I restore them to the original values, DISM was able to run and finished without errors.
SFCFix.exe detects no errors "SUMMARY: No corruptions were detected."
Dism++ also detects no errors.


The strange thing is that if I run sfc /scannow twice in succession it gives message (2) and then (1). So first it corrects errors, and then find them again!
I never get "Windows Resource Protection did not find any integrity violations"

The CBS.log points to some, detected corrupted, files in sub-directories of
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DSCResources\

I will attach CBS.zip and SFCFix.txt

Thanks in advance,
Rui
 

Attachments

I forgot to say that I experience no problems. Windows is running well, and no problems also with updates. Its just annoying the behavior of sfc /scannow
 
It seems that the problem is somehow related with WMF 5.1. I have updated to WMF 5.1 (KB3191564).
So I uninstalled KB3191564 and get back to WMF 4.0. Restart, run sfc /scannow and I get "Windows Resource Protection did not find any integrity violations."
Then I reinstalled WMF 5.1 and the problem described in my first post reappeared.

Could it be that the behavior is related with Language Packs? My win8.1 is en-GB. Previously I had en-US language pack installed, but now is uninstalled.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top