don't have luck today, got BSOD while the script is running. at least didn't fail to 1 thread instead 16 Second try .. Succeeded
I downloaded the Build Architecture Date added Update ID Feature update to Windows 10, version 21H2 (19044.1862) amd64 (IOT) iso All was perfect , but when it came to activate this version Tried the HWID ,, came up with error Then Tried KMs all was ok.. So,, why does the UUP version 19044.1862 (downloaded IOT) refuse to activate with HWID, am i missing something ?? about windows shows Edition Windows 10 Enterprise Version 21H2 Installed on 14/07/2022 OS build 19044.1826 Experience Windows Feature Experience Pack 120.2212.4180.0 where is the IOT version ?
I have a question, if I may. I have been playing with the options on UUPDUMP, and have observed the following. When creating a windows 10 ISO for 19044.18062, if I choose Pro, Edu, and Ent, select solid compression (install.esd) and “component cleanup”, the resulting ISO file comes in at around 4 gigs. Turning off “component cleanup” grows the resulting ISO file by about 0.5 gigs (now 4.5 gigs). Further turning off “solid compression” grows the ISO to about 6.9 gigs. All of which is interesting, but not that important. My question has to do with “component cleanup”. I saw over in the Windows 11 forum here at MDL, a discussion about “cleaning” which led to problems with future system updates. Is that the same thing as “component cleanup” in UUPDUMP? Are we better off / safer if we do not choose “component cleanup” when building an ISO?
I always use the full resetbase, combined with the cleanup, option (available in the convertconfig.ini file) and it never resulted in errors after installing it. Cleanup - compresses superseded components (can give errors with certain insider Preview RP or Beta channel updates afterwards) Cleanup + resetbase - removes the superseded components Solid compression - compresses the install.wim to install.esd which decreases the size with approx. 30-33%
Didn't Cleanup and ResetBase broke the Reset this PC feature? I always use Cleanup and ResetBase because I don't use Reset this PC. The question is, how do we come as close as possible to official MS ISO, which options to use and ignore?
Only for 1809 and that currently is LTSC only, not available as full project by uup dump. By using official MSFT ISOs.
Sarcasam aside, I've created 19044.1862.220706-1736.21H2_RELEASE_SVC_PROD2_CLIENTPRO_OEMRET_X64FRE_EN-US with ResetBase = 1 and Cleanup = 1. In what ways does it differ from official ISO? Is it worth waiting for it?
Not existing. 19042 and up isos are sysprepped and recaptured ISOs from what i remember. You can create every ISO you want, with whatever options you desire, why would it have to be as closest as possible to what MSFT creates? Personally i never use UUP dump for uptodate ISO creation, i always create the .1 ISO at uup dump (and with 22621 we got the .1 MSFT ISO but not for all 38 languages) and next use W10UI with the latest updates to update it.
UUP image is for online update of a running system which does not need boot.wim. As defined in [1].xml of an edition esd, e.g. professional_en-us.esd, we can see that it is composed of three images. Index 1: Windows Setup Media (ISO holder) Index 2: Microsoft Windows Recovery Environment (x64) (Winre.wim) Index 3: Windows 10 Pro (install.wim without WinRe.wim) So, UUP ISO's being lacking in official "boot.wim" is the difference from an official ISO. To make it as official as possible is to replace UUP boot.wim with that of an official ISO. PS: [1].xml Code: <?xml version="1.0"?> -<WIM> <TOTALBYTES>517055041</TOTALBYTES> -<IMAGE INDEX="1"> <DIRCOUNT>84</DIRCOUNT> <FILECOUNT>897</FILECOUNT> <TOTALBYTES>277795732</TOTALBYTES> <HARDLINKBYTES>0</HARDLINKBYTES> -<CREATIONTIME> <HIGHPART>0x01D5ACF0</HIGHPART> <LOWPART>0x8408DDE7</LOWPART> </CREATIONTIME> -<LASTMODIFICATIONTIME> <HIGHPART>0x01D5ACF0</HIGHPART> <LOWPART>0x8408DDE7</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <NAME>Windows Setup Media</NAME> <DESCRIPTION>Windows Setup Media</DESCRIPTION> </IMAGE> -<IMAGE INDEX="2"> <DIRCOUNT>3548</DIRCOUNT> <FILECOUNT>16986</FILECOUNT> <TOTALBYTES>2203347082</TOTALBYTES> <HARDLINKBYTES>972687337</HARDLINKBYTES> -<CREATIONTIME> <HIGHPART>0x01D5ACCD</HIGHPART> <LOWPART>0x97A856C3</LOWPART> </CREATIONTIME> -<LASTMODIFICATIONTIME> <HIGHPART>0x01D5ACF0</HIGHPART> <LOWPART>0xF34A4D93</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> -<WINDOWS> <ARCH>9</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>WindowsPE</EDITIONID> <INSTALLATIONTYPE>WindowsPE</INSTALLATIONTYPE> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE/> -<LANGUAGES> <LANGUAGE>en-US</LANGUAGE> <DEFAULT>en-US</DEFAULT> </LANGUAGES> -<VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>19041</BUILD> <SPBUILD>1</SPBUILD> <SPLEVEL>0</SPLEVEL> <BRANCH>vb_release</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Microsoft Windows Recovery Environment (x64)</NAME> <DESCRIPTION>Microsoft Windows Recovery Environment (x64)</DESCRIPTION> </IMAGE> -<IMAGE INDEX="3"> <DIRCOUNT>18284</DIRCOUNT> <FILECOUNT>85447</FILECOUNT> <TOTALBYTES>14085762355</TOTALBYTES> <HARDLINKBYTES>5921320712</HARDLINKBYTES> -<CREATIONTIME> <HIGHPART>0x01D5ACF0</HIGHPART> <LOWPART>0x608D2670</LOWPART> </CREATIONTIME> -<LASTMODIFICATIONTIME> <HIGHPART>0x01D5ACF1</HIGHPART> <LOWPART>0x4485501C</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> -<WINDOWS> <ARCH>9</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>Professional</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> -<SERVICINGDATA> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.19041.1;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> </SERVICINGDATA> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> -<LANGUAGES> <LANGUAGE>en-US</LANGUAGE> <DEFAULT>en-US</DEFAULT> </LANGUAGES> -<VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>19041</BUILD> <SPBUILD>1</SPBUILD> <SPLEVEL>0</SPLEVEL> <BRANCH>vb_release</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 10 Pro</NAME> <DESCRIPTION>Windows 10 Pro</DESCRIPTION> </IMAGE> </WIM>
So if I might summarize here, there are no known problems with using solid compression (install.esd instead of install.wim). But to be as safe as possible, do not "cleanup" and do not "resetbase". And from an earlier conversation, "feature update" (win10) or "upgrade to" (win11) are preferred over "cumulative update". Now let me put this in my notes, I'm old and forget things.
Resetbase option will only work when cleanup is selected and install.esd is just the recovery compression of install.wim. Resetbase seems safe to use except on 1809 builds.
How to join 2 wim's business & consumer into 1 install.wim I have 2 iso images pl-pl_windows_11_consumer_editions_version_21h2_updated_july_2022_x64_dvd_561d7c2d pl-pl_windows_11_business_editions_version_21h2_updated_july_2022_x64_dvd_fd4f09ff and I'd like to put them both into one, preferably esd. I have fast Internet fibre 1Gbp/s but slow computer. Would it be faster to build the image from UUP Dump? Thanks a lot in advance!!