Windows 10: Not able to install new ISO on SSD
Not able to install new ISO on SSD
Basically, I got fed up with the daily problems from doing an "upgrade" from Win8.1 to Win10TP 32-bit and decided to install afresh from the latest ISO. Since I have a 64-bit processor and 8GB of memory (now) I thought I'd try the 64-bit version.
Booted from the USB stick, chose Install, clicked next, saw the drive with the formatted NTFS primary partition (empty) for Win10 and select that ...
And got the dreaded "we couldn't create a new partition or locate an existing one. See the setup log files".
So, I removed the partition, leaving an unallocated drive, and using the "New" icon, created a new one. That appeared to go OK. Selected it -- and got the same error message again!
Went through the same stuff with the 32-bit version -- same sequence, same error messages.
So, I have two questions:
1) When you're in the installer, how do you look at the setup log files to see the detail messages?
2) What is the "secret" to installing Win10 on an SSD? (Note, I had Win8 install just fine to this same SSD (Crucial 120GB) and move Win8.1 to a larger SSD when I bought a new one. So, I know this SSD works OK.
I ran into this same bunch of problems with the original Win10TP install -- which is why I ended up cloning Win8.1 to this SSD and then doing an "upgrade". But this time, I want to do a clean install.
Can anyone help?
Delete all partitions, DO NOT create a new one, let the installer create what it needs.
See if that works.
Does not work -- already tried that.
What DOES work is the following:
- Boot using install media, select Repair, not Install
- Select Troubleshooting --> Advanced options --> Command prompt
- Enter: diskpart
- Enter: list disk
- Enter: select disk <x> where x=disk# (0 - n) of the target disk in the list
- Enter: clean
- Enter: create partition primary
- Enter: active
- Enter: format fs=ntfs quick
- Enter: assign
- Enter: exit
- Enter: exit
- Shut down and reboot
Then, when the partition selection screen comes up, the installation will proceed.
Can also be if your disk if MBR or GPT and the installer is expecting the other. You may need to add convert gpt or convert mbr into your diskpart steps.
Mark Phelps said:
Finnish but not finished
I've had this issue in quite a many vm installations. There's an easy workaround, works at least on virtual machine installations.
When in partitioning dialog to select which partition to use, delete all partitions on disk 0 (if other disks present you don't have to delete partitions on them), then click the Close button:Accept with Yes:
Again, click Close:
PC will reboot now, let it boot from the install media, when selecting the install location select the disk 0 which is now completely unallocated and click Next:
Should start installing now. If you do not want to use whole disk for system you can later shrink it in Disk Management.
(Screenshots from Hyper-V vm installation.)
Last edited by Kari; 16 Dec 2014 at 18:52.
Neat trick Kari. You are always ahead of the curve.
I think the boot partition needs to be ACTIVE for it to boot if you are creating partitions manually. Switch off PROTECTED BOOT if you have a machine that's using it. You CAN leave UEFI on if you want to. So when using DISKPART add the command ACTIVE after you've created your primary partition. Windows install when then jig around all the other stuff.
Mark Phelps said:
I strangely got this dreaded error too while installing Windows 10 Pro (32bit and 64bit) final edition.
Turns out it was because of my USB Flash drive ! ! !
What i found was Win 10 Preview edition installed ok.
But Win 10 final edition just refused to install on any laptop/desktop, even after trying everything from pre-OS AHCI drivers and changing BIOS settings.
I then eventually realised that the only difference was the USB flash drives i used !
If I used my Kingston DataTravelerG4 USB 3.0 drive, i would always get that dreaded error when it tried to create the partitions.
But if i used my cheapo Sandisk Cruzer Facet USB 2.0 drive, Win 10 would install perfectly without issues !
Finnish but not finished
Judging by the highlighted part in below quote you let the Media Creation Tool create a USB install media containing both bit versions, 32 bit and 64 bit:
If this is a case and if installing Windows 10 on a PC with 32 bit architecture, there might be a natural and logical reason why Windows installation fails. Here's a screenshot of the boot screen when the install media contains both bit versions:Notice that the 64 bit version is default, on top and selected. Also notice that without user interaction, the default (64 bit) installer will be automatically started in 30 seconds (in the screenshot 12 seconds already gone, 18 left). Simply, if the user has 32 bit hardware and do not manually select 32 bit installer on this screen allowing the 64 bit installer start automatically after 30 seconds, or if the user presses Enter here without selecting the 32 bit installer first, the 64 bit installer will be run. Of course it will fail on 32 bit machines, a 64 bit Windows cannot be installed on 32 bit hardware.
Yes Kari, you definitely can Not install 64bit Windows on 32bit architecture.
If you were wondering if that was my mistake, then No, all the machines Ive tested on were x64 (eg Core 2 Duo ... AtomN450.... Core i5).
If the 64bit installer was to be run on a legacy 32bit machine, the installer would Not even get as far as starting the GUI.
Anyway, Ive tried the 32bit installer as well, and it too fails with that dreaded error message at the partitioning stage.
Using only the Microsoft utilities, how do I convert the install.wim to install.esd file?
On install on an HP envy laptop I got the "Just a Moment" Logo at the final stage just going on forever. After about 15 mins I thought well I'll try again. I couldn't even POWER OFF the laptop. I had to open it up and remove the battery...
Solved problem, ignore.
I'm using Windows 10 Build 10041. First of all, Windows wouldn't update to the newest build. This never got fixed so I tried installing the newest Windows 10 ISO, using Rufus to make it bootable. So I went into Settings...
I have W10 Eng 32 bit and latest VMPlayer. I tried installling as W8. It works but vmware tools are messed up. I have other vms with tools already installed. It seems to detect them after I get W10 desktop. Also it never asks me for the product...