Windows 10: Will Media Creation Tool Create A USB Installer With Version 1511?

Hello All,

I am running Windows 10 Pro x64 that I installed as a full version (not from the free update, I purchased the full edition from Microsoft).

Whenever I get a new OS I like to do a clean install so I used the Microsoft Media Creation Tool which I downloaded from this page. I used the Media Creation Tool to install the OS (wiped and created new partitions, installed the OS, etc.).

Now with this nightmare update they just released (Version 1511) I am having SO many issues. I would like to do another fresh install of this new version.

If I use the Media Creation Tool again to create an USB installer will it contain this latest version (i.e. I won't have to go through the whole update process again)? Or does the Media Creation Tool only create a USB installer that contains the "base" operating system which will required updates all over again?

If not, how can i create an installer for Version 1511 so that I can avoid the pain of updating?

Thank you,

Jan

:)

 

Why aren't the system files included in the Recovery drive?

Hi,

A Recovery Drive is only designed to troubleshoot a Windows 10 install - it is

the USB version of a Repair Disc.

If you want a full version of the Windows Installation Media (which can also

be used for Repair) :

Use the Media Creation Tool to download the ISO then make a bootable

USB or DVD. Download as if for another computer.

Installing Windows 10 using the media creation tool - create media then

boot with it.

Windows 10 herunterladen

How to Create a Bootable USB Flash Drive to Install Windows 10

Create Bootable USB Flash Drive to Install Windows 10

Hope this helps.

--------------------------------------------------------------------------------------------

Rob Brown -
Microsoft MVP <- profile - Windows Experience : Bicycle - Mark Twain said it right.

 

Windows 10 wont boot from SSD after clean install

Ok, I've got it working now. The fault seems to have been with Microsofts Media Creation Tool or the version of the installer i used. Created a new USB-installer by downloading the newest version as ISO, and extracting the files manually, instead of letting
the creation tool create the installer for me. The install process then worked perfectly.

 

Yes, from which you can use USB media to clean install or upgrade

 

Thank you. I am curious, is there a way I can look at a file (or files) on the USB drive to see the specific version of Windows it contains (and therefore will install)?

Thanks!

 

Yes, once you have your USB ready, you can execute a command in an elevated Command Prompt which will give you details about the specific version. See details in this tutorial.

 

Excellent! I didn't know you could do that. Very useful. Thanks for the tip.

 

Thank you for the link explaining how to do it. The results are a bit cryptic and don't look at all the same as if I had run the systeminfo command. Let me give some background info and show you the outputs of both.

When Windows 10 first came out I purchased the full version and installed it fresh on my machine (rather than upgrading which I hate to do). The other day, after I got the "November" Windows 10 update my machine was quite buggy so I decided to make a bootable USB drive (after getting the update) and do a fresh install.

After I saw your post I immediately ran the following command:

Code: DISM /Get-WimInfo /WimFile:E:\sources\boot.wim /Index:1[/quote] and here is the output:

Code: Index : 1 Name : Microsoft Windows PE (x64) Description : Microsoft Windows PE (x64) Size : 1,435,293,590 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : 10.0.10586 ServicePack Build : 0 ServicePack Level : 0 Edition : WindowsPE Installation : WindowsPE ProductType : WinNT ProductSuite : System Root : WINDOWS Directories : 3250 Files : 14085 Created : 10/29/2015 - 11:23:48 PM Modified : 11/16/2015 - 4:10:49 AM Languages : en-US (Default)[/quote] It looks pretty cryptic to me and nowhere did I see anything resembling the patch/OS version of what Microsoft just released (10.0.10586 N/A Build 10586).

So I assume that you either have to know how to read it to know the Windows version and patch(es) or there is some kind of program/website that will do it for you.

Compare and contrast this to the output of the systeminfo command (pasted at the bottom of this message as it is very long), Notice how much more readable the output from systeminfo is compared to DISM /Get-WimInfo. It shows the name, version, etc.

Is there another command I can run on the USB drive that's more user friendly than DISM? Because frankly if DISM is all I have I don't know if it will do me much good.

Thank you,

Jan

Code: Host Name: MY-PC OS Name: Microsoft Windows 10 Pro OS Version: 10.0.10586 N/A Build 10586 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free Registered Owner: Me Registered Organization: Product ID: 00330-80818-96125-AA346 Original Install Date: 11/16/2015, 12:41:58 AM System Boot Time: 11/17/2015, 10:55:07 AM System Manufacturer: ASUS System Model: All Series System Type: x64-based PC Processor(s): 1 Processor(s) Installed. [01]: Intel64 Family 6 Model 60 Stepping 3 GenuineIntel ~3501 Mhz BIOS Version: American Megatrends Inc. 2801, 6/25/2015 Windows Directory: C:\Windows System Directory: C:\Windows\system32 Boot Device: \Device\HarddiskVolume2 System Locale: en-us;English (United States) Input Locale: en-us;English (United States) Time Zone: (UTC-08:00) Pacific Time (US & Canada) Total Physical Memory: 32,708 MB Available Physical Memory: 28,445 MB Virtual Memory: Max Size: 37,828 MB Virtual Memory: Available: 32,844 MB Virtual Memory: In Use: 4,984 MB Page File Location(s): C:\pagefile.sys Domain: WORKGROUP Logon Server: \\MY-PC Hotfix(s): 2 Hotfix(s) Installed. [01]: KB3103688 [02]: KB3105211 Network Card(s): 1 NIC(s) Installed. [01]: Intel(R) Ethernet Connection (2) I218-V Connection Name: Ethernet DHCP Enabled: Yes DHCP Server: 192.168.1.1 IP address(es) [01]: 192.168.1.134 [02]: fe80::7d06:96de:ee96:3031 [03]: 2600:8801:c000:41:a03f:834d:bbe5:66fb [04]: 2600:8801:c000:41:7d06:96de:ee96:3031 Hyper-V Requirements: VM Monitor Mode Extensions: Yes Virtualization Enabled In Firmware: No Second Level Address Translation: Yes Data Execution Prevention Available: Yes[/quote]

 

look at the VERSION...

10.0.10586

10586 is the New OS Build

10.0.10240 was the old build