Perhaps the reconfigured ISO could be shared, for testing purposes or for daily use? Thanks... #NewThing
When we failed to extract CU, gailium119's tool will fail too. Same error - lots of mum files with no cat files. The difference between two extraction methods is gailium119's method is far easier and quicker. [Fact] But the latest CUs seemingly would not work as aforementioned.
the mum files with missing cat are now verified by update.cat (notice how it's big now) however, legacy cbs servicing seems not aware of this change, or they don't plan to support it only the new mumx v2 container will correctly verify the mum files with update.cat hence, you can't add expanded LCU, you must add the msu file
[28000.3351 ServerRdsh arm64 en-US] Code: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~arm64~~28000.3351.1.28 [==========================100.0%==========================] The operation completed successfully. Code: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.3351 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : ServerRdsh (RETAIL) ============================================================ [Credit] gailium(119)
Sorry, but I don't find xinso's posts helpful, because he never provides files or instructions - he just brags about the result.
reconstruction script (which is easier than construction) is required - for example professional (you can download this sku from uupdump) to enterprises
hey i am trying to construct enterprise g 21h2 via @winosr25 method (ie convert boot.wim - to base.wim and later convert base wim to install wim now i have an error " Deployment Image Servicing and Management tool Version: 10.0.22000.1 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1 [==========================100.0%==========================] An error occurred - Microsoft-Windows-Client-LanguagePack-Package Error: 0x800700a1 Error: 161 The specified path is invalid. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Deployment Image Servicing and Management tool Version: 10.0.22000.1 Image Version: 10.0.22000.1 Error: 87 UI language is not installed. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log" my xml files are in attachment... language pack is in .esd format
26300.9807 == Customization Terminator? There are 26100.9807 packages, but no 26100.9807 Edition. And. There is 26100.1742 CU, but no 26100.9807 CU. It is replaced by \Windows\servicing\MumX\Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.9807.1.32.mumx
[Test 28000.3351 CoreSingleLanguage arm64 sr-LATN-RS] Code: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~arm64~~28000.3351.1.28 [==========================100.0%==========================] The operation completed successfully. Code: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.3351 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : CoreSingleLanguage (RETAIL) ============================================================ [Credit] gailium119
LTSC with W10UI also cannot be updated. Code: Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.9807.1.32 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x80070002 Error: 2 The system cannot find the file specified.