Windows 10: media creation tool

why doesn't media creation tool have windows 10 pro?

i downloaded the media creation tool from first link on google Windows 10

and started it clicked next, til i got to where i can choose from what version and there weren't windows 10 pro..

:)

 

Media Creation Tool

Microsoft determined my Toshiba machine could be successfully upgraded from Win7 to Win10.

I was going to use the Media Creation Tool to either do an automatic repair or failing that perform a restore. Not a clean install.

 

Media Creation Tool

So, you cannot make the media tool from your Vista machine. Vista is an older os and is not supported anymore by Microsoft. What you should do is have your friend help you create the media tool. After that, run it in your Toshiba machine. You will have to
go to the bios of the machine to do a clean installation of Windows 10 (boot your machine from the usb). The thing is not about accepting Microsoft's offer to install Win. 10 on the Toshiba machine. As I mentioned, it is weather the machine specific meets
the requirements of Windows 10. If it doesn't and you are able to install Windows 10 successfully, the machine could have issues when running it. Plus, you might need a license for Windows 10.

So, you were able to install Windows 10 based on your last points? There are issues because your device is not compatible with Win. 10.

 

The system that you want to upgrade, does it have Home or Pro?

 

Pro. i was thinking clean install with format and clean disk before i install again kinda because this thread i made and i was kinda insecure about what i can do.

thread here: Solved fat32 efi partition on OS disk and bootloader showing in bios - Windows 10 Forums

 

The current ISO file for Windows contains both Home and Pro versions. That's why there is no selection to download either Home or Pro - when you select Windows 10 you get both.

Code: E:\x64\sources>dism /get-wiminfo /wimfile:install.wim Deployment Image Servicing and Management tool Version: 10.0.10586.0 Details for image : install.wim Index : 1 Name : Windows 10 Pro Technical Preview Description : Windows 10 Pro Technical Preview Size : 13,905,900,578 bytes Index : 2 Name : Windows 10 Technical Preview Description : Windows 10 Technical Preview Size : 13,864,879,010 bytes The operation completed successfully. E:\x64\sources>[/quote]

 

When I use Media Creation Tool, I always have access to Windows 10 Pro.

 

i was a bit dodgy to that 99mb partition. so i formated and clean in diskpart and installed windows 10 pro again.

it's correct that when you search for media creation tool on google or whatever. you download it from a microsoft site it's always updated.

so i found out that i opened the media creation tool and pressed next and went with what said windows 10, selected my usb and rebooted and checked just to be sure that when i got to the choice from either windows 10 home or windows 10 pro i could choose one of them, even though it doesn't say pro or home in media creation tool. it gives you the choice later in the install section.

and after i installed windows 10 pro again, i checked the disk management window and the partition was actually 100mb now.

 

Was your concern that the original partition was 99mb in size instead of 100mb?

 

no that was something i noticed in detail.

the main concern was when i fixed my friends laptop. he had a broken monitor on his laptop so i had to take out the hdd and put it in my pc and fix it from there. but while doing this 2 boot manager entries appeared in bios which wasnt there from before. and i have never noticed the recovery partition before. and i didnt know that windows 10 used efi partition fat32 for the whole thing so i thought maybe it was something from his laptop hdd.

 

The second boot manager entry in your UEFI was from his laptop hard drive. UEFI firmware scans all storage devices for the EFI partitions and boot entries and when it finds one, it adds it to it's options for booting. If you have legacy booting enabled in the UEFI firmware it will also add any partitions on MBR partitioned devices that are marked as active.

 

sorry, that's what i was trying to tell you *Smile i didnt want that cause i thought it interfered with the whole booting thing.

is legacy booting under when fast boot is active in bios? if so. i have ssd and read alot about turning that off since it's already fast enough boot with samsung mechanics like rapid mode and over provisioning.

 

Fast booting in bios and fast startup in Windows 10 are two different things.

Fast booting in bios reduces the number of things the bios checks for when booting - it basically reduces your chances of being able to hit the key to enter bios setup and/or the custom boot menu. Fast booting in bios gets to loading the boot files from the HDD/SSD faster. Having an SSD vs a HDD doesn't really affect that too much.

Fast startup set in the Windows 10 power menu does a couple of things. When it is enabled and the computer is shut down, a lot of system information is stored in a hibernation file on the HDD/SSD . Then Windows 10 sends a signal to the bios that says shut down the computer - but don't reset it to a state where it boots up from scratch. Instead go into a state that reads the system information stored in the hibernation file on the HDD/SSD. This also prevents you, usually, from having the option to press the key to go into bios setup or the custom boot menu when the computer restarts from this state. With a slow HDD, it's usually faster for this information to be read from the hibernation file than it is to recreate it upon startup. With a fast SSD, the difference between reading it from the hibernation file and recreating it from scratch is minimal. I don't like having some of the options taken away when Windows 10 fast startup is enabled, so I have it turned off on my computers which have SSDs.

 

i didnt know windows had a fast startup also. never looked so hard.. anyway. i'll look more into it when i get back. have to use the idiotmobile *Biggrin

 

just read some of the fast startup in windows. turned it off and set the hibernation file to reduced. since i just want it to normal standby \ sleep mode.

thanks for that *Smile