This did not work for me. I updated to the latest driver, but Windows 10 update WILL NOT install because it still sees the old driver.
Update to Windows 10 1903 requires updated Intel Rapid Storage Technologies
After receiving the notification, I updated my Dell Inspiron 5000 series with an update from Dell. This update installed successfully as indicated:
However, the file that is blocking the Windows update, iasota.sys, is the old version that was present before I updated RST (note that other iasot*.sys files are newer):
Any idea on what can be done to workaround the problem?
Is the iaStorA.sys file obsolete and no longer needed now that the RST driver has been updated? If yes, should I simply rename the file to iaStorA.old and attempt to update Windows again?
Do newer versions of Intel RST still use the older iaStorA.sys file resulting in the Windows Setup not recognizing that a compatible version of RST has been installed? If yes, then do I have to wait for Microsoft to modify the Setup program so that it assesses RST compatibility by looking at something other than the iaStorA.sys version (e.g., the iaStorAC.sys version, which is the file that serves as the driver for the I/O SATA AHCI Controller?
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.
53 answers
Sort by: Oldest
-
Anonymous
2019-08-01T21:29:03+00:00 -
Anonymous
2019-08-01T23:09:56+00:00 Hi Max,
I also ran into a problem the 1st time I followed this procedure. What I did was restore the computer to a restore point and ask the person who recommended the procedure for some more detail, which he kindly provided. With this additional information, the upgrade went very smoothly. For details about what I did wrong and how to avoid it please see my reply to MarcelCornichon's post on July 27, his reply to me and my subsequent reply to his reply.
Also, I posted a more detailed description of the steps I used to successfully upgrade to 1903 in my reply to AkwasiNimako's post on July 31.
If you can tell me at what point in the procedure your friend's computer got hosed and describe the problem, perhaps I or someone else on this forum can advise you on how to fix the problem.
Best,
Maurice
-
Anonymous
2019-08-01T23:22:46+00:00 Hi Ready_Rover,
You are correct. The problem is that when you update RST, the new version of RST still installs the old iaStorA.sys file while installing some other newer drivers. Unfortunately, the Windows installation program looks at the iaStorA.sys file instead of the newer ones. Please see my reply earlier today to JohnptD's post for more detail.
And, see the correspondence between MarcelCornichon and me on July 27 for additional information about this bug.
Finally, see my reply to AwasakiNikamo's post on July 31 for the detailed steps I used to successfully upgrade to 1903.
Best regards,
Maurice
-
Anonymous
2019-08-01T23:30:14+00:00 Hi Christopher,
You will be able to successfully upgrade to 1903 without waiting for Microsoft to fix the bug and without having to do a clean install.
First, please read the entire exchange between MarcelCornichon and me on July 27 to get a better understanding of what is causing the problem. The discussion also contains one clarification to Marcel's procedure that is critical for avoiding a major problem.
Then, you can follow the detailed steps I used to successfully install the upgrade. These steps are contained in my reply to AwasakiNikamo's post on July 31.
Best regards,
Maurice
-
Anonymous
2019-08-02T01:52:53+00:00 My solution was simply to rename the old iastora.sys file, once I had confirmed that a new driver had been installed and was active (15.9.6.1044). Once the file was renamed, to iastora_old.sys, I relaunched the Windows 10 update and it installed without a hitch. Clearly the update hangup is not fixed by simply updating the driver. The old driver must be removed or renamed, otherwise Windows 10 will not update. (Seems like someone should have tested the recommended "fix'' -- updating drivers, before rolling this out, this former IT support guy thinks.)