none
scf /scannow keeps saying same message...

    Question

  • Hello,


    Windows 8.1


    DISM /Online /Cleanup-Image /RestoreHealth

    then ran scf /scannow......and says...

    Windows Resource Protection found corrupt files and successfully repaired them


    And rebooted my machine....and ran the scf command again...

    However, the same message.., which is 

    Windows Resource Protection found corrupt files and successfully repaired them...


    I thought since these were repaired first, I expected something like "Windows Resource Protection did not find any integrity violations"...However, I didn't get this one..everytime I run for scf, I always get "Windows Resource Protection found corrupt files and successfully repaired them"


    Is that something I can safely ignore? Why am I getting same "repaired" message every time? Were they actually repaired?


    This is the log...


    2018-04-19 20:29:40, Info                  CSI    00000a32 Hashes for file member \??\C:\windows\System32\invagent.dll do not match actual file [l:24{12}]"invagent.dll" :
      Found: {l:32 b:iWgm+g91Ipr1hs3jhOiZUoOUYg97OI4FcPE9W8T/m8M=} Expected: {l:32 b:VPjm/YvSezUcu8zvYdB78Ond40lUUz4bVsoagzlCreo=}
    2018-04-19 20:29:40, Info                  CSI    00000a33 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:24{12}]"invagent.dll" from store
    2018-04-19 20:29:40, Info                  CSI    00000a34 Hashes for file member \??\C:\windows\system32\wbem\aeinv.mof do not match actual file [l:18{9}]"aeinv.mof" :
      Found: {l:32 b:2XExSZoIM6M3Emva2DtGGBSahGNN2UX0qgLopQomt20=} Expected: {l:32 b:UAftWAdoZ2IUoH2ZRPYBi67+PUmaa0JDdsm2zL8M4QA=}
    2018-04-19 20:29:40, Info                  CSI    00000a35 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\windows\system32\wbem"\[l:18{9}]"aeinv.mof" from store
    2018-04-19 20:29:40, Info                  CSI    00000a36 WARNING: File [l:24{12}]"invagent.dll" in [l:46{23}]"\??\C:\windows\System32" switching ownership
        Old: Microsoft-Windows-Application-Experience-Program-Data, Version = 6.3.9600.18161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
        New: Microsoft-Windows-Application-Experience-Inventory, Version = 6.3.9600.17736, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    2018-04-19 20:29:40, Info                  CSI    00000a37 WARNING: File [l:18{9}]"aeinv.mof" in [l:56{28}]"\??\C:\windows\System32\wbem" switching ownership
        Old: Microsoft-Windows-Application-Experience-Program-Data, Version = 6.3.9600.18161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
        New: Microsoft-Windows-Application-Experience-Inventory, Version = 6.3.9600.17736, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    2018-04-19 20:29:41, Info                  CSI    00000a38 Hashes for file member \??\C:\windows\System32\invagent.dll do not match actual file [l:24{12}]"invagent.dll" :
      Found: {l:32 b:VPjm/YvSezUcu8zvYdB78Ond40lUUz4bVsoagzlCreo=} Expected: {l:32 b:iWgm+g91Ipr1hs3jhOiZUoOUYg97OI4FcPE9W8T/m8M=}
    2018-04-19 20:29:41, Info                  CSI    00000a39 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:24{12}]"invagent.dll" from store
    2018-04-19 20:29:41, Info                  CSI    00000a3a Hashes for file member \??\C:\windows\system32\wbem\aeinv.mof do not match actual file [l:18{9}]"aeinv.mof" :
      Found: {l:32 b:UAftWAdoZ2IUoH2ZRPYBi67+PUmaa0JDdsm2zL8M4QA=} Expected: {l:32 b:2XExSZoIM6M3Emva2DtGGBSahGNN2UX0qgLopQomt20=}
    2018-04-19 20:29:41, Info                  CSI    00000a3b [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\windows\system32\wbem"\[l:18{9}]"aeinv.mof" from store
    2018-04-19 20:29:41, Info                  CSI    00000a3c WARNING: File [l:24{12}]"invagent.dll" in [l:46{23}]"\??\C:\windows\System32" switching ownership
        Old: Microsoft-Windows-Application-Experience-Inventory, Version = 6.3.9600.17736, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
        New: Microsoft-Windows-Application-Experience-Program-Data, Version = 6.3.9600.18161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    2018-04-19 20:29:41, Info                  CSI    00000a3d WARNING: File [l:18{9}]"aeinv.mof" in [l:56{28}]"\??\C:\windows\System32\wbem" switching ownership
        Old: Microsoft-Windows-Application-Experience-Inventory, Version = 6.3.9600.17736, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
        New: Microsoft-Windows-Application-Experience-Program-Data, Version = 6.3.9600.18161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    2018-04-19 20:29:41, Info                  CSI    00000a3e [SR] Repair complete


    It looks like there are two files caused this one..invagent.dll  and aeinv.mof ... 


    Can I safely assume that these were actually repaired even if I didn't get "Windows Resource Protection did not find any integrity violations""?

    Any help?

    Thanks a lot in advance.

    Thursday, April 19, 2018 3:10 PM

All replies

  • From the log file, it keeps repairing invagent.dll  and aeinv.mof, I am not sure that if both of have been repaired. However, you can manually repair them.

    Here is the reference, please check 

    "How to manually replace a corrupted system file with a known good copy of the file" in the below document:

    https://support.microsoft.com/en-sg/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, April 20, 2018 2:50 AM
  • Couple of questions.

    1. Yes, I know that there is a way to replace them manually. However, this option only is viable only if I can get a good copy of files from somewhere else such as different computer, and dvd...If not, then I am out of luck..

    2. One thing I don't understand is that...the repair completed at first..then how come it was corrupted again right after booting my machine? Does this mean those are from store even corrupted? Is that why they keep copying from corrupted store? 

    Thanks,

    Friday, April 20, 2018 3:01 PM
  • Perform the following steps:

    1) Find a flash drive that you can format ( > or = 8 GB )

    2) Create a bootable Windows 10 iso:

    https://www.microsoft.com/en-us/software-download/windows10

    3) Perform an in place upgade repair with the Windows 10 iso:

    a) Power on the computer

    b) Open file explorer

    c) Insert the Windows 10 iso into any flash drive

    d) Within file explorer click on the iso and launch setup or setup.ext

    e) Follow the text and images in this thread:

    https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

    .

    .

    .

    Please remember to vote and mark the replies as answers if they help.

    .

    .

    .

    Friday, April 20, 2018 4:52 PM
  • Yes, it is possible that the source file in store is corrupted and sfc /scannow can't fix them completely even it says Complete. 

    So if you do want to repair the corrupted store source file, an in-place upgrade is a good choice.

    How to perform an in-place upgrade:

    https://support.microsoft.com/en-sg/help/2255099/how-to-perform-an-in-place-upgrade-on-windows-vista-windows-7-windows


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, April 23, 2018 1:24 AM