I downloaded the ISO directly from Microsoft. Twice. The MediaCreationTool wasn't used. A USB flash drive created from the ISO doesn't boot unless Secure Boot is disabled in the UEFI BIOS. All previous Win10 ISOs (USB flash drive) booted with Secure Boot enabled, even the one from 5 weeks ago. I also found the ISO was too large to burn to a DVD. Have others seen this issue?
My PC is too old have a BIOS with Secure Boot. However, the ISO built with Rufus does hang whenever the Windows logo (flag) is shown during startup. I had to update using a real DVD... (created with the update tool, since the downloaded ISO was indeed too large for a real disc, like 1803).
This is what I'm seeing in Rufus when I load the 1809 ISO - I don't have any UEFI systems atm, so can't actually reproduce this. [EDIT] I checked the USB I created with MediaCreationTool, it is formatted as FAT.
I just downloaded the MediaCreationTool and then the ISO. The ISO size was 3.78 GiB as opposed to 4.72 GiB for the recent ISO. Rufus gave the option of FAT32 or NTFS formatting so I chose FAT32. The UFD booted with Secure Boot enabled.
It's the same one I have here, downloaded through MCT. So the 4.72 one did not give the option of FAT format even if you set it to GPT?
No, it did not. NTFS only. Out of interest I created another UFD from today's ISO but chose NTFS formatting. It would not boot with Secure Boot enabled. Interesting.
I checked the 4.72 GiB ISO with Rufus again. Definitely only NTFS formatting. However the ISO from 5 weeks ago allows NTFS and FAT32 formatting. Its size is 4.46 GiB. Edit... Yesterday I installed a fresh Win 10 from a UFD with Secure Boot disabled. After the install completed, Secure Boot was enabled. All OK.
I downloaded the 4.7 ISO (had to wait... the download was limited to 1MB/s for some reason) and I'm seeing the same. The first obvious difference is that the 4.7 ISO uses install.wim (the older format), while the 3.7 one uses install.esd format - The wim file size exceeds FAT32 limit so the only option available to format the drive was NTFS. That would explain the 'NTFS only' option. As far as I know you can't boot from NTFS on a UEFI enabled system.
Looking at this again, it seems that the wim format is not just 'older' (wrong assumption) it is used for DISM deployment (Windows Deployment Services), while the esd supports high compression and encryption but is not scriptable. I always wondered about the label of my USB disk (ESD-USB), but never really looked into it. Now I know.
Seer, That is great info. It looks like I'll have to avoid directly downloading the ISO in the future. The MCT will save me a lot of headache. The NTFS formatted Win10 UFD does boot and Win10 can be installed but only if Secure Boot is disabled in the UEFI BIOS. After Win10 is up and running, Secure Boot can be re-enabled and Win10 will continue to boot. Edit... I looked at the NTFS UFD created by Rufus. Two partitions are present on the GPT disk. A 494 KiB FAT partition containing an EFI folder. The remainder of the drive contains a NTFS partition labelled ESD-ISO.
This would be the bootable one. A MCT created one contains only FAT. I don't have much experience with UEFI, but as I understand it the firmware needs an NTFS driver to be able to boot directly from it. Newer motherboards now support this.
I also had this problem once. I just edited the ISO and removed versions of windows, like Enterprise, that I don't have. And it works fine Unfortunately I can't look right now what programs I used, but I'm sure google will come up with something.
Author here: https://pureinfotech.com/windows-10-1809-iso-download/ came up with a way of getting a direct ISO download via Edge, Chrome, or Firefox. I tried the Edge method and everything was fine till this step: The correct non-supported Microsoft ISO download page displayed but was locked i.e. rotating arrow symbol shown. Then it refreshed to the original ISO download page: https://www.microsoft.com/en-us/software-download/windows10ISO . Tried multiple times with same results. Looks like Microsoft has shut this one down.
itman, I've always used that Edge method. I tried it a few minutes ago as a test and it is working here.
I had the debug screen open on the right hand side. The web page displayed for a few secs. or so on the left side of the screen and then redisplayed the original ISO download page.
itman, Have you tried other browsers? There is no point in keeping the wim build unless you're using DISM scripts to deploy customized Windows installations on multiple systems (like in a corporate environment i.e.). There's also a couple of 3rd party wim2esd converters (and vice versa) if you ever need to use scripting.
According to this article: https://pureinfotech.com/create-bootable-usb-windows-10/ , the recommended way to create Win 10 installation USB drive for Win 10 for a device with UEFI is: Also, the Rufus format specification in this example is FAT32.
i used MCT to cerate ISO - not WIM, and banned it on stick with rufus. ofc some can convert wim to iso, but thats complete nonsense if some want to use stick or dvd.
