Why is the volume licensing install of win 10 pro not making 4 partitions? Why isn't this otherwise fine win 10 pro install bootable automatically?
I've installed a load of win 10 machines using usb thumb drives that have win 10 on them. Probably made the usb disks from a page like this:
https://www.microsoft.com/en-us/software-download/windows10
setup will start, I'll say I want a new install, it'll show me the hard drive, I'll delete any partitions that are on it, point to the one unallocated space entry, hit continue and it will make 4 partitions, 1 that's bootable and things are fine.
I did that on this win 10 home laptop and it worked fine. The church this is for needs win 10 pro, they bought home by mistake. through tech soup, they bought 'get genuine' win 10 full install licenses. The MS rep said you have to install win 10 pro only from the VL ISO on the VL license page with the keys.
I download the ISO, make a bootable thumb drive using win 7 creator tool.
Put the usb in, press f12 at startup (for bootable devices list - it's a dell), choose the USB and the install starts up, I do the delete partitions / point to the unallocated space..
install goes fine till it reboots. at reboot it goes right into diagnostics (not the hard drive). If I restart and press f12, and choose hard drive it boots into win 10 pro fine.
Some things l noticed:
In system management / device management, I see there's only 2 partitions on the drive, not 4 - some small one and then the C drive.
Doing some googling, I see to look at hard drive properties in device manager. Under partitions, it's blank!? I choose reload and nothing happens.
In bios it's set to UEFI. but no boot sequence listed
If I click add boot option it says no file system found.
I guess I could install win 10 home with the standard win 10 installer, then rather than wipe all 4 partitions, just install win 10 pro with the volume license disk.
But is there something else you'd suggest?
Right? Win 10 clean install should be 4 partitions?
I relly don't think the install ISO is bad - it does make a win 10 machine.. just the drive has 2 partitions and Ican't get it to boot into win 10 on its own...
https://www.microsoft.com/en-us/software-download/windows10
setup will start, I'll say I want a new install, it'll show me the hard drive, I'll delete any partitions that are on it, point to the one unallocated space entry, hit continue and it will make 4 partitions, 1 that's bootable and things are fine.
I did that on this win 10 home laptop and it worked fine. The church this is for needs win 10 pro, they bought home by mistake. through tech soup, they bought 'get genuine' win 10 full install licenses. The MS rep said you have to install win 10 pro only from the VL ISO on the VL license page with the keys.
I download the ISO, make a bootable thumb drive using win 7 creator tool.
Put the usb in, press f12 at startup (for bootable devices list - it's a dell), choose the USB and the install starts up, I do the delete partitions / point to the unallocated space..
install goes fine till it reboots. at reboot it goes right into diagnostics (not the hard drive). If I restart and press f12, and choose hard drive it boots into win 10 pro fine.
Some things l noticed:
In system management / device management, I see there's only 2 partitions on the drive, not 4 - some small one and then the C drive.
Doing some googling, I see to look at hard drive properties in device manager. Under partitions, it's blank!? I choose reload and nothing happens.
In bios it's set to UEFI. but no boot sequence listed
If I click add boot option it says no file system found.
I guess I could install win 10 home with the standard win 10 installer, then rather than wipe all 4 partitions, just install win 10 pro with the volume license disk.
But is there something else you'd suggest?
Right? Win 10 clean install should be 4 partitions?
I relly don't think the install ISO is bad - it does make a win 10 machine.. just the drive has 2 partitions and Ican't get it to boot into win 10 on its own...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
nobus
its win10...
Yes, so sorry to bother you guys with this. After posting here I googled and came up with all the points you talk about - UEFi vs BIOS, MBR vs. GPT.
You'd think in 2018, someone that's supposedly tech savvy would know about those... but I kinda avoided them. I used Rufus to make a UEFI GPT of the thumb drive, filddled with the Bios / UEFI settings, installed, the VL license and it rebooted fine.
some thoughts / questions though:
I guess I want to choose the option in Rufus that mentiojns BOTH uefi and BIOS? so the thumb drive is bootable in either? Just have to turn off secure boot if it's on to be able to boot from that USB? I think in the past I'd switch to bios / legacy and leave it there after installing windinws.
When fiddling with the settings, when I choose UEFI, there's a boot sequence area and add . delete boot buttons. I have to learn what those are / how they get populated. A little knowledge is good.
MASQ - interesting what you say - 2 partitions is VL, 4 partitions is OEM? I thought 4 partitions what win 10 and previous versions, I'd only see 2 partitions. I got this win 10 pro VL install done and going... and I am 99% sure it has 4 partitions.
And interesting (to someone ignorant like me...) that the way that the bootable USB can be made can effect if the installed win 10 is bootable or not? Again, the win 10 installed fine but was only bootable manually. I'd have thought things in the background would adjust the boot capabiluty to the system it's going on... but that incorrectly made USB drive can break things?!
but
a) that's what you get when you are ignorant
b) it's windows 10 (nothing from microsoft is simple?)
You'd think in 2018, someone that's supposedly tech savvy would know about those... but I kinda avoided them. I used Rufus to make a UEFI GPT of the thumb drive, filddled with the Bios / UEFI settings, installed, the VL license and it rebooted fine.
some thoughts / questions though:
I guess I want to choose the option in Rufus that mentiojns BOTH uefi and BIOS? so the thumb drive is bootable in either? Just have to turn off secure boot if it's on to be able to boot from that USB? I think in the past I'd switch to bios / legacy and leave it there after installing windinws.
When fiddling with the settings, when I choose UEFI, there's a boot sequence area and add . delete boot buttons. I have to learn what those are / how they get populated. A little knowledge is good.
MASQ - interesting what you say - 2 partitions is VL, 4 partitions is OEM? I thought 4 partitions what win 10 and previous versions, I'd only see 2 partitions. I got this win 10 pro VL install done and going... and I am 99% sure it has 4 partitions.
And interesting (to someone ignorant like me...) that the way that the bootable USB can be made can effect if the installed win 10 is bootable or not? Again, the win 10 installed fine but was only bootable manually. I'd have thought things in the background would adjust the boot capabiluty to the system it's going on... but that incorrectly made USB drive can break things?!
but
a) that's what you get when you are ignorant
b) it's windows 10 (nothing from microsoft is simple?)
"MASQ - interesting what you say - 2 partitions is VL, 4 partitions is OEM? "
More 4 partitons are found in OEM, see David's comment about multiple partitons in UEFI installations.
More 4 partitons are found in OEM, see David's comment about multiple partitons in UEFI installations.