Yeah, MCT don't export (rebuild) new install.wim, it just soft delete first 3 indexes (setup files + boot.wim after creating it), and rename original ESD to install.wim
Yes (with Windows 8.1 and first 2 or 3 Windows 10 versions, it was renamed install.wim although it's esd) their "point" is to deliver faster process, export / rebuild install.esd takes time and resources
Windows 10 Version 20H2 ESDs [19042.1706.220513-0540.20h2_release_svc_refresh] 664.0 GB Windows 10 Version 21H1 ESDs [19043.1706.220505-1151.21h1_release_svc_refresh] 580.0 GB Windows 10 Version 21H2 ESDs [19044.1706.220505-0136.21h2_release_svc_refresh] 580.0 GB Windows 10 Version 22H2 ESDs [19045.1826.220707-2303.22h2_release_svc_refresh] 580.0 GB Windows 10 Version 22H2 ESDs [19045.2006.220908-0225.22h2_release_svc_refresh] 721.0 GB Windows 10 Version 22H2 ESDs [19045.2965.230505-1139.22h2_release_svc_refresh] 727.0 GB
LTSB/C is not available as ESD. And LTSB/C is not really lighter on resources either. Here all LTSB/C threads are listed; https://forums.mydigitallife.net/th...rprise-n-ltsb-ltsc-download-discussion.84127/
Hmm, so which is just the fastest and the lightest ? Would it be 21h1 or IoT then ? I got a lil confused with all the mishmash ...
This is the ESD thread, only for discussing ESD files, downloads, content and conversion to ISO. Maybe start with reading the mentioned threads and the other sticky build threads.
Hi All, I have a question regarding the Windows 10 Version 22H2. On the 2nd post of this thread the links for the WSUS have been made available. I'm interested in the "Client Consumer Retail Windows 10 Pro" version. I understand that it's an ESD file and that it's need to be converted to ISO with the ESD>ISO tool. Now, can I also use the Windows 10 Installation Media tool to download the ISO itself directly into an USB flash drive instead? I currently don't have other computer than my company laptop, which is running Windows 10 Enterprise. If I do so, will it by default install the same Windows version under which I created the ISO (Enterprise in my case) or will I be able to chose which version when installing ? Kind regards, Ken
The MCT only downloads the latest Consumer ESD (19045.2006) and creates ISOs with install.esd (not serviceable). Consumer ESDs don't contain Enterprise. In the past you could upgrade 10 Enterprise by using Pro but didn't test that anymore lately.
Thank you for quick reply Enthousiast! I can see that the version in the link for the WSUS is 19045.2006.220908-0225. I'm afraid that I don't understand what you mean with "not serviceable", is this WSUS related ? Cheers
install.esd is not serviceable, install.wim only, so when you plan on servicing (offline updating and such) best to download the desired ESD and convert it manually (it will give you options). When you simply want to use the MCT ISO, no problems, except it doesn't contain Enterprise by default, you can create it manually though.
Great thanks. I have no need for Enterprise. Will the MCT ISO give me the option to install "Windows 10 Pro" ? No, I don't plan to offline updating, I just want a clean install on my wife's laptop and let the updates be done automatically. If the MCT ISO allows it then I'll go for that, provided I can install Windows 10 Pro. If not, I'll go for the links given in this thread.
If you selected to create the USB by the MCT or when you got a bootable USB in any other way, you can simply copy/paste the ei.cfg to the "USB:\Sources" folder. NTFS is only bootable for Legacy Bios (MBR) systems, FAT32 can boot on both, Legacy BIOS and UEFI systems. How you do it is up to you, for me a simple FAT32 formatted USB with the ISO extracted to its root is enough.
Pid.txt contains a key for a specific SKU, the ei.cfg can also be sku specific but then it would only select that SKU, my generic one enables you to select from all available SKUs. Best to not combine them.