Windows 10: SFC /SCANNOW cannot fix storport.sys

Hi there, been a while since I was on here.

Been getting a few intermittent lock ups here and there and I MAY have narrowed it to the SSD, or specifically old firmware and corrupt files.

Firmware was easy enough to resolve, then I used DISM to fix the disk image too - all good.

All that's left is good old SCANNOW - and I cannot for the life of me get it to fix the one file that still seems to be a problem - storport.sys.

Errors are:

So it gives mixed messages about whether it's fixed or not, but when I re-run SCANNOW it's pretty much the same problem. I put on a 'good' copy of storport.sys to replace the 'corrupt' one but I still get the same errors.

I get no errors at all in safe mode, but I do in normal mode.

I'd like to nail this ASAP and if anyone can assist, I'd appreciate it.

Windows 10 64 fully up to date
1080Ti
Z97-A
32GB Corsair XMS @ 1600
OCz 130GB SSD

No overclocking anywhere.

:)

 

Win 10 SFC /Scannow cannot fix provsvc.dll

Hi,

Since you are trying to run the System File Checker tool (SFC.exe) that allows you to scan for corrupted files. It seem to not fix the error. It suggest that the system image of where the
SFC tries to find the error itself is corrupted. What we can do instead is to run the Deployment Image Servicing and Management(DISM.exe) first to check and fix the system image. You can follow the instructions provided on
this
link. Then kindly run an SFC scan and check if the
SFC scan was able to fix the system file corruption.

Let us know how it goes.

 

Win 10 SFC /Scannow cannot fix provsvc.dll

I'm attempting to track down and fix a problem on my laptop that is causing sudden crashes that apparently leave no dmp files. I ran the SFC /Scannow command from an elevated CMD box 4 times, and while it did find and fix a few errors, it cannot seem to
solve this one. I have tried rebooting, and running SFC again with no luck, same error each time. This is a copy directly from the most recent CBS log file:

2016-09-13 03:53:33, Info CSI 000052d3 [SR] Verify complete

2016-09-13 03:53:33, Info CSI 000052d4 [SR] Repairing 1 components

2016-09-13 03:53:33, Info CSI 000052d5 [SR] Beginning Verify and Repair transaction

2016-09-13 03:53:33, Info CSI 000052d6 [SR] Cannot repair member file [l:11]'provsvc.dll' of Microsoft-Windows-HomeGroup-ProvSvc, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing

2016-09-13 03:53:33, Error CSI 000052d7 (F) Failed on regenerating file [l:11]'provsvc.dll'[gle=0x80004005]

2016-09-13 03:53:33, Info CSI 000052d8 [SR] Unable to repair \SystemRoot\WinSxS\amd64_microsoft-windows-homegroup-provsvc_31bf3856ad364e35_10.0.14393.0_none_bf31d8560473824b\\[l:11]'provsvc.dll'

2016-09-13 03:53:33, Info CSI 000052d9 [SR] Repaired file \SystemRoot\WinSxS\amd64_microsoft-windows-homegroup-provsvc_31bf3856ad364e35_10.0.14393.0_none_bf31d8560473824b\\[l:11]'provsvc.dll' by copying from backup

2016-09-13 03:53:33, Info CSI 000052da@2016/9/13:07:53:33.199 Primitive installers committed for repair

2016-09-13 03:53:33, Info CSI 000052db [SR] Cannot repair member file [l:11]'provsvc.dll' of Microsoft-Windows-HomeGroup-ProvSvc, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing

2016-09-13 03:53:33, Info CSI 000052dc [SR] This component was referenced by [l:88]'Microsoft-Windows-Shell-HomeGroup-Package~31bf3856ad364e35~amd64~~10.0.14393.0.HomeGroup'

2016-09-13 03:53:33, Info CSI 000052dd Hashes for file member \??\C:\WINDOWS\System32\provsvc.dll do not match actual file [l:11]'provsvc.dll' :

Found: {l:32 Cx0iftSyiF9D7drxcnLQAXNePRYuI0qYtyvPPtjNdho=} Expected: {l:32 OjsFu04RVBDScGOzDA7z8YKV9UIFDzKfHkZsganiOkY=}

2016-09-13 03:53:33, Info CSI 000052de [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\provsvc.dll; source file in store is also corrupted

2016-09-13 03:53:33, Info CSI 000052df [DIRSD OWNER WARNING] Directory [l:29 ml:30]'\??\C:\WINDOWS\Logs\HomeGroup' is not owned but specifies SDDL in component Microsoft-Windows-HomeGroup-ProvSvc, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2016-09-13 03:53:33, Info CSI 000052e0@2016/9/13:07:53:33.225 Primitive installers committed for repair

2016-09-13 03:53:33, Info CSI 000052e1 [SR] Repair complete

2016-09-13 03:53:33, Info CSI 000052e2 [SR] Committing transaction

2016-09-13 03:53:33, Info CSI 000052e3 Creating NT transaction (seq 1), objectname '(null)'

2016-09-13 03:53:33, Info CSI 000052e4 Created NT transaction (seq 1) result 0x00000000, handle @0x10d0

2016-09-13 03:53:33, Info CSI 000052e5@2016/9/13:07:53:33.257 Beginning NT transaction commit...

2016-09-13 03:53:33, Info CSI 000052e6@2016/9/13:07:53:33.257 CSI perf trace:

CSIPERF:TXCOMMIT;13033

2016-09-13 03:53:33, Info CSI 000052e7 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

At this point, I'm not even sure if this is the reason for my sudden crashes, but it's the only obvious problem I see in front of me. Any suggestions on how to proceed?

 

Hi

Can you try to repair the system image files please

Run...
DISM /Online /Cleanup-Image /RestoreHealth

hope this helps

 

Hi, thanks for the reply. If you notice in my post I pointed out I'd used DISM already - all good. I suppose I can always run it again.

 

I did notice that you had run DISM but you didn't state what options you added !

Normally, when the image cannot extract the files required to repair from scannow, the DISM command line works every time.

 

And I did - still fine. Problem isn't there.

 

Yeah it's (DISM Health thingy) working just fine, but unfortunately SCANNOW still seems to think there's a problem with storport.sys. A tad bemused!

 

could try the following:

Open Admin Command prompt, copy/paste each line and run:

dism /mount-wim /wimFile:%USERPROFILE%\Desktop\install.wim /index:1 /MountDir:%USERPROFILE%\Desktop\mount
Dism /Online /Cleanup-Image /CheckHealthDism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\mount\windows /LimitAccess
Dism /unmount-wim /Mountdir:%USERPROFILE%\Desktop\mount /discard
re-run: sfc /scannow

hope this helps

 

I'll give it a go, thanks. I'll report back how it went.

EDIT; sorry I'm struggling with these commands. I'm getting errors in CMD when I try the first one - I can't quite tell where the first line ends. Is it '/index: 1' or '\mount'.

Mind you either way I'm not getting very far! Could you kindly be a little clearer in the syntax?

 

Maybe I can clear it up. Notice there is a blank before each /. I think the sequence below is what jl2509 intended:

Dism /mount-wim /wimFile:%USERPROFILE%\Desktop\install.wim /index:1 /MountDir:%USERPROFILE%\Desktop\mount

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\mount\windows /LimitAccess

Dism /unmount-wim /Mountdir:%USERPROFILE%\Desktop\mount /discard

re-run: sfc /scannow

 

yeh, sorry my post was a bit shabby.

If you copy to whole command(s) to notepad without word wrap turned on, each command should be on one line.

Thank you

 

Thanks for the clarity.

Doesn't this lot require preparation though; a folder on the desktop and mounted ISO etc? Or should it just work off the bat?

 

Ahhhhhh finally. I just ran the CMD SCANNOW and it now finds no issues. OORAAH! Cheers guys.

 

Well glad you got it fixed.
Yes I made another mistake there, and you noticed it.

You need to:

• Create a folder on desktop: mount
• Copy install.wim to desktop (from Windows ISO)

I missed it when I pasted the solution in


Cheers