SFC /SCANNOW cannot fix storport.sys

Page 2 of 2 FirstFirst 12

  1. Posts : 120
    Windows 10 64
    Thread Starter
       #11

    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?
      My Computer


  2. Posts : 120
    Windows 10 64
    Thread Starter
       #12

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


  3. Posts : 194
    Windows 10 Pro
       #13

    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
      My Computer


  4. Posts : 120
    Windows 10 64
    Thread Starter
       #14

    jl2509 said:
    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
    Hard not to notice it, it stopped me being able to do the commands! Thank you for the assistance though, a combination of DISM and some luck fixed this. Although I dread SCANNOW now - the horror at seeing errors after waiting 10 minutes each time!

    I am hoping all of this has resolved my lock ups - they do SEEM to be related to SSD but it's hard to pinpoint the culprit. Very hard. Event viewer wasn't overly enlightening, but the fact a storage driver was corrupt and the drive firmware was out of date does point to my theory being correct.

    We'll see.
      My Computer


  5. Posts : 2
    Win 10 x64
       #15

    I am posting here since this is the #1 Google result for this, despite the thread being old.

    (Also...the "help" about this on MS official "answers" forum, AS ALWAYS, makes me cringe beyond belief. Needless to say, there is no answer on MS forum, nor anywhere). Here it is:


    The problem comes when you have installed bad/flakey IRST (Intel Rapid Storage Tech) HDD SATA drivers, which replace the "Standard AHCI SATA controller" of Windows.

    Solution:

    Uninstall the Intel IRST drivers from your system (Programs/Features). Done. SFC comes out clear. Either use the standard AHCI drivers that are included with W10, or download proper IRST drivers from Intel.

    **** Added notes for the "pros" ****

    For some older chipsets, like Z77, there are actually no "proper" Intel AHCI drivers according to some sites. But a guy on win-raid forum made certified and signed modded Intel universal AHCI drivers.

    Forum - Intel RST/RSTe Drivers (latest: v17.7.0.1006 WHQL/v6.2.0.1238 WHQL)

    These are a "bit" involved to install as you need (?) to install the certifcates as well (see link), but they seem to work. SFC comes out clear. So long, no problems. The idea here is that the Intel AHCI drivers are "better" than the Standard W10 AHCI drivers, this is why some people like the Intel drivers over the W10 drivers.
      My Computer


 

  Related Discussions
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 11:00.
Find Us




Windows 10 Forums