Since I really doubt, that this is true for a clean install onto any SSD (a cloning of the OS installation from a HDD to an SSD may be something else), I would like to get the source of this statement.
Strange as it may sound, it actually is true and I am not making anything up as I go along here! But yes, I 've previously tried cloning the HDD to SSD and as you allude the results were not positive. Look at this > link < . I at times get the last image in that article (having tweaked the BIOS settings and I suppose the SSD is not recognised). However, other times the SSD is recognised, even the partitions on it are recognised but when I try to install on the primary partition I get the error Windows Setup is unable to locate a valid hard drive to store temporary installation files. I can not even delete or create new partitions as it seems as soon as I try to setup magically looses the drive (and that is why I thought it is driver related).
In any case, if it is simply inf files, would I be able to get the inf file for the driver in the working installation and point it to setup at that stage? (there’s an option on the setup screen to load drivers)
I will attach the related INF file for your Intel 8-Series Haswell CPU system, but integrating or loading this file is wasted time, because 1. this file will not change anything regarding the detection of the SSD and 2. the Win10 image contains already all required informations to detect your Intel chipset.
Question: Why dont you just try to do what I have proposed previously (don’t forget to unplug the HDD before you start wih the Win10 installation)? I am pretty sure, that you will succeed this way, and in the worst case (your SSD will not be detected) no data will be written onto your SSD.
@Fernando - thanks again for all the help. I have actually done exactly as you suggested, I’ll repeat the steps I’ve taken briefly below. 1. Downloaded the Win10 ISO image from TechBench (I actually found this very useful as I was downloading using a public PC where I could not run the media creaion tool!) 2. Burnt the image using Rufus (as you suggested) onto an 8GB SanDisk USB 3. Opened up my laptop, removed the HDD and replaced with the SSD - initially, the SSD did not have any partitions, but after consulting here and the install failing, I added one partition of 150GB. At first, I had not set that partition as active, and setup did not recognise the drive, I then went into the command prompt and made the partition active … it was recognised and the process went further only to fail with the temporary files error I mentioned above.
I do NOT want to waste your or my time, but since you took the effort to post the inf file, I will try it as I have nothing to lose really. Just a note: I have presently placed the SSD in the caddy I mentioned with the HDD replaced and booted up the laptop but the SSD is NOT recognised! When I attach it using a USB adapter, it is recognised, though as a removable drive (just thought I’d mention that).
You should connect the SSD with the "normal" SATA port, not with the caddy one. There should be no disk drive connected with your laptop except the SSD and the USB Flash drive containing the bootable Win10 image. Furthermore should delete all partitions after Win10 Setup has detected your SSD and before you create any new partition.
I’ve re-run the setup just to be able to get some screenshots. This is the error I get when I try to delete the aprtition I previously created on the drive. The error is: [Error:0x80070002]
EDIT: Also see > this post < for a very similar scenario. If you want me to take any other screenshots, I’ll oblige, just let me know (now I have the SSD in place)
You can find >here< the possible reasons and how to solve it. If this shouldn’t help, I recommend to delete the existing partitions via Diskpart commands. By the way: Your screenshot indicates, that there is currently no boot sector on your SSD.
You can find >here< the possible reasons and how to solve it. If this shouldn’t help, I recommend to delete the existing partitions via Diskpart commands. By the way: Your screenshot indicates, that there is currently no boot sector on your SSD.
The possible solutions in the link do not apply as I am doing a clean install. I only have the SSD and the USB drive (I’ve even removed the DVD / CDROM drive!). As per the edit on my last post, the link in that referenced post mentions that deleting partitions results in the drive not being recognised at all (which was my experience as noted previously), but for the sake of completeness, I’ll try and delete the partitions. Also, i am not sure why the significance of the lack of a boot sector has, but if you can point me to how I can put one ther, I’ll, again, be glad to try that too.
I removed the partitons, rebooted the USB and just as mentioned, the install failed to recognise the drive.
2. So I booted up the HDD, converted the drive to GPT via diskpart and added one 141GB partition which I did not format. When I replaced the HDD with the SSD in the laptop and booted up the USB, install seemed to go further that it has before, even creating an MSR partition! However, it will not install on the 141GB partition, neither is it able to create a new partition from the un-allocated 81GB. I am stumped!
I am now going to try converting the SSD back to NTFS and create a single partiton (seeing the disk is not recognised without an partition on it)
@ nepaluz: All your problems seem to be caused by either having chosen a wrong "Partition Scheme" while creating the bootable USB Flash drive by using the tool Rufus or by chosing the wrong (non-UEFI) device while selecting the bootable USB Flash Drive. Questions: 1. Which "Partition Scheme" did you choose, when you ran Rufus? 2. Does your laptop support to boot in UEFI mode? 3. Are you able to run a "Boot Menu" by hitting an F key (F8, F11 etc) resp. can you select a specific boot device from within the BIOS?
1. I was following your instructions but Rufus did not have the exact option you mentioned that included GPT. 2. Yes, the laptop supports UEFI mode (also see below) 3. Yes I am able to to run a boot menu and abke to select a specific boot device from within BIOS (in fact, it detects the USB and lists it as a USB device with the option to enable USB device booting also offered)
From 2 (and 1 above) above, you may have a point as the laptop initially failed to boot from USB device until I changed boot options to allow Legacy support. So would you say rather than changing the partitions on the drive I should get the GPT / UEFI option while burning the USB? PS. I’ll boot the laptop up with the HDD in a moment and update you on the options Rufus offers before I go ahead with anything else.
Right, the options in Rufus are: 1. Partition Scheme - MBR Partition scheme for BIOS or UEFI - MBR Partition scheme for UEFI - GPT partition scheme for UEFI
I am going to hold off deleting the SDD partitions and re-run Rufus with the following settings: Prtition scheme: GPT partition scheme for UEFI File System: NTFS Cluster size: 4096 bytes (Default)
Are those correct?
EDIT: I just noticed that when I select NTFS the partition scheme changes to MBR Partition scheme for BIOS or UEFI as soon as I start the process, so I cancelled and left the default selection of FAT32.
If you want to get Win10 installed in UEFI mode, you have to choose the Rufus option "GPT partition scheme for UEFI". Since the UEFI mode is not supported by using the NTFS File System, you have to choose the option "Large FAT32 (Default)".
If you have created a bootable USB Flash drive by using Rufus and chosen the "GPT partition scheme" as Partition scheme and "Large FAT32 (Default)" as File System, you should get a bootable device listed named (UEFI) <NAME OF THE USB>". You have to choose this option and not the other one without the "(UEFI)" prefix, if you want to get the OS installed in UEFI mode (using the GUIMODE Partition Table).
@Fernando - thanks a lot for the input and apologies for going so off topic. I did as advised and the install process does not get too far off where it previously reached however, I now have a different error, ie: We couldn’t install Widows in the location you chose. Please check your media drive. Here’s more info about what happened: 0x80300002
I’ve googled for that error and it seems to be related to installation media, but I am using a USB (from an ISO), so I am at a loss as to the remedy. However, when I click on refresh in he screen to choose a partition, all the partitions disappear. I tried loading the driver you attached and they are all incompatible, I wonder whether I need to give you more details on my system … well it is a lenovo flex 2-15.
I have to say you were spot on with regard to the boot disk settings in Rufus … GPT UEFI et al … as the install boot up is much faster and the display sharper (denoting loading proper drivers?).
Did you check the used USB Flash drive? Maybe it will help, when you take another (better) USB Flash drive.
It is not an issue with the USB flash drive as I also have another new 16GB Sandisk drive that I’ve flashed but still get the same result. If, however, by better you mean a different model, then I have yet to try that (and won’t be able to till tomorrow!).
Saying that, I’ve been fiddling a bit with the BIOS, and had the SATA controller mode set to Compatible and getting the errors I’ve documented. After the last install fail, I changed the mode back to the factory default AHCI and the drive partitions were NOT detected from the onset. So there, the error has to do with the SATA controller!
In the meantime, I also dug up > this link < on how to get Intel RST drivers. I managed to load the inf drivers and the install process does recognise the driver for my chipset, i.e Intel(R) 8 Series Chipset Family SATA AHCI Controller, but still can not get past THAT screen in the install process, aka the drive is lost after being detected.
I’ll make this my last progress post here as I am totally off-topic until (and when) I manage to have better progress. Thanks again for all the input.
This may have been a mistake. After having created a new partition for the OS, the OS automaticly will add some additional ones and sets them in front of the partition you had created. You cannot install the OS onto any of these additionally created and very small sized partitions! Look at the sizes of the partitions, before you decide where to install the OS.
This may have been a mistake. After having created a new partition for the OS, the OS automaticly will add some additional ones and sets them in front of the partition you had created. You cannot install the OS onto any of these additionally created and very small sized partitions! Look at the sizes of the partitions, before you decide where to install the OS.
You are right about the OS creating smaller partitions, well, in my case it created one extra partition of 128MB, which it placed in front of the 151GB partition that I created. It is this 151GB partition that I chose and the install process fails to install on (as mentioned possibly due to the SATA controller driver). If I choose the smaller partition created by the install process, I get short shrift from the install process immediately.
AFAIK the Win10 Setup running in UEFI mode creates 3 extra partitions in front of the desired OS partition: 1. the Recovery Partition, 2. the EFI System Partition (with the boot sector) and 3. the Microsoft Reserved Partition (MSR). For details of the Win10 installation please look into >this< detailed guide.
I told you already, that the Win10 Setup doesn’t need any SATA Controller driver to detect your on-board Intel 8-Series SATA AHCI Controller and your screenshots verify, that I was right.
AFAIK the Win10 Setup running in UEFI mode creates 3 extra partitions in front of the desired OS partition: 1. the Recovery Partition, 2. the EFI System Partition (with the boot sector) and 3. the Microsoft Reserved Partition (MSR). For details of the Win10 installation please look into >this< detailed guide.
I do not dispute that, but possibly the other partitions are created later on in the install process, but again as per my screen-grabs, the other partition I was refering to as having been created is the MSR partition.
I told you already, that the Win10 Setup doesn’t need any SATA Controller driver to detect your on-board Intel 8-Series SATA AHCI Controller and your screenshots verify, that I was right.
It certaily does not need to detect the driver to detect the controller, but it is very possible it needs a driver to detect (and retain) the discovered SDD. It seems to detect it OK (from BIOS?) then unexplainably can notsee it anymore. On that, I have no doubt, but maybe I am looking at the wrong driver and I need the SSD one (are there any?).
