Windows 10: sfc/scannow cannot repair Solved


  1. Posts : 8
    Windows 10 Home, version 1511, 10586
       11 Nov 2015 #1

    sfc/scannow cannot repair


    I'm experiencing an issue with a corrupt file "close.png". It's not causing any issues with my daily activities, that I'm aware of, but while attempting to fix another issue relating to message "updater crashed" I keep running into this file saying unfixable. I've ran sfc/scannow a number of times and each time it's showing different errors that it has fixed but the same one resisting.
    2015-11-10 17:46:40, Info CSI 000030f3 [SR] Cannot repair member file [l:18{9}]"Close.png" of Microsoft-WindowsFeedback.AppxMain, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-10 17:46:53, Info CSI 00003147 [SR] Cannot repair member file [l:18{9}]"Close.png" of Microsoft-WindowsFeedback.AppxMain, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-10 18:03:12, Info CSI 0000592b [SR] Cannot repair member file [l:18{9}]"Close.png" of Microsoft-WindowsFeedback.AppxMain, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-10 18:03:13, Info CSI 0000592e [SR] Cannot repair member file [l:18{9}]"Close.png" of Microsoft-WindowsFeedback.AppxMain, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-11 14:07:07, Info CSI 000030ca [SR] Cannot repair member file [l:18{9}]"Close.png" of Microsoft-WindowsFeedback.AppxMain, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-11 14:07:17, Info CSI 00003118 [SR] Cannot repair member file [l:18{9}]"Close.png" of Microsoft-WindowsFeedback.AppxMain, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-11 14:54:14, Info CSI 00005905 [SR] Cannot repair member file [l:18{9}]"Close.png" of Microsoft-WindowsFeedback.AppxMain, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-11 14:54:15, Info CSI 00005908 [SR] Cannot repair member file [l:18{9}]"Close.png" of Microsoft-WindowsFeedback.AppxMain, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    I just included the "cannot repair". The full file will not upload due to size. I've tried "DISM.exe /Online /Cleanup-Image /Restorehealth" but without success as it says it cannot find the source. My pc originally ran windows 8.1 and upgraded to 10 via OTA update. So no disk either.
    Thank you for any help you may offer.
      My ComputerSystem Spec


  2. Posts : 1
    Dual Boot 10 Pro v1607 10 Pro rs2 build 14971
       11 Nov 2015 #2

    HI charles17, welcome to Ten Forums. This is from the tutorial forum. https://www.tenforums.com/tutorials/7...-10-image.html . There is a link in the tutorial to make a windows 10 iso to use as a source.
      My ComputerSystem Spec


  3. Posts : 8
    Windows 10 Home, version 1511, 10586
    Thread Starter
       11 Nov 2015 #3

    JohnC said: View Post
    HI charles17, welcome to Ten Forums. This is from the tutorial forum. https://www.tenforums.com/tutorials/7...-10-image.html . There is a link in the tutorial to make a windows 10 iso to use as a source.
    Thank you. I downloaded the iso, burned it to a dvd and copied the "sources" file to the c drive. I reran dism.exe and it said it was a success. I ran sfc/scannow and it had a log of 9MB. The original issue was still present. The log showed an extensive number of issues that it corrected. The log after using iso was actually larger than the log prior to using the image file.
      My ComputerSystem Spec


  4. Posts : 1
    Dual Boot 10 Pro v1607 10 Pro rs2 build 14971
       11 Nov 2015 #4

    Sometimes you need to run the SFC command three times to get it to clean up all the mess. One other thing I might add is there is going to be a update to the RTM sometime soon and that should fix the problem, (if you have the RTM). That is like an in place upgrade (repair install) which would be the next step to try if the SFC command won't fix your troubles. Just in case, and I hope you don't need it. Repair Install Windows 10 with an In-place Upgrade .
      My ComputerSystem Spec


  5. Posts : 8
    Windows 10 Home, version 1511, 10586
    Thread Starter
       12 Nov 2015 #5

    Thanks again. I ran sfsc/scannow twice more and after the second it said it did not find any integrity violations. It appears everything is fine now. Thank you for your assistance on this matter. You've been most helpful.
      My ComputerSystem Spec


  6. Posts : 1
    Dual Boot 10 Pro v1607 10 Pro rs2 build 14971
       12 Nov 2015 #6

    Glad it worked for you.
      My ComputerSystem Spec


 

Related Threads
Solved SFC /SCANNOW Error in Performance & Maintenance
When trying to run SFC /SCANNOW the following error is generated: C:\Windows\system32>sfc /scannow Windows Resource Protection could not start the repair service. Is this a knpown problem with solution?
Sfc /scannow in Performance & Maintenance
Hi I'm new to the forum When running SFC / SCANNOW I get an error message - Can someone help in fixing the issues that it refers to? "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included...
33374 What affect will these errors have on Windows 10? Are they repairable, if so, how?
This is on a new pc I bought today. Bad news! Where can I get an ISO 10240 which I can use on my external disk as a source file to repair - or where can I go for a source file? Appreciate any help. Thanks!
Greetings. After some troubble with my PC I wanted to restart in safe mode, but it can't do that. Breaks off and write something about a "hard crash", only the taskbar works, and I can also ust winkey+R and start regedit aso. Because of this I...
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 07:23.
Find Us