Universal MediaCreationTool.bat wrapper for ALL versions (1507 - 21H2)

Discussion in 'Windows 10' started by AveYo, Oct 3, 2018.

  1. jaladhjin

    jaladhjin MDL Novice

    Nov 26, 2013
    48
    3
    0
    Can this be used to upgrade W10 Home to Pro?
     
  2. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,693
    4,937
    60
    Yes, edition change is a feature. Rename the script from "MediaCreationTool.bat" to "Pro MediaCreationTool.bat" and it will always force upgrade to Pro. It's that simple.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,693
    4,937
    60
    #263 AveYo, Mar 16, 2022
    Last edited: Mar 17, 2022
    (OP)
    I have decided to rework the script in order to prevent issues stemming from non-canonical paths i.e. with special characters and accents that ntfs allows, but are particularly bad for scripts.
    Specially when elevation is involved (when even windows itself has troubles handling it).

    The updated script I just pushed should work around most issues I've managed to reproduce.
    Now C:\ESD is always used as a work folder, and the original script path is preserved and used when needing to create an iso.
    Some path I've used to run the script from and create iso:
    E:\@DATA\DATA\OLD\TE (S) T\! ` ~ @ % & ( ) [ ] { } + = ; ' ,\! ` ~ @ % & ( ) [ ] { } + = ; ' ,\w t f\MediaCreationTool (3).bat
    ;)

    Another notable change is that the script picks up a $ISO$ folder contents to add on the created media (instead of just the $OEM$ previously).
    So if you previously had stuff in $OEM$ folder next to the script, you need to move it inside $ISO$\sources\$OEM$

    There's more changes specific to Windows 11 in it's dedicated thread
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Super Spartan

    Super Spartan MDL Expert

    May 30, 2014
    1,582
    913
    60
    THANK YOU so much for your efforts!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,693
    4,937
    60
    clean-slate stable version up - it's finally in the form I've envisioned it when I started the last rework
    hopefully I haven't misses any outstanding issues and I can go back to once in a blue moon maintenance ;)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. oceansalt

    oceansalt MDL Novice

    Mar 26, 2017
    41
    31
    0
    @BAU,

    Thanks to the MediaCreationTool.bat, Auto-upgraded the Windows 10 (in a H81 mainboard, i5-4570 CPU) to Windows 11.

    While I already had the Win11 WIM file in my disk, I had to wait for MCT to download it.
    Is it possible to start the "auto-upgrade" process by drag-and-drop a WIM/ESD/ISO file onto the MediaCreationTool.bat?

    Details:

    MCT is always going to download and install the lastest ESD file. However I wanted the existing install.WIM/ESD file on my disk to use it. I've created a symbolic link to the following paths:
    Take no notice of that. MCT persistently downloads the ESD link in CAB->XML it receives from MSoft server.

    I'm aware of the extra coding for both file extensions. For install.WIM/ESDs, Dynamic Update needs to be downloaded. For ISO, mounting. (I hope it is possible to MCT detects the sources\Install.wim/esd in mounted without extracting ISO)

    Thank you also for the "auto-upgrade" feature and "Auto.cmd". I wish we could use this feature with the drag-and-drop method. It would save time.
     
  7. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,693
    4,937
    60
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,693
    4,937
    60
    Well, 11 has kinda taken over.

    But this script's initial focus was supporting older versions, and I have been busy doing just that.
    May 10th is closing in, and it will ax even more versions. End-Of-Support is not End-Of-Life, tho.
    I've been a strong supporter of running the latest windows for the added security benefits, but I've seen first-hand that it's not always achievable.
    Not all people are gullible idiots. Compensating with stricter online usage can be fine (until it's not :D)
    Anyway, plenty of machines will remain online, that for some reason or other can't upgrade to the newest offer in this accelerated WaaS world.
    20H2 is pushed aggressively on 1507 to 2004 atm, regardless of hardware incompatibilities or - well - user choice.
    20H2 Home and Pro goes EOS May 10th. What then? I can only assume 21H1 takes it's place, but that won't be a bump-less ride (there are still official upgrade holds).

    So in the upcoming script update, I'm gonna introduce REJECT FEATURE UPGRADES (and REJECT DRIVERS) even in the policy-crippled Home editions!
    And I'm not using a Sledgehammer to achieve that :p
    Stay tuned!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...