Windows 10 (OEM and Retail)

This guide contains instructions for Downloading Windows 10 (OEM and Retail) Installation Media, Creating a Bootable USB, using the Dell Data Wipe, Clean Installing Windows 10 (with and without a Microsoft Account) on Dell Hardware with a UEFI BIOS and Secure Boot and using Dell Command Update to get Dell System Drivers. It also instructions on installing the new Chromium Edge Browser and Microsoft Office 365.

Downloading Installation Media

Windows 10 is available to download through the Windows 10 Download Page and the Windows Insider Preview Pages. The Windows 10 Download Page defaults to the Windows 10 Media Creation Tool when ran on a Windows PC and reverts to Direct Download Links when ran on Linux. The Workstation Editions aren't covered in the Media Creation Tool. To get the Direct Download Links on a Windows PC, one can either switch their browser to mobile view or use the Windows ISO Download Tool which offers all Versions of Windows 10.

  • Windows 10 Download Page (Version 2004)
  • Insider Preview ISO
  • Windows ISO Download Tool (All Older Windows 10 Versions…)

Windows 10 Download Page

The Windows 10 Download Page has the following form on a Windows 7/8.x/10 PC and defaults to the Windows 10 Media Creation Tool.

On a non-Windows 10 PC it will have the following form and defaults to direct download links.

The Windows 10 Media Creation Tool downloads a series of setup files on your computer, checks the integrity of the downloaded files and creates an ISO from them. This ISO has a unique checksum as it has a unique time of creation. It has an install.swm smaller than 4 GB.

The direct download links are of ISOs created by Microsoft and you should ensure that the checksum matches the checksum provided on their download page. These ISOs have slightly more Windows 10 editions however these are for Workstations and less commonly used for Home PCs. As a consequence they have an install.wim that exceeds 4 GB. 4 GB is the upper limit for FAT32 and as a result some additional steps need to be carried out to make installation media that passes Secure Boot.

Using the Media Creation Tool

Note the Version of the Media Creation Tool. It should be Version 2004. Double click the Windows 10 Media Creation Tool.

Accept the User Account Control:

Accept the License Agreement:

Select Create Installation Media (for another PC) and then select Next:

The Language, Architecture and Edition will match that currently installed. To change it uncheck the "Use Recommended Options for this PC Box" and amend to your own preferences. Select Next:

Select ISO file and then select Next:

Change the folder to Downloads and add the Version number to the file name and then select save.

It will download Windows 10 setup files, check the integrity of the files it downloaded and then create a ISO from the installation files. Note because the ISO is created on your computer at a unique time/date it is a unique ISO and has a unique ISO checksum.

You can select Finish to close the Windows 10 Media Creation Tool. Ignore any prompt about DVD burning. Optical Drives are obsolete and in the few systems that have them, they normally a Legacy Only Boot Device.


The Direct Download Links will automatically display on a non-Windows PC. If you want the direct download links on a Windows 10 PC. On Google Chrome or Chromium Edge press [F12] to open developer tools and toggle the view to a Mobile Device.

Then refresh the page:

You can then close developer tools and use the website as normal:

You will now get the direct download links.

Select Windows 10 and then Confirm. Then select your Language and then select Confirm. Note English International = English (UK) and English = English (US).

Select Verify your Download to get a list of SHA256 for each ISO:

You can use this to check the integrity of your download.


Insider Preview Download Page

There are three Windows Insider Channels and one Mainstream Channel:

  • The Active Development Channel (Previously Known as Fast Track)
  • The Beta Channel (Previously Known as Slow Track)
  • The Release Preview Channel
  • The Mainstream Channel

There are sometimes newer installation ISOs available for these channels (although the ISOs are newer, Windows Insider Preview Builds are likely to contain bugs as they have had limited testing compared to Mainstream Channel ISOs.):

The Active Development Channel is an untested new build of Windows 10. The Active Development Channel Windows 10 builds will contain new features and as a result Microsoft now refer to new builds as feature updates. The Active Development channel has a new feature update released approximately every 2 weeks. As it is untested, there may be some generic problems and some hardware specific problems resulting in possible boot issues in some cases.

Not all experimental features of the Active Development Channel are popular or stable. The features that are deemed both popular and stable are then passed onto the Beta Channel for extended testing. Beta Channel users will therefore obtain feature updates less often. However cumulative updates and security patches will be issued to increase the quality of the features and overall Windows 10 stability. These updates are hence referred to as quality updates.

Approximately every 6 months, Microsoft creates a new Windows 10 Mainstream Channel Build. The Release Preview Channel tests this Build normally 1-2 months in advance and Microsoft issue quality updates to increase the overall quality, security and stability of the build. When Microsoft are satisfied with the overall quality, updates are released to the mainstream.

For more information about the three Insider Channels see:

Windows ISO Download Tool (All Previous Versions/Builds)

The Windows ISO Download Tool can be used to Download all Previous Versions of Windows 10 or Insider Preview. Note that the Mainstream builds don't expire whereas the Windows Insider Preview builds only remain activated within a time window. In most cases it is not recommended to remain on an older build however for those running really old computers, Version 1709 is the last build that will run on their computer due to elevated system requirements introduced in later versions.

If you have came here looking for an older build as your Windows 10 recently installed an update and can no longer boot try to use the Advanced Boot Options settings to uninstall the Feature Update or Quality Update before attempting a complete OS clean install:

Click to see English (UK and US) checksums.

Windows 10 VersionISO NameMD5Editions
Version 1909 (October 2019) 64 Bit UKWin10_1909_EnglishInternational_x64.isod1f08aea37586702f6fbe2fe3ea8c3fdAll
Version 1909 (October 2019) 32 Bit UKWin10_1909_EnglishInternational_x32.iso989260c78055cadf4355573c7f1a1685All
Version 1909 (October 2019) 64 Bit USWin10_1909_English_x64.iso86c16116ebacf9b29e4766dd479b5a79All
Version 1909 (October 2019) 32 Bit USWin10_1909_English_x32.iso989260c78055cadf4355573c7f1a1685All
Version 1903 (September 2019 V2) 64 Bit UKWin10_1903_V2_EnglishInternational_x6439979067eeea4d0076154bac01204fd6All
Version 1903 (September 2019 V2) 32 Bit UKWin10_1903_V2_EnglishInternational_x326f1f137df072040577eb74219b72930fAll
Version 1903 (September 2019 V2) 64 Bit USWin10_1903_V2_English_x64ba2e91ee7dab4b1415e4120a5c4fabedAll
Version 1903 (September 2019 V2) 32 Bit USWin10_1903_V2_English_x32053d13e06d9955701ffab1f03207b220All
Version 1903 (April 2019 V1) 64 Bit UKWin10_1903_V1_EnglishInternational_x6489bb55da144709a3e1446026fa139b6dAll
Version 1903 (April 2019 V1) 32 Bit UKWin10_1903_V1_EnglishInternational_x320d34450acd5c2843a61cb6fb815e3e67All
Version 1903 (April 2019 V1) 64 Bit USWin10_1903_V1_English_x648ba0e81b276d9052e8538deb0cf6c7d0All
Version 1903 (April 2019 V1) 32 Bit USWin10_1903_V1_English_x325520dad27b89fa7ddd9168c58378a948All
Version 1809 (March 2019 V2) 64 Bit UKWin10_1809Oct_v2_EnglishInternational_x641ee374d3c95ce1cdaf363508fd948ebdAll
Version 1809 (March 2019 V2) 32 Bit UKWin10_1809Oct_v2_EnglishInternational_x32 888faafbe80f7e9f857502e74502f404All
Version 1809 (March 2019 V2) 64 Bit USWin10_1809Oct_v2_English_x64ab22088758dbc5a13247ffc64c36f9a8All
Version 1809 (March 2019 V2) 32 Bit USWin10_1809Oct_v2_English_x323157760c5db52c81bc057f7608857141All
Version 1809 (October 2018 V1) 64 Bit UKWin10_1809Oct_EnglishInternational_x64a1f0c9af54c5c954fc6d7cec9bb8ef23All
Version 1809 (October 2018 V1) 32 Bit UKWin10_1809Oct_EnglishInternational_x32f05f5a4dfb3eaabd5dbad78175bf84b5All
Version 1809 (October 2018 V1) 64 Bit USWin10_1809Oct_English_x647a19f70f948614b55b716a6ee0ca5274All
Version 1809 (October 2018 V1) 32 Bit USWin10_1809Oct_English_x32663e18f44a8e799f538d8c6ed5d4f520All
Version 1809 (September 2018 V0) 64 Bit UKWin10_1809_EnglishInternational_x6407d63f6600f07e54837e84f2760022cfAll
Version 1809 (September 2018 V0) 32 Bit UKWin10_1809_EnglishInternational_x3243a1ea5fede1a53d8f737280f19cd7b2All
Version 1809 (September 2018 V0) 64 Bit USWin10_1809_English_x649065bb606708828266da06fcba9e9af2All
Version 1809 (September 2018 V0) 32 Bit USWin10_1809_English_x3213993a58b8861d398f28210642e24cbcAll
Version 1803 (April 2018) 64 Bit UKWin10_1803_EnglishInternational_x64318836e71c148d7f4ab3183f998ade21All
Version 1803 (April 2018) 32 Bit UKWin10_1803_EnglishInternational_x328edf94c78529126a0360660a8b6fb62aAll
Version 1803 (April 2018) 64 Bit USWin10_1803_English_x64986e2e17cf6b0b49141cd15699768e6eAll
Version 1803 (April 2018) 32 Bit USWin10_1803_English_x32166d99b85390d58017dc0bef14e5f8ebAll
Version 1709 (September 2017) 64 Bit UKWin10_1709_EnglishInternational_x64a94f0f77b4ec604d33a389f72684953cAll
Version 1709 (September 2017) 32 Bit UKWin10_1709_EnglishInternational_x326e82ac3d9313cf2e7e93fe81cb2d6099All
Version 1709 (September 2017) 64 Bit USWin10_1709_English_x645e8bdef20c4b468f868f1f579197f7cfAll
Version 1709 (September 2017) 32 Bit USWin10_1709_English_x8698b59f9927eb0aecc10526e08c70f907All
Version 1703 (March 2017) 64 Bit UKWin10_1703_EnglishInternational_x64a73f174bcfd1d260285264b2e437a124Pro&Home
Version 1703 (March 2017) 64 Bit UKWin10_1703_SingleLang_EnglishInternational_x6406927b21a0fc844cefb13660b98163f3HomeSL
Version 1703 (March 2017) 64 Bit UKWin10_1703_N_EnglishInternational_x6423240021549194e018ca37b9d4de0f59ProN&HomeN
Version 1703 (March 2017) 32 Bit UKWin10_1703_EnglishInternational_x3287ecc4375d82fd0800d1d3e6075b2a35Pro&Home
Version 1703 (March 2017) 32 Bit UKWin10_1703_SingleLang_EnglishInternational_x32c8d56ecaa3ff216d406e709a6220b966HomeSL
Version 1703 (March 2017) 32 Bit UKWin10_1703_N_EnglishInternational_x32c189254197b89508c6e13d319fecff5cProN&HomeN
Version 1703 (March 2017) 64 Bit USWin10_1703_English_x64effccfda8a8dcf0b91bb3878702ae2d8Pro&Home
Version 1703 (March 2017) 64 Bit USWin10_1703_SingleLang_English_x64 c10477812d9280f8546a618c9ce4778dHomeSL
Version 1703 (March 2017) 64 Bit USWin10_1703_N_English_x64 96b458cb0f721a4841b6fa7c4687c987ProN&HomeN
Version 1703 (March 2017) 32 Bit USWin10_1703_English_x326c8bd404dd95a286b3b3ef3a90e2cb34Pro&Home
Version 1703 (March 2017) 32 Bit USWin10_1703_SingleLang_English_x32fc8bbdf6a461927bb06fc34c4d41acbcHomeSL
Version 1703 (March 2017) 32 Bit USWin10_1703_N_English_x32138507f14d5cdb3f1089f9f7e14f5953ProN&HomeN
Version 1607 (July 2016) 64 Bit UKWin10_1607_EnglishInternational_x6457532598fd918fec63b287ea4228515ePro&Home
Version 1607 (July 2016) 64 Bit UKWin10_1607_SingleLang_EnglishInternational_x64c388062598df063f1f53ef76ef2f4176HomeSL
Version 1607 (July 2016) 64 Bit UKWin10_1607_N_EnglishInternational_x6481b4a6b5bf5601915e8f63ef76d58c12ProN&HomeN
Version 1607 (July 2016) 32 Bit UKWin10_1607_EnglishInternational_x325d0f70f267d7c48411a2af9126f2a0f5Pro&Home
Version 1607 (July 2016) 32 Bit UKWin10_1607_SingleLang_EnglishInternational_x326577a006bcb1bcb71cbbdf3128f82812HomeSL
Version 1607 (July 2016) 32 Bit UKWin10_1607_N_EnglishInternational_x322cafc511e94e33c97fd4d405bccfc36fProN&HomeN
Version 1607 (July 2016) 64 Bit USWin10_1607_English_x6488b98698600511dcd69596df92b242e5Pro&Home
Version 1607 (July 2016) 64 Bit USWin10_1607_SingleLang_English_x64 566354bc12d351693db22d830baa764eHomeSL
Version 1607 (July 2016) 64 Bit USWin10_1607_N_English_x64 ba94bfd1c2bffcc61abaa4f6e7a0f9dbProN&HomeN
Version 1607 (July 2016) 32 Bit USWin10_1607_English_x324fee637ee28f5ef78d451bdeb8a5b82cPro&Home
Version 1607 (July 2016) 32 Bit USWin10_1607_SingleLang_English_x3298cf5797ecf2b5dc2253f19d9975d837HomeSL
Version 1607 (July 2016) 32 Bit USWin10_1607_N_English_x325083839a428140304484b77f204ee0eaProN&HomeN
Version 1511 (April 2016 V2) 64 Bit UKWin10_1511_2_EnglishInternational_x64cf6179ef39b3fc828b23c57ff7c49aadPro&Home
Version 1511 (April 2016 V2) 64 Bit UKWin10_1511_2_SingleLang_EnglishInternational_x641a9531ce573f0198e80454320ce68abfHomeSL
Version 1511 (April 2016 V2) 64 Bit UKWin10_1511_2_N_EnglishInternational_x64101089f7fecd5cf18be13df88a507debProN&HomeN
Version 1511 (April 2016 V2) 32 Bit UKWin10_1511_2_EnglishInternational_x327c710c8f47df13102606d73a26101174Pro&Home
Version 1511 (April 2016 V2) 32 Bit UKWin10_1511_2_SingleLang_EnglishInternational_x322b28e2c41d2c10af9ed72b13d6cae967HomeSL
Version 1511 (April 2016 V2) 32 Bit UKWin10_1511_2_N_EnglishInternational_x32bc8fa7e4cecf160dee877d1f49e7eef2ProN&HomeN
Version 1511 (April 2016 V2) 64 Bit USWin10_1511_2_English_x643ca03a2c59ae5b58ca965a345d4f2ae1Pro&Home
Version 1511 (April 2016 V2) 64 Bit USWin10_1511_2_SingleLang_English_x64 a68197de867de355ca5a353414bd45bcHomeSL
Version 1511 (April 2016 V2) 64 Bit USWin10_1511_2_N_English_x64 87bb37ed24afc66e484f53a143206b15ProN&HomeN
Version 1511 (April 2016 V2) 32 Bit USWin10_1511_2_English_x3291565f54dc7a4e1df8a5f2b913d869b1Pro&Home
Version 1511 (April 2016 V2) 32 Bit USWin10_1511_2_SingleLang_English_x32552335b52d880cb955ad5d7782380d9aHomeSL
Version 1511 (April 2016 V2) 32 Bit USWin10_1511_2_N_English_x32e2b9545dff0e8ed8bebdffa577eadd90ProN&HomeN
Version 1511 (October 2015 V0) 64 Bit UKWin10_1511_1_EnglishInternational_x64b4140f914b656783c531871b2629c6a5Pro&Home
Version 1511 (October 2015 V0) 64 Bit UKWin10_1511_1_SingleLang_EnglishInternational_x649a9dcb4ed3734718c64a7f48f105c876HomeSL
Version 1511 (October 2015 V0) 64 Bit UKWin10_1511_1_N_EnglishInternational_x649a9dcb4ed3734718c64a7f48f105c876ProN&HomeN
Version 1511 (October 2015 V0) 32 Bit UKWin10_1511_1_EnglishInternational_x3279359383be6bba1c553ed9380c00f42ePro&Home
Version 1511 (October 2015 V0) 32 Bit UKWin10_1511_1_SingleLang_EnglishInternational_x329382af15a0038c3d26103268b03998c5HomeSL
Version 1511 (October 2015 V0) 32 Bit UKWin10_1511_1_N_EnglishInternational_x32901986b82f660e274af14f4863cab30cProN&HomeN
Version 1511 (October 2015 V0) 64 Bit USWin10_1511_1_English_x64a4fde74732557d75ffc5354d0271832ePro&Home
Version 1511 (October 2015 V0) 64 Bit USWin10_1511_1_SingleLang_English_x64 d25924c16404040849a2a8c6c894e26eHomeSL
Version 1511 (October 2015 V0) 64 Bit USWin10_1511_1_N_English_x64 7ce47983293069d02b539dc05c559a98ProN&HomeN
Version 1511 (October 2015 V0) 32 Bit USWin10_1511_1_English_x3248110a8ea54e78f10124c74cb3bfd706Pro&Home
Version 1511 (October 2015 V0) 32 Bit USWin10_1511_1_SingleLang_English_x32913e733ebdc31141e4a1954be78f6aa4HomeSL
Version 1511 (October 2015 V0) 32 Bit USWin10_1511_1_N_English_x3247495a3e4b09b3bd9ec9edac7158b189ProN&HomeN
Version 1511 (October 2015 V0) 64 Bit UKWin10_1511_EnglishInternational_x643c45cb361bf29098c2536e14a2be6f1cPro&Home
Version 1511 (October 2015 V0) 64 Bit UKWin10_1511_SingleLang_EnglishInternational_x64548e82f78f1ec7c7c9456aa16aa16254HomeSL
Version 1511 (October 2015 V0) 64 Bit UKWin10_1511_N_EnglishInternational_x6415279a6c52f6eca9f5234698226de684ProN&HomeN
Version 1511 (October 2015 V0) 32 Bit UKWin10_1511_EnglishInternational_x32808da353b2277806f50a286903591258Pro&Home
Version 1511 (October 2015 V0) 32 Bit UKWin10_1511_SingleLang_EnglishInternational_x322170e29284bd0c823be716f8fb64bf17HomeSL
Version 1511 (October 2015 V0) 32 Bit UKWin10_1511_N_EnglishInternational_x32a07c0acd6d11270fe4fb575a7433921bProN&HomeN
Version 1511 (October 2015 V0) 64 Bit USWin10_1511_English_x64a0d4271b7537732a060909fd39d54829Pro&Home
Version 1511 (October 2015 V0) 64 Bit USWin10_1511_SingleLang_English_x64 e7c597a3989c3d135181ed6e226c876cHomeSL
Version 1511 (October 2015 V0) 64 Bit USWin10_1511_N_English_x64 65a0ff50179323d2866123cbb658acd5ProN&HomeN
Version 1511 (October 2015 V0) 32 Bit USWin10_1511_English_x3291fad72bb84ee259cdb1772b2ce42375Pro&Home
Version 1511 (October 2015 V0) 32 Bit USWin10_1511_SingleLang_English_x3266bb8070415e404707b32649aa3f5853HomeSL
Version 1511 (October 2015 V0) 32 Bit USWin10_1511_N_English_x3288de7f34363da72c9628fd965585136bProN&HomeN
Version 1507 (July 2015 V0) 64 Bit UKWin10_EnglishInternational_x640fcc367c530f41c77cb7043fe29ae9eaPro&Home
Version 1507 (July 2015 V0) 64 Bit UKWin10_SingleLang_EnglishInternational_x64aea0810813ced5e7d72492c59ef9b5ecHomeSL
Version 1507 (July 2015 V0) 64 Bit UKWin10_N_EnglishInternational_x6406525e96735cb4d956974f79440e9769ProN&HomeN
Version 1507 (July 2015 V0) 32 Bit UKWin10_EnglishInternational_x32c945abe032e3e9f95d2a93581a3dd613Pro&Home
Version 1507 (July 2015 V0) 32 Bit UKWin10_SingleLang_EnglishInternational_x32c4a328ac72be7bf02a9320fe8863ee54HomeSL
Version 1507 (July 2015 V0) 32 Bit UKWin10_N_EnglishInternational_x329fc9482470db21a6584dbaadb1f0284fProN&HomeN
Version 1507 (July 2015 V0) 64 Bit USWin10_English_x6423e397a21a9e01f141c64b7e1260314aPro&Home
Version 1507 (July 2015 V0) 64 Bit USWin10_SingleLang_English_x64 66bc453f12236b89438c90d6e5c3bdcfHomeSL
Version 1507 (July 2015 V0) 64 Bit USWin10_N_English_x64 e02b45f2801801a42b79ee4ca5db74edProN&HomeN
Version 1507 (July 2015 V0) 32 Bit USWin10_English_x3299feb0f9e7262b7eefa460840a31b59dPro&Home
Version 1507 (July 2015 V0) 32 Bit USWin10_SingleLang_English_x32dce5cb714f79ab2094e54f52d28b218dHomeSL
Version 1507 (July 2015 V0) 32 Bit USWin10_N_English_x324935e4793b7003c498d6f3d4f315df36ProN&HomeN


UEFI BIOS Settings

You may or may not have these technologies depending on the age of your system.

If using your Computer to Download Windows and make the Bootable USB, do not change the UEFI BIOS Settings until you have created the Bootable USB.

It is recommended to update the UEFI BIOS before clean installing Windows 10. This can be done using a USB Flash Drive in newer models or a FreeDOS Bootable USB in older models.

Dell UEFI BIOS

For reference:

  • OptiPlex 390/790 – 2011 (2nd generation Sandy Bridge) UEFI BIOS – No Secure Boot, there is no option for Legacy ROMs as these are always Enabled
  • OptiPlex 3010/7010 – 2012 (3rd generation Ivy Bridge) UEFI BIOS with Secure Boot (only with the latest UEFI BIOS Update)
  • OptiPlex 7020 – 2014 (4th generation Intel Haswell) UEFI BIOS with Secure Boot
  • OptiPlex 7040 – 2015 (6th generation Intel Skylake) UEFI BIOS with Secure Boot

On a Dell system press [F12] when powering to enter the Boot Menu. Other OEMs may use different usually function key combinations and have slightly different BIOS General User Interfaces.

Look for the term "Boot Mode" or "UEFI".

If these terms are not present on the Boot Menu you have a Legacy only BIOS.

Next look for the Secure Boot status (a handful of early UEFI systems don't have Secure Boot) such as the OptiPlex 790 boot menu below. These system will use a UEFI Boot that always enables Legacy ROMs:

In the UEFI Boot Menu above some systems will allow you to select Change Boot Mode Settings to UEFI without Secure Boot or Legacy Directly:

Windows 10 64 Bit should be installed using a UEFI Boot with Secure Boot (when supported by the hardware). A Windows 10 32 Bit install requires a Legacy Boot (Secure Boot Off). Note the Windows 10 32 Bit architecture is non-standard and many systems build in 2012 or later have only Windows 64 Bit Drivers.

Use this setting for Windows 10 64 Bit.
When using Rufus to make a Bootable USB use the GPT Partition Scheme.
Use this setting for Windows 10 32 Bit.
When using Rufus to make a Bootable USB use the MBR Partition Scheme.

In other systems you may need to enter the UEFI BIOS setup to amend the settings.

The BIOS setup can also be accessed directly using [F2] when powering up the Dell system:

Look for a tab called Secure Boot, expand it, select Secure Boot Enable and change the setting to Enabled for Windows 10 64 Bit and Disabled for Windows 10 32 Bit. Select OK at any warning dialog box:

Legacy Option ROMs should be Disabled for Windows 10 64 Bit. Go to the general tab and select Advanced Boot Options, ensure Enable Legacy Option ROMs and Enable Attempt Legacy Boot are unchecked. For Windows 10 32 Bit both these checkboxes should be checked:

Next go to Boot Sequence and ensure the Boot List Option is set to UEFI:

You can also expand the System Configuration and check the SATA Operation. In most cases for a single drive it should be AHCI. If you have an older system with a small 32-64 GB SSD Cache Drive and a large capacity HDD, you may have a different SATA Operation such as RAID On (Intel Rapid Response Technology). It is recommended in most cases to replace both drives with a large capacity >250 GB SSD for optimal performance:

You an have a look at your Drives. In my case I have a single 128 GB SSD:

Select Apply:

Press OK:

Then Exit:


Lenovo UEFI BIOS

For a Lenovo we will use a Lenovo P320 ThinkStation with a 6th Generation Intel Skylake Processor as an example. When powering up the system press [F12] to get to the UEFI Boot Menu:

There is no mention about Secure Boot so we will have to Enter the Setup to check, the setup can be accessed directly by powering up and pressing [F1]:

The setup may also tell you if a SLIC Version of 2.1 (OA2.1 Marker) is present.

Select the Security tab and then highlight Secure Boot:

Ensure that Secure Boot is Enabled for a Windows 10 64 Bit install and Disabled for a Windows 10 32 Bit Install:

Use this setting for Windows 10 64 Bit.
When using Rufus to make a Bootable USB use the GPT Partition Scheme.

To install Windows 10 32 Bit you will need to go to the Startup tab and change the Boot Options:

If Secure Boot is Enabled, CSM will be locked to Disabled and Boot Mode will be UEFI only which are the correct settings for Windows 10 64 Bit.

For Windows 10 32 Bit installation you will need to enable CSM (this is what Dell call Legacy Roms):

A Legacy Boot must be used for Windows 10 32 Bit.

Use this setting for Windows 7 32 Bit.
When using Rufus to make a Bootable USB use the MBR Partition Scheme.


HP UEFI BIOS

When powering up press [F9] to get the Boot Menu and [F10] to get to the UEFI BIOS setup. On some older systems you need to power up pressing [Esc] to get to a startup menu which you can use to access the BIOS setup or Boot Menu respectively.


Creating a Bootable USB

Instructions to create a Bootable USB depend on the Partitions Scheme (UEFI or Legacy), method used to Download the ISO (Media Creation Tool, Direct Download, Insider Preview) and Operating System to make the Bootable USB on (Windows or Linux).

On Windows

Rufus can be used directly to create the Bootable USB from the ISO Downloaded from the Windows 10 Media Creation Tool however additional workarounds will be required for the ISO downloaded via direct links as the install.wim exceeds 4 GB (the maximum size for FAT32).

Creating a UEFI Bootable USB – Windows 10 Media Creation Tool ISO

Double click Rufus to launch it:

Accept the User Account Control Prompt:

Insert your USB Flash Drive and make sure it is populated under Devices:

Select, select:

Select the Windows2004 ISO and select Open:

Change the Volume Label to something more meaningful like Win-2004:

In order for the Bootable USB to Boot using a UEFI BIOS with Secure Boot (standard for all computers build after 2012) the Partition Scheme must be GPT and FAT32.

Select Start:

Select OK to begin creating the Bootable USB:

When it is Finished it will have a Status of Ready. You can now close Rufus.


Double click Rufus to launch it:

Accept the User Account Control Prompt:

Insert your USB Flash Drive and make sure it is populated under Devices:

Select, select:

Select the Windows2004 ISO and select Open:

Select the checksum button to view the Checksum:

The SHA256 should match the one that Microsoft provide:

We can change the volume label to something more sensible.

The Bootable USB cannot be created directly with Rufus as it has an install.wim file which exceeds 4 GB. As a result Rufus will use the NTFS file system which will be rejected by Secure Boot.

We will instead use Rufus to setup a USB Flash Drive to use the GPT Partition Scheme and to be FAT32 Formatted and manually copy the Windows Installation files over with the install.wim being split between a install.swm and install2.swm file.

Change the Boot Selection to Non-Bootable. Ensure the Partition Scheme is GPT and ensure the File System is FAT32:

Select Start:

Select OK to Create the Blank USB:

When done it will say Ready. Select Close:

Delete the two autorun files on the Bootable USB:

Select Yes at the dialogue.

Now right click the ISO and select Mount (Windows 7 doesn't have the ability to mount ISOs directly. if making the Bootable USB on Windows 7 you will need to install Virtual Clone Drive in order to mount ISOs).

Copy the entire contents of the ISO (except for the install.wim within the sources folder):

And then paste to the USB:

You will be informed that the install.wim is too large to fit on the file destination system (FAT32). Select Skip:

Go to the sources folder of the mounted ISO and Copy the install.wim.

Paste it directly to C:\

Select Continue to allow permissions:

Right click the install.wim and select Properties:

Ensure Read Only is not checked then select Apply:

Then select Continue:

Windows 10

We need to use PowerShell to split the install.wim file into multiple install.swm files that are less than 4 GB.

Now right click the start button and select Windows PowerShell (Admin):

Accept the User Account Control Prompt:

This can be done by using the following command:

Dism /Split-Image /ImageFile:C:\install.wim /SWMFile:C:\install.swm /FileSize:4000

You may now close down the Powershell Prompt.

Windows 7 and Windows 8.1

Windows 7 DISM is out of date and does not include the split command.

We can get the functionality by using the wimlib library instead. Download the latest zip file for Windows. It should end in Windows-x86_64-bin.zip file.

Extract the folder and rename the extracted folder wimlib and copy it directly to the C:Drive

Go to the start menu and search for CMD, right click it and select Run As Administrator.

Accept the User Account Control:

Type in the following to change directory to the wimlib folder

CD C:/wimlib

Type in the following command to split the install.wim:

wimlib-imagex split C:/install.wim C:/install.swm 4000

You now have multiple install.swm files:

Now copy install.swm and install2.swm:

To the sources folder of the USB Flash Drive:

Your Windows 10 Bootable USB is now ready.


Creating a UEFI Bootable USB with Driver Pack Slipstream – Direct Download ISO

Note these instructions do not work on Windows 7 which has an older version of DISM.

Double click Rufus to launch it:

Accept the User Account Control Prompt:

Insert your USB Flash Drive and make sure it is populated under Devices:

Select, select:

Select the Windows2004 ISO and select Open:

Select the checksum button to view the Checksum:

The SHA256 should match the one that Microsoft provide:

We can change the volume label to something more sensible.

The Bootable USB cannot be created directly with Rufus as it has an install.wim file which exceeds 4 GB. As a result Rufus will use the NTFS file system which will be rejected by Secure Boot.

Note if using a Legacy Only BIOS you can change the Partition Scheme to MBR and leave the File System to NTFS and proceed using Rufus.

We will instead use Rufus to setup a USB Flash Drive to use the GPT Partition Scheme and to be FAT32 Formatted and manually copy the Windows Installation files over with the install.wim being split between a install.swm and install2.swm file.

Change the Boot Selection to Non-Bootable. Ensure the Partition Scheme is GPT and ensure the File System is FAT32:

Select Start:

Select OK to Create the Blank USB:

When done it will say Ready. Select Close:

Delete the two autorun files on the Bootable USB:

Select Yes at the dialogue.

Now right click the ISO and select Mount (Windows 7 doesn't have the ability to mount ISOs directly. if making the Bootable USB on Windows 7 you will need to install Virtual Clone Drive in order to mount ISOs).

Copy the entire contents of the ISO:

And then paste to the USB:

You will be informed that the install.wim is too large to fit on the file destination system (FAT32). Select Skip:

Go to the sources folder of the mounted ISO and Copy the install.wim.

Paste it directly to C:\

Select Continue to allow permissions:

Right click the install.wim and select Properties:

Ensure Read Only is not checked then select Apply:

Then select Continue:

We need to use PowerShell to split the install.wim file into multiple install.swm files that are less than 4 GB.

For select business models (OptiPlex, Latitude, Precision and XPS) you also have the option to download the Dell Driver Cab and we can slipstream this into the install.wim using a handful of lines of code. You will also need to download and install 7-zip in order to extract the drivers folder.

This guide focuses more on the Dell systems but it will also work with the Lenovo Business model if you rename the extracted folder Drivers and move it to the C:\ Drive the procedure will be identical.

On the Dell website select your model and then select Windows 10 64 Bit under Operating System and then Systems Management under category.

Select the Driver Pack and select Download:

You will need to extract these drivers. I recommend using 7zip for this.

Right click the CAB file and select 7-Zip and then Extract to " ":

You may get the Warning "There are some data after the end of the payload data". You can ignore this and select Close:

Open the extracted folder:

Select the model:

Select the Win10 folder:

You should now have an x64 folder.

Right click this folder and select rename, rename the folder

Drivers

Copy this folder directly to:

C:\

You should now have the following:

Now right click the start button and select Windows PowerShell (Admin):

Accept the User Account Control Prompt:

Copy the following command:

Dism /Get-WimInfo /WimFile:C:\install.wim

Right click the file and select run as administrator. Select your index. I will select index 6 for Windows 10 Pro.

Copy and paste in the following command to create a temporary folder:

mkdir C:\WinTemp

Copy the following command (amending the index to desired) to extract the index of the install.wim to the temporary folder:

Dism /Mount-WIM /WimFile:C:\install.wim /index:6 /MountDir:C:\WinTemp

Type in the following command to add the drivers to this folder:

Dism /Image:C:\WinTemp /Add-Driver /Driver:C:\Drivers /Recurse

Type in the following command to commit the changes:

Dism /Unmount-WIM /MountDir:C:\WinTemp /Commit

Type in the following to remove the temporary folder:

rmdir C:\WinTemp

Type in the following to get the updated information about the install.wim

Dism /Get-WimInfo /WimFile:C:\install.wim

Type in the following to split the install.wim into multiple install.swm files:

Dism /Split-Image /ImageFile:C:\install.wim /SWMFile:C:\install.swm /FileSize:4000

You may now close down the Powershell Prompt:

Now copy install.swm and install2.swm:

To the sources folder of the USB Flash Drive:

Your Windows 10 Bootable USB is now ready.


Creating a Legacy BIOS USB – Media Creation Tool ISO

Double click Rufus to launch it:

Accept the User Account Control Prompt:

Insert your USB Flash Drive and make sure it is populated under Devices:

Select, select:

Select the Windows2004 ISO and select Open:

Change the Volume Label to something more meaningful like Win-2004:

Older computers have a Legacy only BIOS and will only Boot from the USB if you use MBR and NTFS.

Select Start:

Select OK to begin creating the Bootable USB:

When it is Finished it will have a Status of Ready. You can now close Rufus.


Double click Rufus to launch it:

Accept the User Account Control Prompt:

Insert your USB Flash Drive and make sure it is populated under Devices:

Select, select:

Select the Windows2004 ISO and select Open:

Select the checksum button to view the Checksum:

The SHA256 should match the one that Microsoft provide:

We can change the volume label to something more sensible.

Ensure the Partition Scheme is MBR and the File System is NTFS:

Select Start:

Select OK to proceed making the Bootable USB:

When the Bootable USB is made Rufus will say Ready:

You may now close Rufus.


On Linux

On Linux we need to use GParted to make sure our USB Flash Drive is formatted as FAT32.

Then as the install.wim file exceeds 4 GB we need to use the wimtools library to split the install.wim file to multiple swm files that are below 4 GB so that they can fit within the constrains of the FAT32 file system. Once we have this, we can copy all the files over and will get a USB Flash Drive that can Boot in a UEFI BIOS and Pass Secure Boot.

To check the ISO checksums. Open up the terminal and type in:

cd Downloads

Replace filename with the filename of your ISO:

sha256sum filename.iso

Close the terminal after you have verified the checksum.

Right click the Windows 10 ISO file and select Open with Disk Image Mounter:

Open the mounted ISO and go to the sources folder:

Copy the install.wim over to Downloads. It exceeds 4 GB (the upper bound for a FAT32 file format):

We will need to split it using wimtools:

To install wimtools and gparted we need to use the terminal:

First we need to make sure the links to the repositories are up to date. To do this type in:

sudo apt-get update

On Fedora use dnf instead of apt-get.

Then [↵]

To authorise input your password and then input [↵].

Now type in:

sudo apt-get install wimtools

On Fedora use dnf instead of apt-get.

Followed by [↵].

Input:

y

Followed by [↵]

Input:

sudo apt-get install gparted

On Fedora use dnf instead of apt-get.

Followed by [↵]

Input:

y

Followed by [↵]

Both programs are now installed.

Now type in the following to split the install.wim into multiple .swm files:

wimlib-imagex split Downloads/install.wim Downloads/install.swm 4000

Followed by [↵]

Once finished you can close the terminal, we now have the two swm files:

Now we will launch GParted:

Input your password to authenticate:

To the top right, select your USB Flash Drive:

Right click it and if Format to is grayed out select Unmount.

Right click it and select Format to FAT32:

Then Apply:

Then Apply:

When done select Close:

Now copy all files from the ISO to the USB except the sources folder:

Create a new folder on the USB called sources:

Copy all the files from the sources on the ISO to the sources folder on the USB except for the install.wim which is too big for FAT32:

In its place copy the two .swm files:

Ensure all files are copied across there should be no progress indicator under the folder icon on the side panel.

You should now have a Bootable USB that can Boot within a UEFI BIOS with Secure Boot.


On Linux we need to use GParted to make sure our USB Flash Drive is formatted as NTFS.

To check the ISO checksums. Open up the terminal and type in:

cd Downloads

Replace filename with the filename of your ISO:

sha256sum filename.iso

Close the terminal after you have verified the checksum.

Right click the Windows 10 ISO file and select Open with Disk Image Mounter:

Open the mounted ISO and go to the sources folder:

To install gparted we need to use the terminal:

First we need to make sure the links to the repositories are up to date. To do this type in:

sudo apt-get update

Then [↵]

To authorise input your password and then input [↵].

Now type in:

sudo apt-get install gparted

Followed by [↵]

Input:

y

Followed by [↵]

Both programs are now installed, you can close the terminal.

Now we will launch GParted:

Input your password to authenticate:

To the top right, select your USB Flash Drive:

Right click it and if it is mounted, select Unmount.

Right click it and select Format to NTFS:

Then Apply:

Then Apply:

When done select Close:

Now copy all files from the ISO to the USB:

Ensure all files are copied across there should be no progress indicator under the folder icon on the side panel.

You should now have a Bootable USB that can Boot within a Legacy BIOS.


Clean Installation


Booting From Windows 10 Installation Media

Insert your Bootable USB into your Computer and Remove any other USB Storage Devices such as USB Sticks and External Hard Drives.

Power off your computer.

Power it up and press the key combination for your OEM to get to the Boot Menu.

  • For a Dell or Lenovo System this is [F12].
  • For a HP and other OEMs it is often [Esc] or one of the Function Keys [F1-F12].
This image has an empty alt attribute; its file name is 1.png

Preparing Boot Menu should Flash Up. If not and you are taken straight into Windows, you will need to power down and try again:

This image has an empty alt attribute; its file name is 2.png

If your system was built in 2012 or newer the next screen you should have should mention Boot Mode and Secure Boot. For optimal Security and Performance with Windows 10 64 Bit you should have these set to UEFI and ON respectively. See the UEFI BIOS Settings section above for more detail.

This image has an empty alt attribute; its file name is 3.png

Use the [↓] key to get to your Bootable USB and once it is highlighted press [Enter]

This image has an empty alt attribute; its file name is 4.png

You should see your OEM Logo:

This image has an empty alt attribute; its file name is 5.png

You should now see the following Windows screen.

The Language to Install is for informational purposes only and lists only a single option. To change it you need to Download the Windows 10 ISO of the Desired Language and begin the install with your new Windows 10 Bootable USB.

The Time and Currency Format and Keyboard or Input method can be changed to Australian or Canadian settings for example.

Once you have made the correct options select Next:

The next screen gives you the option to Repair your Computer. This guide focuses on Clean Installation however:

Your Windows Product Key

Select Install Now:

Windows 8.0/8.1/10 OEM Embedded Product Key

The next screen will say Setup is Starting and you will see an Hour Glass Appear.

Windows 10 will look for an embedded OEM Product Key. If present Windows 10 Installation Media will find the key, the key will dictate the Edition of Windows 10 to install and take you straight to the license agreement screen.

Windows 10 Installation Media treats Windows 8.0 OEM and Windows 8.1 OEM Product Keys as Windows 10 Product Keys.

Bypass OEM Embedded Product Key

In the background the Windows setup will look in order for:

  1. A PID.txt in the sources folder.
  2. An embedded OEM Product Key.

To bypass the embedded OEM product key you can create a text file within the sources folder of the Bootable USB called pid.txt.

Copy and paste the following into the text file. Note you can either use your retail key or the generic product keys below. Product Activation will only take place if your system has been activated before usually with a Retail Key. This activation mechanism is also commonly used for Windows 10 Insiders who tested the Windows 10 Insider Build 10130 and got Windows 10 Pro as a Free Upgrade.

Windows 10 Home

[PID]
Value=YTMG3-N6DKC-DKB77-7M9GH-8HVX7

Windows 10 Home N

[PID]
Value=4CPRK-NM3K3-X6XXQ-RXX86-WXCHW

Windows 10 Home SL

[PID]
Value=GH37Y-TNG7X-PP2TK-CMRMT-D3WV4

Windows 10 Pro

[PID]
Value=VK7JG-NPHTM-C97JM-9MPGT-3V66T

Windows 10 Pro N

[PID]
Value=2B87N-8KFHP-DKV6R-Y2C8J-PKCKT

Windows 10 Education

[PID]
Value=YNMGQ-8RYV3-4PGQ3-C8XTP-7CFBY

Windows 10 Education N

[PID]
Value=84NGF-MHBT6-FXBX8-QWJK7-DRR8H

Windows 10 Pro Education

[PID]
Value=8PTT6-RNW4C-6V7J2-C2D3X-MHBPB

Windows 10 Pro Education N

[PID]
Value=GJTYN-HDMQY-FRR76-HVGC7-QPF8P

Windows 7 OEM Printed Product Keys

The technology to embed a Product Key wasn't available when Windows 7 was released. Windows 7 OEM Keys were instead physically printed. The following screen will accept a Windows 7 Product Key however if Windows 10 has already been installed and activated then your systems hardware details are already stored with a Microsoft Product Activation Server. It will recognise your system and automatically reactivate Windows on it even without input of a Product Key. Select "I don't have a Product Key" and then either Windows 10 Home or Windows 10 Pro:

Windows 7 EditionWindows 10 Edition
StarterHome
Home BasicHome
Home PremiumHome
ProfessionalPro
UltimatePro

The Windows 7 Product Key can be used for the initial first time activation of Windows 10. If the Product Key has faded the GatherOSState application can be used instead.

The Code of Authenticity (CoA) was often found in the battery compartment of laptops for protection.

This image has an empty alt attribute; its file name is 3-2.png

These Product Keys can be used for a one time activation of Windows 10. During this one time activation, your systems hardware (motherboard) is registered with a Microsoft Product Activation Server. This activation server will remember your hardware any subsequent time you install Windows 10 and there will be no need for you to input a Product Key during installation.

If your Product Key has faded and you have never installed Windows 10 and are still running Windows 7. You will need to copy the GatherOSState.exe from the sources folder to the Windows 7 Desktop.

Ensure you are online and right click gatherostate.exe and run it as an administrator:

Accept the User Account Control Prompt:

If your Windows 7 OEM Install is genuine and you are connected to the internet, a genuineticket will be generated.

You can use this genuine ticket for Product Activation. Copy it over to your Bootable USB.

Once Windows 10 is installed from the Bootable USB, copy the GenuineTicket over to the following folder and then restart your Computer.

C:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket

Microsoft will check this folder upon startup and submit the genuine ticket and your system details to the Product Activation Server giving it the green light for Product activation. Once this is done you can clean install Windows 10 without a Product Key and it will activate when online. You won't need the GenuineTicket ever again.

The genuineticket will only work on the same computer it was generated on.

Unlicensed Mode: No Product Key and No OEM License

The Product Key can be skipped and Windows 10 will be installed unlicensed.

For an unlicensed install there will be a watermark on the bottom right hand side of the Desktop and at the bottom of Settings. Some minor personalisation settings will be grayed out but otherwise Windows 10 will be fully functional.

Some users have been running Windows 10 Unlicensed on old Windows Vista PCs since 2015. Microsoft recommend saving your money towards new hardware which will come with a Windows 10 OEM License opposed to spending money on a Full Retail License for a system whose hardware is at End of Life.

Windows 10 License Agreement

Accept the License Agreement then select Next:

Drive Options

THE NEXT STEP WILL RESULT IN DATA LOSS. DO NOT PROCEED IF YOU HAVE IMPORTANT DATA ON YOUR DRIVE.

Data Recovery

If you are reinstalling Windows because you cannot boot into your old Windows Installation use a Linux Fedora Live Bootable USB to Back all your files to an External Hard Drive.

Delete all Partitions and Format your Drive

You can use the Windows Setup to remove all previously existing partitions on tour drive. Highlight each partition and select Delete. Do this until all you have is Drive 0 Unallocated Space. Do not worry about any of the partitions being recovery partitions, they correspond to old versions of Windows and in any case won't work when a manual installation is performed. The Windows 10 will create all the additional partitions it needs during the Windows setup. Once you have deleted all the partitions select next to proceed with the install.