How to use MediaCreationTool.bat: install media and upgrade guide

What MediaCreationTool.bat is and what it changes

The script wraps Microsoft's Media Creation Tool. Its README describes it as a universal wrapper for Windows 10 and 11 versions from 1507 to 21H2, with support for business editions and deployment automation.

Because it wraps the official tool and changes its setup behaviour, it is not an officially supported Microsoft process. The README says the presets modify the media they create, so the output is not an untouched Microsoft download unless you choose the MCT Defaults preset.

• Works on Windows 10 or 11 only, since the script is a Windows batch file.
• Licence is MIT.
• Language is Batchfile.

Install MediaCreationTool.bat by cloning the repository

The project's install method is clone-and-build. The README gives this command to clone the repository:

• Run the clone command in a folder where you want the script to live.
• Run the script from that folder. The README says you do not need to right-click and choose Run as Admin, because the script asks for elevation itself.
• If you saved the raw file directly instead of cloning, the changelog notes that line endings no longer break.

Choose the right preset

The script offers five presets. Pick the one that matches your goal. The README lists them as follows.

• 1. Auto Upgrade: uses the detected media and helps set up an upgrade directly. It can keep files and apps in more scenarios where the OS and target edition do not match. It defaults to Windows 11, so pass the version for Windows 10.
• 2. Auto ISO: creates an ISO using the detected media in the current folder, or C:\ESD if run from a zip. You can override the detected media by adding edition, language or architecture to the script name.
• 3. Auto USB: uses the detected media and a USB target you specify. For data safety, you must select the USB drive manually in the GUI. It is not fully automated.
• 4. Select: you pick the edition, language and architecture (x86, x64 or both) and the target. It includes setup override files unless you add def to the script name.
• 5. MCT Defaults: runs unassisted and creates media without modifying the script output. The script passes products.xml to MCT and quits without touching the media.

Understand what presets 1 to 4 write to the media

Presets 1 to 4 modify the media they create. According to the README, they can write the following items. The README says you can disable these changes by adding def to the script name to get a default, untouched MCT media.

• auto.cmd, to run an auto upgrade on demand with edition switch and TPM skip.
• The $ISO$ folder content, if it exists, at the root of the media. If you previously used $OEM$ content, place it in $ISO$\sources\$OEM$\.
• sources\PID.txt, to preselect the edition at media boot or within Windows.
• sources\EI.cfg, to prevent the product key prompt on Windows 11 consumer media.
• AutoUnattend.xml in boot.wim, to enable a local account on Windows 11 Home.
• A patched winsetup.dll in boot.wim, to remove Windows 11 setup checks when booting from the media.

Run an unattended upgrade by renaming the script

The README says the Auto Upgrade preset is behind auto.cmd, and that you can run it fully unattended by renaming the script. The generated script is added to the media so you can run it again later.

The script detects editions in install.esd, picks a suitable index, and sets EditionID in the registry to match. It can also force another edition while keeping files and apps. The README says the original EditionID is backed up as EditionID_undo.

• Rename the script to auto MediaCreationTool.bat for a fully unattended run.
• Add an edition name to the script name to switch edition, for example ProfessionalWorkstation MediaCreationTool.bat.
• Pass a version for Windows 10, for example auto 21H2 MediaCreationTool.bat.
• Add a version and edition together, for example auto 21H2 Pro MediaCreationTool.bat, to upgrade several PCs to one edition.
• Add a VL, MAK or retail product key in the same way to handle licensing differences.

Troubleshoot an upgrade that fails

The README says you can troubleshoot a failing upgrade by adding no_update to the script name. It also says that if you had no success launching the script before, the latest version should work. Those statements are from the README; this guide cannot confirm outcomes on your hardware.

• Try the no_update option in the script name if an upgrade fails.
• If the Media Creation Tool itself will not launch, the README suggests trying this version of the script.
• Use MCT Defaults if you need unmodified Microsoft media.