AveYo’s MediaCreationTool

Topic

New Reply

Hey 1803 Upgraders,

I ran the MediaCreationTool1809.exe and got a windows.iso and did the upgrade. Everything went smooth but the Service Stack Update for 1809 would not run. The reason is, I am on 1909, so watch out!

Warning: This method is not working.

I still have another 1809 ISO from 6 months ago so I am going to try again.

The MediaCreationTool batch files was at https://pastebin.com/bBw0Avc4 . Probably worked well, until Microsoft changed it.

Reply | Quote

Replies

While we know that Heidoc.net’s MCT has proved to be safe (it sources Microsoft directly), the only other place I would ever consider getting it from would be Microsoft.

This is one of those occasions where you just can’t be too careful, and good computer security / hygiene should be at the front of users’ risk assessments!

There may well be other locations to source them, but do you get hash checksum values to check?

Reply | Quote

I tried getting the ISO via Heidoc.net’s MCT  and got 1909, then uninstalled it via Settings –> Recovery –> ~go back to previous build  (depends on your version: Home, Pro)

So it looks like you cannot get 1809 ISO and can only get 1909 via Microsoft, unless you or someone you know has it.

The other way to upgrade will be the 1903 Feature Upgrade.

Reply | Quote

Which download of Windows 10 did you select in the Heidoc options dropdown?

Reply | Quote

I could not get the executable to work and ended up at the web site, where I downloaded the MediaCreationTool1809.exe . Then the process is similar to AveYo’s MediaCreationTool .

I did a SHA256 hash of the two MediaCreationTool’s and the hashes are the same. Still I went to try the upgrade, to confirm the Windows.iso was 1909.

Reply | Quote

[KP]

Tried to uninstall 1809 and found you need to go through Recovery –> ~Previous Windows version; got back to 1803.

I had saved a 1809 ISO from Nov 2019 and upgraded to 1809. Upgrade seemed faster than the 1909 upgrade. I am on 1809, yahoo.

Reminder if you go thorough this process to run Windows Update MiniTool to check for other updates, after running the Service Stack Update and Monthly Cumulative Rollup. An example is KB4465065 Intel microcode updates.

• This reply was modified 5 years, 4 months ago by KP.

Reply | Quote

[EP]

speaking of the KB4465065 Intel microcode update, that update will not be offered if the newer 2019-08 KB4494174 intel microcode update is installed as KB4494174 supersedes/replaces KB4465065 – WU and WUMT don’t show nor offer KB4465065 because I have the newer KB4494174 update installed on all my computers that have either Win10 Pro v1809 or Win10 LTSC 2019 v1809.

• This reply was modified 5 years, 4 months ago by EP.

Reply | Quote

Typo Tried to uninstall 1809.

It should be 1909 uninstall.

Reply | Quote

see https://www.askwoody.com/forums/topic/whats-the-best-way-to-upgrade-from-windows-7-to-windows-10/#post-2036692 for info on Rufus and FIDO, worked for me, as it is a Powershell file that runs seems less of a risk than heidoc

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

I am summarizing what I have decided.

AveYo’s MediaCreationTool1809 is currently pointing to a 1909 ISO which is the same as https://www.microsoft.com/en-us/software-download/windows10 .

Heidoc.net’s MCT did not work for me; I must have something blocking it.

It looks like I tried Rufus 6 months ago and it did not work; something is blocking it.

My hesitation with PowerShell is you need to vet it and I am not well-versed with PowerShell. (I do not have Fido.ps1 working yet.) [Some malware use PowerShell script with a “-bypass” parameter.] Because this is posted on GitHub, I am guessing it is well vetted.

I am going to stick with changing the User Agent on the browser to download the Windows 10 ISO. If anyone know of any disadvantages (aside from changing the user agent back and forth), please post.

I like having all my defenses up:
host file
standard user privileges for downloading, and running Anti-Virus scan against the ISO, then upgrading Windows in admin mode.

Reply | Quote

Rufus is a boot disk builder, there is nothing you can do to block it as it uses local files and standard methods to create the boot disk/USB.

PowerShell scripts are the same as programs like MCT, except that you can see what the program will do (if you can read PowerShell). They are no more likely to contain a virus – possibly less likely because anyone competent reading the script would spot the malware immediately.

Why don’t you want to run 1909? Was it flakey when you last installed it?

cheers, Paul

Reply | Quote

Paul T wrote:

Rufus is a boot disk builder, there is nothing you can do to block it as it uses local files and standard methods to create the boot disk/USB.

… nothing except standard system permissions and misconfigured antimalware tools. (Seen things that blocked raw device writes for example, even to USB devices.)

Reply | Quote

I am choosing not to try Rufus with admin privileges, even though I had to use admin  access  with Microsoft’s Media Creation Tool.

I am using Windows Defender for AV so am guessing that it is not the problem.

Thanks for your thoughts.

 

Reply | Quote

Initially I thought the upgrade was on 1809 when the 1809 Service Stack Update did not work and realized it  was on 1909. Nothing seemed wrong with 1909.

I wanted to get onto 1809 because it seemed like the most stable version, no other reason.

I see Woody’s post today about 1903; I will consider moving to 1903 which I will have to do in 6 months anyways.

Reply | Quote