Share via

sfc scan fixes errors - or not?

Anonymous
2020-06-27T11:05:37+00:00

windows 10 pro 19041.329  (version 2004)

windows started acting wonky on me necessitating a cold reset of the system, whether this was due to windows being windows, or due to system corruption, i wasn't sure. so i ran SFC /scannow to check my files, and each time i ran it, it said files were repaired. curious as too which files were fixed (or not, in this case?) I checked out the cbs.log. every run of listed two files as having a hash mismatch, which it proceeded to fix, but the files in the store, apparently  either contained the same issue or sfc was generating a false alarm. the files were 'c:\windows\syswow64\srmclient.dll' and 'c:\windows\syswow64\srmscan.dll'. I don't have any information on these files, and trying to google them returned so much garbage search results I gave up almost immediately.

does anyone here have any info on those two files or why they are listed as having an issue SFC?

cbs.log extract:

2020-06-27 03:44:20, Info                  CSI    00000698 Hashes for file member [l:13]'srmclient.dll' do not match.

 Expected: {l:32 ml:33 b:1b0b86b04dabba626b22a0a289186d219cb5290e9815f1bc69bc890b0920bf40}.

 Actual: {l:32 b:5e2a5d7dcf32648190d5cc2109aaec9a4e30a37df6b34b0b94cac041c3884474}.

2020-06-27 03:44:20, Info                  CSI    00000699 [SR] Repairing file ??\C:\WINDOWS\SysWOW64\srmclient.dll from store

2020-06-27 03:44:20, Info                  CSI    0000069a Hashes for file member [l:11]'srmscan.dll' do not match.

 Expected: {l:32 ml:33 b:22cd02ec611d7ed212ee86f7ab90979408c405c353a22123b84420e4db93f501}.

 Actual: {l:32 b:1de1a66fafd5a82c62722a3b6879b3804164a87cffae6963205ea7637439231f}.

2020-06-27 03:44:20, Info                  CSI    0000069b [SR] Repairing file ??\C:\WINDOWS\SysWOW64\srmscan.dll from store

I am more than capable of performing a repair install *if* necessary, but if this is just a false alarm or something, I would like to know.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

36 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-06-27T18:17:21+00:00

    OK here's the latest. installing the latest update did not solve the issue. ever since windows 10 came out I have made the habit of downloading the .ISO that contains install.wim when ever I upgrade builds. This habit saved me several time in the past on my old system. these version were called techbench ISO's at one point I believe. anyways, I mounted the ISO, and moved the install.wim to c:\temp. then I dropped to the recovery mode command prompt. from here I performed an offline image repair using two different methods. neither method of using dism worked. I tried mounting the install.wim into c:\mount and then opened a second dos prompt and compared the two copies of the files (srmclient.dll & srmscan.dll) there were minor differences, mostly having to do with the dates on the files. mutliple passes of SFC had failed to fix the issue, despite SFC saying it had. and then I got the bright idea of using one of SFC other features, a targeted scan focusing on only one file. basically I used the following command - "sfc /scannow /offbootdir=c:\ /offwindir=c:\windows\ /scanfile=c:\windows\syswow64\srmscan.dll" this gave the same message that I had been seeing all along, but when run a second time, the message saying no resource protection errors found was displayed. I ran the same command on srmclient.dll and here is where things get a bit weird. fixing the other file seems to have fixed both files at the same time. So, I rebooted back into windows, and ran SFC once more. now here is where things get really, really weird. SFC still says those two files have a file hash mismatch. BUT, when running at targeted scan using either /verifyfile or /scanfile, SFC says 'Windows Resource Protection did not find any integrity violations.'

    in a side note, trying to run the copy of SFC that exists in c:\windows\syswow64\fails with a "windows resource protection could not start repair service " error message. I don't know if this is normal, or if this is a symptom of a problem.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-27T13:33:43+00:00

    i will post back with my findings once i get the update installed. i suspect that SFC will indeed stop complaining about file hash mismatches once the update is installed. fingers crossed!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-27T13:04:13+00:00

    Lets hope not!

    If you don't have any more questions, feel free to choose a rating and let us know whether this information was helpful to you!"

    Was this answer helpful?

    0 comments
  4. Neil D 33,005 Reputation points Volunteer Moderator
    2020-06-27T12:54:00+00:00

    For current issues you might want to read through this, and keep checking for the future.

    https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-06-27T12:46:42+00:00

    hmm.... i at least have had no issues about printing.... unless that one of the issues that comes from the latest update..... *shudder*

    Was this answer helpful?

    0 comments