[SOLVED] Problems to get Win10 installed onto an Intel 530 SSD

Operating Systems Windows 10/Server 2016-2019
41

No, there are no special drivers for SSDs. They need the same as HDDs.


Which leaves the controller drivers … what’s the difference between iaStorA.sys and iaStorAC.sys then? The driver pack I got has the latter, which is identfied as NOT needed by the install but the former is used by my Vista machine for the SSD. I think my next sojourn will be in investigating the instanciation of an unattended install and see whether it’ll be fast enough to miss the shipped driver intermittancy.

42

No, you are mixing the names of the drivers (= *.sys files) and their related information files (= *.inf files). There is no driver named iaStorAC.sys in your driverpack. Your former OS Vista may have used the Intel AHCI driver named iaStorA.sys, but didn’t need it, because even Vista had an on-board generic AHCI driver, which supports Intel SATA AHCI Controllers as well.

43

@ nepaluz:
I have to stop my support now, because I will go to bed and I doubt, that I will have tomorrow the needed time to help you.
Please read >this< already previously linked guide carefully. Maybe you will find this way the reason for your Win10 installation failure.
If you should succeed one day, please let us know how you managed it.

44

Just to finally update and bring closure to the off-topic query I in-advertently started.

1. Looks like there is a well documented hardware incompatibility issue with the Intel 530 240GB SSD and the Intel(R) 8 Series Chipset Family SATA AHCI Controller. I put the SSD into my Sony laptop with an Intel(R) ICH9M-E/M Sata AHCI Controller, cloned the disk and it worked flawlessly.
2. I decided to get a SanDisk Ultra II 120GB drive to try in the Lenovo laptop and it worked wihout issue installing a downloaded ISO of Win 10.

Just a note on a clean install of Win 10 using the > tech-bench link < provided by Fernando - Make doubly sure that the version of Win 10 that you download is the same as that one that is on your ugraded Win 8/8.1 to Win 10 system that you wish to clean install or else your clean installed version of Win 10 it will not activate. I made the mistake of downloading a single language version Win 10 ISO (in the misguided belief it would be smaller … in hindsight actually turned out to be larger by 600MB!) and it would not activate. Downloading and installing a plain Win 10 ISO, which was on my laptop, solved that issue. If you use the media creator tool on the target system, there is no need to be concerned as the correct ISO will be downloaded.

Finally, my thanks to everyone that tried to help, in hindsight, the initial issue that I tried to raise regarding modded drivers for the controller to be able to recognise (and keep alive) the intel SSD, seems to have actually been the real issue, albeit without a known solution if I am to go by what I’ve found on the net.

45

@ nepaluz:
Thanks for your final report, which verifies, that your problem had nothing to,do with a missing driver. So there was no reason to integrate any driver into the Win10 image.
As already announced I have moved our discussion into the "Special: Windows 8.1/10" section of the Forum and gave the new thread a meaningful title.
Enjoy your freshly installed Win10!

@ Nemo:
Here is the new location of our discussion with nepaluz.
Thanks for your help!

46

@Fernando :
You’re welcome.

@Nepaluz:
That’s why I wanted you

  • to generate a GenuineTicket.xml by GatherOSState.exe to be copied after installation to C:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket*.xml
  • to create a backup of your Win10 license with Advanced Tokens Manager (ATM)

Which install files do you find on your different ISOs: .\sources\install.ESD or .\sources\install.WIM?
ESDs are much smaller as they are compressed with a higher rate than WIMs, but they have to be converted to WIMs before you can manipulate them with DISM.exe in order to integrate patches, drivers, tweaks.

Regards, Nemo

47
  1. I get your nod towards the GenuineTicket stuff, however, that’s a long winded way to achieve what could be achieved "out of the box" using a similar version ISO.
    2. Both ISO’s have WIM files, which as you say dism.exe (and NTLite) do not need to convert, but for some reason the plain (multi language?) ISO download is smaller than the single language one.

    Generally, it was definitely worth it to get the clean install onto SSD … cold boot-up is in a flash (4.3 secs and improving) and I’ve definitely got rid of A LOT of garbage that ships with he Lenovo install. Thus far, I’ve not had any issues with drivers, though I have to mention that after burning the ISO onto USB I copied the the entire FileRepository directory under DriverStore on the shiped Lenovo drive into the USB. I tried integrating the drivers using NTLite but it kept on crashing whenever I applied the changes for no apparent reason so I gave up on that.

    After installing, there were a couple of exclamation marks against some components in device manager and all I did was right click on them, select update driver then choose to browse for the driver then point to the FileRepository folder I’d copied over. Aside from the synaptics stuff, all other drivers installed properly. As for the synaptics, all I had to do was look for a directory under the FileRepository that was named similarly to the name and run the exe’s inside sequentially, checking each time whether the mouse was moving as smoothly and fast as before, and as soon as that happened, I stopped (not very scientific, but it worked!). You could download the driver packages from Lenovo (or whoever makes your system), but that is a fair bit of bandwidth with just the graphics drivers coming to nearly half a GB!
48

@nepaluz :
Thank you very much for your final feedback and congrats for your successful clean Win10 installation.
Since your problem obviously has been solved, I have customized the title of this thread.