Stop messing around and look at the MSUs properly. Don't trust AI; I'm using my own brain. The difference lies in the wrapper language, which isn't the same (pro enterg enters). The wrapper language will mess things up for you. Stop adding files that don't exist. I create my versions without patches, using my own brain, my base 25398 IoT server. Thanks, ACE. I don't recognize the forum I used to know. Now that the problem is solved (AI or servo)? For the AI, I have my script that creates boot.wim as a winpe.wim file, which goes into build mode on all versions. Without my script, the AI in its cu blabla!
Try make update with sign custom mum file Code: CU_BuildNumber = KB5077179 UARC = amd64 ARCH = amd64 LVER = 10.0.28000.1575 SVER = 28000.1575 [PATCH] update.mum: scanned 1, updated 1 [PATCH] wrapper-*~31bf3856ad364e35~amd64~~*.mum: scanned 9, updated 1 [CAT][SSU] processing 2 modified MUM file(s) [CAT][SSU] update.mum [CAT][SSU] Wrapper-042B0F47D4945DABC444491D648035697CDF468AD6FFA53F2775CD1C70BEB569~31bf3856ad364e35~amd64~~10.0.28000.1575.mum [PATCH] update.mum: scanned 1, updated 1 Modded EnterpriseS Package ....
[Test 28000.2333 Windows 11 Enterprise (OEM_COA_NSLP with Edge with Store in Official style) en-GB by WinPE] [arm64] Code: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Convert Winpe to Enterprise :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.1 Removing package Microsoft-Windows-WinPE-Package~31bf3856ad364e35~arm64~~10.0.28000.1 [==========================100.0%==========================] The operation completed successfully. Code: ------------------------------------------------------------ Add en-GB Client Language ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~arm64~en-GB~10.0.28000.1 [==========================100.0%==========================] The operation completed successfully. Code: ------------------------------------------------------------ Add Baseline Cumulative Update to Enterprise image ------------------------------------------------------------ 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.2333.1.12 [==========================100.0%==========================] The operation completed successfully. Code: ------------------------------------------------------------ Set Enterprise Key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.2333 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : Enterprise (OEM_COA_NSLP) ============================================================ [amd64] Code: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Convert Winpe to Enterprise :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.1 Removing package Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.28000.1 [==========================100.0%==========================] The operation completed successfully. Code: ------------------------------------------------------------ Add en-GB Client Language ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-GB~10.0.28000.1 [==========================100.0%==========================] The operation completed successfully. Code: ------------------------------------------------------------ Add Baseline Cumulative Update to Enterprise image ------------------------------------------------------------ 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~amd64~~28000.2333.1.12 [==========================100.0%==========================] The operation completed successfully. Code: ------------------------------------------------------------ Set Enterprise Key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.2333 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : Enterprise (OEM_COA_NSLP) ============================================================ [Credits] winosr25
This message also concerns TesterMachineOS. Update build (rebuild), this will avoid the same questions and answers. The package is complete (except for boot.wim and sxs). New OS, new method requested.
[Fact] WinVOS cannot be constructed and reconstructed. Q: Why? A: 26100.1 for example. 1. Any Container OS is built by this package: InternalBuildPackage-ServicingStack-OneCore-InstallOptions-Package~31bf3856ad364e35~amd64~~10.0.26100.1 2. The package is "removed" upon completion of Construction. This is why it is impossible to be constructed\reconstructed by Users. [InternalBuildPackage] Internal == Inside Microsoft Build == Construct Package == Package
I think Xinso didn't understand the script We detail the packages in the XML file, removing the problematic package and, if necessary, patching it with a .reg file. And in version 26100.1(VNC) 22000.1(ContainerOsplus) there are no restrictions on packages; you can modify them as you wish, so it's a non-issue.
Thank you for precious instruction. But I am used to official Sessions.xml. Yesterday, I used your WinPE way, but I did not use registry tweak. And it worked fine. Thanks again. Oh. I am used to "Full" structure and you are good at "Core" structure. They are beyond comparison. Right? As for xml, I use it for Reconstruction only. Why? My script is common to amd64 and arm64.
InternalBuildPackage-ServicingStack-OneCore-InstallOptions-Package~31bf3856ad364e35~amd64~~10.0.10586.0
Test 10240.21161 CoreARM en-US (With resetbase) Spoiler Question: How does xinso remove legacy edge without custom update package?
I apologize for my ignorance; I usually have limited time due to work. Could you familiarize me with the topic you're discussing? I'm a bit out of the loop right now. If there's a problem within the thread, you can contact me privately. Aside from what I mentioned... I received your EnterpriseG 19041.1 script privately; the tutorial is accurate, and I'm currently testing it. If I get your permission, it will also be added to the thread's index.