Windows 10 update fails with error about iastora.sys after upgrading to recommended Intel Rapid Storage version

Anonymous
2019-07-26T19:17:02+00:00

I'm attempting to update Windows 10 to 1903. The update failed with the error message "The inbox storage driver iastora.sys doesn't work on these systems and causes stability problems on Windows. Check with your software/driver provider for an updated version that runs on this version of Windows." This error led to a support page at https://support.microsoft.com/en-us/help/4514156/updating-to-windows-10-version-1903-on-devices-with-certain-versions-o recommending that the driver be upgraded to version 15.9.6.1044.

I have upgraded the driver accordingly (see attached screenshot), and rebooted the machine afterwards, but still receive the same error. I have also tried uninstalling and reinstalling the driver, and attempting the upgrade with the driver uninstalled, but receive the same error message no matter what version of this driver is installed, or indeed if it is installed at all.

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 No comments
Answer accepted by question author
Anonymous
2019-07-26T19:22:48+00:00

Hi Todd. I'm Greg, an installation specialist and 10 year Windows MVP here to help you.

That's the buggy Windows Upgrade Advisor which is often wrong and wastes a lot of time. For this reason it's much more stable to Upgrade using the media itself and not buggy Windows Updates or Upgrade Advisor.

Install the Media Creation Tool from this link http://windows.microsoft.com/en-us/windows-10/m..., choosing Download Tool Now, install the tool, open it and choose Upgrade this PC Now. . This will save your files and apps while bringing you up to the latest version by the most stable method. It will also bring all of your Updates current and solve most problems since it reinstalls Windows.

If any problems report back the verbatim error and number, then continue with these steps for overcoming Version Upgrade problems: http://answers.microsoft.com/en-us/windows/wiki...

I hope this helps. Feel free to ask back any questions and keep me posted. I will keep working with you until it's resolved.

________________________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

74 additional answers

Sort by: Oldest
  1. Anonymous
    2019-08-30T08:25:06+00:00

    like i stated before...go to microsoft web site and register for a free account, let it scan device, you'll have to accept TOS and allow the download to be installed. if you are running a legit licensed version of windows 10 then follow the steps to resolve issue. if it cant resolve your issue answer no to the question did this resolve your issue. i did that twice and it asked if i wanted a microsoft tech to call on a time best for me. now if you are not running a licensed version for whatever the reason might be, you may not want to use this method. because it may result in you not being able to get anything but a blue screen, and maybe a warning that an illegal version of windows has been detected.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-08-31T00:38:13+00:00

    I didn't apply any of the fixes suggested during the life of this thread except that I did apply the latest Intel update (which of course did not fix the Windows 1903 update problem).  When the Windows 10 August update came out, I found that I could apply it OK.  Then I was offered the 1903 version and it installed OK.  It appears that (for me anyway) Microsoft has eventually fixed the issue.

    Was this answer helpful?

    0 comments No comments