Windows 10: Help with SFC?

  1.    20 Dec 2016 #1

    Help with SFC?


    Okay so all day I have been trying to repair this and this is what I get

    Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.The system file repair changes will take effect after the next reboot.


    However one time I got this


    Windows Resource Protection found corrupt files and successfully repairedthem. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.The system file repair changes will take effect after the next reboot.

    I don't know anymore I have tried DISM, repair tools, etc and every time I reboot it apparently finds another thing wrong I'm at the end of my rope.

    Here is the log I notice the most



    2016-12-20 16:43:28, Info CSI 000058f7 [SR] Verify complete2016-12-20 16:43:28, Info CSI 000058f8 [SR] Repairing 1 components2016-12-20 16:43:28, Info CSI 000058f9 [SR] Beginning Verify and Repair transaction2016-12-20 16:43:28, Info CSI 000058fa Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-storport_31bf3856ad364e35_10.0.14393.351_none_61457c93ce250a47\storport.sys do not match actual file [l:12]'storport.sys' : Found: {l:32 8tM8T9aOLrSEwRjdhyKPosKv7tVfzKBiJX+/3hhMcdk=} Expected: {l:32 3veknXyJ7pwPd/kXoPtKHETUuI7Rkb4o508w2FlFhQU=}2016-12-20 16:43:28, Info CSI 000058fb [SR] Cannot repair member file [l:12]'storport.sys' of Microsoft-Windows-StorPort, version 10.0.14393.351, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch2016-12-20 16:43:28, Info CSI 000058fc@2016/12/20:21:43:28.266 Primitive installers committed for repair2016-12-20 16:43:28, Info CSI 000058fd Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-storport_31bf3856ad364e35_10.0.14393.351_none_61457c93ce250a47\storport.sys do not match actual file [l:12]'storport.sys' : Found: {l:32 8tM8T9aOLrSEwRjdhyKPosKv7tVfzKBiJX+/3hhMcdk=} Expected: {l:32 3veknXyJ7pwPd/kXoPtKHETUuI7Rkb4o508w2FlFhQU=}2016-12-20 16:43:28, Info CSI 000058fe [SR] Cannot repair member file [l:12]'storport.sys' of Microsoft-Windows-StorPort, version 10.0.14393.351, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch2016-12-20 16:43:28, Info CSI 000058ff [SR] This component was referenced by [l:80]'Package_1441_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8.3206632-2891_neutral'2016-12-20 16:43:28, Info CSI 00005900 Hashes for file member \??\C:\WINDOWS\System32\drivers\storport.sys do not match actual file [l:12]'storport.sys' : Found: {l:32 8tM8T9aOLrSEwRjdhyKPosKv7tVfzKBiJX+/3hhMcdk=} Expected: {l:32 3veknXyJ7pwPd/kXoPtKHETUuI7Rkb4o508w2FlFhQU=}2016-12-20 16:43:28, Info CSI 00005901 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-storport_31bf3856ad364e35_10.0.14393.351_none_61457c93ce250a47\storport.sys do not match actual file [l:12]'storport.sys' : Found: {l:32 8tM8T9aOLrSEwRjdhyKPosKv7tVfzKBiJX+/3hhMcdk=} Expected: {l:32 3veknXyJ7pwPd/kXoPtKHETUuI7Rkb4o508w2FlFhQU=}2016-12-20 16:43:28, Info CSI 00005902 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\drivers\storport.sys; source file in store is also corrupted2016-12-20 16:43:28, Info CSI 00005903@2016/12/20:21:43:28.328 Primitive installers committed for repair2016-12-20 16:43:28, Info CSI 00005904 [SR] Repair complete2016-12-20 16:43:28, Info CSI 00005905 [SR] Committing transaction2016-12-20 16:43:28, Info CSI 00005906 [SR] Cannot commit interactively, there are boot critical components being repaired2016-12-20 16:43:28, Info CSI 00005907 [SR] Repairing 1 components2016-12-20 16:43:28, Info CSI 00005908 [SR] Beginning Verify and Repair transaction2016-12-20 16:43:28, Info CSI 00005909 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-storport_31bf3856ad364e35_10.0.14393.351_none_61457c93ce250a47\storport.sys do not match actual file [l:12]'storport.sys' : Found: {l:32 8tM8T9aOLrSEwRjdhyKPosKv7tVfzKBiJX+/3hhMcdk=} Expected: {l:32 3veknXyJ7pwPd/kXoPtKHETUuI7Rkb4o508w2FlFhQU=}2016-12-20 16:43:28, Info CSI 0000590a [SR] Cannot repair member file [l:12]'storport.sys' of Microsoft-Windows-StorPort, version 10.0.14393.351, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch2016-12-20 16:43:28, Info CSI 0000590b@2016/12/20:21:43:28.344 Primitive installers committed for repair2016-12-20 16:43:28, Info CSI 0000590c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-storport_31bf3856ad364e35_10.0.14393.351_none_61457c93ce250a47\storport.sys do not match actual file [l:12]'storport.sys' : Found: {l:32 8tM8T9aOLrSEwRjdhyKPosKv7tVfzKBiJX+/3hhMcdk=} Expected: {l:32 3veknXyJ7pwPd/kXoPtKHETUuI7Rkb4o508w2FlFhQU=}2016-12-20 16:43:28, Info CSI 0000590d [SR] Cannot repair member file [l:12]'storport.sys' of Microsoft-Windows-StorPort, version 10.0.14393.351, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch2016-12-20 16:43:28, Info CSI 0000590e [SR] This component was referenced by [l:80]'Package_1441_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8.3206632-2891_neutral'2016-12-20 16:43:28, Info CSI 0000590f Hashes for file member \??\C:\WINDOWS\System32\drivers\storport.sys do not match actual file [l:12]'storport.sys' : Found: {l:32 8tM8T9aOLrSEwRjdhyKPosKv7tVfzKBiJX+/3hhMcdk=} Expected: {l:32 3veknXyJ7pwPd/kXoPtKHETUuI7Rkb4o508w2FlFhQU=}2016-12-20 16:43:28, Info CSI 00005910 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-storport_31bf3856ad364e35_10.0.14393.351_none_61457c93ce250a47\storport.sys do not match actual file [l:12]'storport.sys' : Found: {l:32 8tM8T9aOLrSEwRjdhyKPosKv7tVfzKBiJX+/3hhMcdk=} Expected: {l:32 3veknXyJ7pwPd/kXoPtKHETUuI7Rkb4o508w2FlFhQU=}2016-12-20 16:43:28, Info CSI 00005911 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\drivers\storport.sys; source file in store is also corrupted2016-12-20 16:43:28, Info CSI 00005912@2016/12/20:21:43:28.375 Primitive installers committed for repair2016-12-20 16:43:28, Info CSI 00005913 [SR] Repair complete2016-12-20 16:43:28, Info CSI 00005914 Creating NT transaction (seq 1), objectname '(null)'2016-12-20 16:43:28, Info CSI 00005915 Created NT transaction (seq 1) result 0x00000000, handle @0xb6c2016-12-20 16:43:28, Info CSI 00005916 Poqexec successfully registered in [l:12 ml:13]'SetupExecute'2016-12-20 16:43:28, Info CSI 00005917@2016/12/20:21:43:28.391 Beginning NT transaction commit...2016-12-20 16:43:28, Info CSI 00005918@2016/12/20:21:43:28.672 CSI perf trace:CSIPERF:TXCOMMIT;3582322016-12-20 16:43:28, Info CBS TI: CBS has signaled that a reboot is required.

    Any help would be nice, though I'm sure this is just Microsoft not being good again.
    Last edited by Barman58; 21 Dec 2016 at 18:31.
      My ComputerSystem Spec


  2. Posts : 1,755
    Windows 10 Home x64 (Laptop), Windows 10 Pro x64 (Desktop)
       21 Dec 2016 #2

    Various people on the forum have advised you may need to run sfc /scannow from an admin command prompt 3 times (with reboots between each) for sfc to report no errors. Which DISM commands have you tried to date?
      My ComputerSystem Spec

  3.    21 Dec 2016 #3

    I did the three times I believe, I will try again. As for dism, I did restore health, scan health, and check health. And they were all admin.
      My ComputerSystem Spec

  4.    21 Dec 2016 #4

    Redbatman said: View Post
    I did the three times I believe, I will try again. As for dism, I did restore health, scan health, and check health. And they were all admin.
    This may help:

    Download the ISO image for the version of Windows you currently have. You can find information on this here:

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

    Note: Mount the ISO download on your system by a right click on the file and selecting "Mount". Make note of the id of the mounted drive. The version of the ISO and the version on your system must match. You can check your running version by entering the command winver from an admin command prompt. To check the ISO version of the ISO download, run from an admin command prompt:

    dism /Get-WimInfo /WimFile:X:\sources\install.wim /index:1

    Where X is the drive you mounted for the ISO. If the versions match, then run this command from the admin command prompt:

    DISM /Online /Cleanup-Image /RestoreHealth /source:wim:X:\sources\Install.wim:1 /LimitAccess
    where X is the mounted volume for the ISO image.

    Hope this resolves your issues.
      My ComputerSystem Spec

  5.    21 Dec 2016 #5

    How do I properly mount on the desktop?
      My ComputerSystem Spec

  6.    21 Dec 2016 #6

    Asus shipped it's ASUS ZENBOOK FLIPS with corrupted images. I know I went through three of them and kept two. What I learned -- OVERSIMPLIFIED --

    1. When SFC doesn't work, DISM.
    2. When DISM doesn't work, reset PC to factory and start over.
    3. When DISM appears to work, go back to SFC and see if it's happy. If it is, fixed. If not, do DISM again and SFC again. If SFC still unhappy, reset PC to factory.
    4. Note the existence of logs but ignore content of logs unless you're good that way.

    When you FINALLY have everything working properly

    5. Create a restore point like a MOFO
      My ComputerSystem Spec


  7. Posts : 25,426
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       21 Dec 2016 #7

    Redbatman said: View Post
    How do I properly mount on the desktop?
    @Redbatman

    Right-click the ISO. If you see the option Mount at the top, click that. If you do not see Mount, click Open With and choose Explorer.
      My ComputersSystem Spec

  8.    15 Jan 2017 #8

    I just though Id give an update. So while i did try this and everything the first time it worked and SFC scan reported no issues. A few days later I had decided to another SFC scan and this time it had given me the message of that it found something and fixed it message again. So after another bit of messing around and trying to fix it again which I couldn't so I had to do restore health option to fix it some more I finally managed to relaize this.

    When ever I fix the image and do an sfc scan it thinks it had found some corrupt files and fixes them only in reality causes them to be unfixed and gives me the message that it found but could not repair corrupt files message. I'm convinced that this is a Microsoft thing and not me since ever since that cumulative update in December, I thought that the cumulative update the we got 5 days ago in Jan. 2017 would have fixed it but nope it gives the same message.

    But either way once a week I do a SFC, DISM check and now I'm starting to wonder if I should do it on a weekly basis or not. Any thoughts or ideas?
      My ComputerSystem Spec

  9.    16 Jan 2017 #9

    If you are continuously having corruption issues detected by SFC or DISM, perhaps it's time for a system restore. My advice is to back out the last update and run the SFC utility again. If it finds corrupt issues it cannot fix, run DISM as described above. If that does not correct the issue, go back another restore point and try again. If the issue is still not corrected, you may need to perform a windows repair or reinstall.
      My ComputerSystem Spec

  10.    16 Jan 2017 #10

    Here is the thing though if I do a DISM check or scan health then it gives me the message "No component store corruption detected." However if I do an SFC scan that's when I get message,

    "Windows Resource Protection found corrupt files and successfully repaired 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.The system file repair changes will take effect after the next reboot."
    So its odd but this isn't my first time with this issues since back in Feb/March of 2016 I had the same issues with a slight difference, tried the iso, sfc scan fix and it didn't not until later when the next cumulative update when things were back to normal. That's when SFC had worked.

    So yeah probably just gonna wait unless some else has an idea.
      My ComputerSystem Spec


 

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:57.
Find Us