1. Joined : Oct 2014
    Arnold, MD
    Posts : 17,511
    Triple Boot 10 Pro & 10 Insider Pro & 8.1 Pro
       02 Apr 2015 #1

    SFC /SCANNOW results


    Finally in this build 10049, I can run SFC /SCANNOW completely. I've extracted just the SR results from cbs.log showing repairs, but one did not fix. Has something to do with powershell. I've rebooted and rerun 3 times, the recommended. Any thoughts?

    sfcdetails.txt
      My System SpecsSystem Spec


  2. Joined : Jul 2014
    Belo Horizonte
    Posts : 710
    Windows 10 Build 14267
       02 Apr 2015 #2

    Yeah ! It's good to see SFC working again !

      My System SpecsSystem Spec


  3. Joined : Nov 2013
    Posts : 804
    10 Pro Preview x64
       02 Apr 2015 #3

    Why do you want to run it? All this is telling you is one file doesn't match what is in the store and what is in the store is corrupt. It says:
    Could not reproject corrupted file [ml:140{70},l:138{69}]"\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\SmbShare\en-US"\[l:40{20}]"SmbLocalization.psd1"; source file in store is also corrupted
    You could repair the store by running dism. Most likely this will not work as MS haven't uploaded these versions to their servers.

    You can force dism through by specifying a /source .wim and then sfc will work. The question is whether forcing the version of SmbLocalization.psd1 that happens to be on the .wim you extract from your esd is either required or sensible.

    I think on the whole I would not bother as I know of no way to say which is correct. That's my 2c.
      My System SpecsSystem Spec


  4. Joined : Oct 2014
    Arnold, MD
    Posts : 17,511
    Triple Boot 10 Pro & 10 Insider Pro & 8.1 Pro
       02 Apr 2015 #4

    adamf said: View Post
    Why do you want to run it? All this is telling you is one file doesn't match what is in the store and what is in the store is corrupt. It says:


    You could repair the store by running dism. Most likely this will not work as MS haven't uploaded these versions to their servers.

    You can force dism through by specifying a /source .wim and then sfc will work. The question is whether forcing the version of SmbLocalization.psd1 that happens to be on the .wim you extract from your esd is either required or sensible.

    I think on the whole I would not bother as I know of no way to say which is correct. That's my 2c.
    Adam, there was no particular thing I was trying to fix. I just knew in previous builds it would not run correctly, and was just testing. I've done the DISM routine before, on 10041 using the ISO as source, but did not repair anything in store. Got the exact same results I got this time. Just wondering if the non-repairable component was anything to be concerned about. Testing only, no big deal.
      My System SpecsSystem Spec


  5. Joined : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       03 Apr 2015 #5

    f14tomcat said: View Post
    Just wondering if the non-repairable component was anything to be concerned about. Testing only, no big deal.
    SmbLocalization.psd1 is part of the language pack and these things have been an issue for most of the TP, nothing to worry about.

    The two json files, utc.app.json & telemetry.ASM-WindowsDefault.json were successfully repaired on my machine with
    Dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:<ISO mounted drive letter>:\Sources\install.wim:1 /LimitAccess

    The LimitAccess parameter just tells Dism to not use Windows Update.

    SmbLocalization was not reported on my machine, so I don't know which index of the WIM the file is located.

    Try running the Dism command with each index as the source
    wim:1
    wim:2
    wim:3
    wim:4

    Then run SFC again
      My System SpecsSystem Spec


  6. Joined : Oct 2014
    Arnold, MD
    Posts : 17,511
    Triple Boot 10 Pro & 10 Insider Pro & 8.1 Pro
       03 Apr 2015 #6

    Slartybart said: View Post
    SmbLocalization.psd1 is part of the language pack and these things have been an issue for most of the TP, nothing to worry about.

    The two json files, utc.app.json & telemetry.ASM-WindowsDefault.json were successfully repaired on my machine with
    Dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:<ISO mounted drive letter>:\Sources\install.wim:1 /LimitAccess

    The LimitAccess parameter just tells Dism to not use Windows Update.

    SmbLocalization was not reported on my machine, so I don't know which index of the WIM the file is located.

    Try running the Dism command with each index as the source
    wim:1
    wim:2
    wim:3
    wim:4

    Then run SFC again
    Thanks for the reply. Already had done the DISM and SFC and fixed same as you. This was the SR detail before I had run DISM. Only thing that was left was the SmbLocalization.psd1, so I'm not concerned a bit! It had something to do with powershell, which is fine, and I'm not running in Korean or anything but EN-US. Have a good one!
      My System SpecsSystem Spec


 


Similar Threads
Thread Forum
SFC /scannow errror
Hi, just wondering if these are anything I should try to fix or if I can just ignore them. When doing a sfc /scannow after it finished it reported this. I'm just trying to get my laptop ready for the upgrade and getting ready to clean it up and make...
Performance & Maintenance
Search Box not showing results from other hard drives
For example, my documents on on my Data drive G:, and although it is indexed documents don't show up in search. Does anyone know of a workaround for this?
General Support
Trying to do sfc/scannow via ISO image option
How to repair your system files using DISM and SFC Scannow - Microsoft Community Using technique to do an SFC scannow via ISO I have an ISO (usb) on drive L Here is what I typed in DISM /Online /Cleanup-Image /RestoreHealth...
General Support
SFC /scannow does not work - what to do??
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...
General Support
Solved SFC Scannow Results
Has anyone else run "sfc /scannow" on their system? I am receiving integrity errors but they don't seem to logged or I can't find them in the usual place.
General Support
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 16:18.
Find Us
Twitter Facebook Google+



Windows 10 Forums