See for help https://forums.mydigitallife.net/th...struction-project.80939/page-705#post-1820761 https://forums.mydigitallife.net/th...struction-project.80939/page-705#post-1820770
extract wim and run psfextractor: Code: dism /apply-image /imagefile:%wim% /index:1 /applydir:%path% psfextractor -v2 %path%\express.psf.cix.xml %path%
For components in CU, as it can be determined that they have been updated, their updated content must be determined through other builds.
Reconstruction (especially in Server to Client/Client to Server) may cause component miss, which is a known issue.
Now the confusion is that the Apply-Unattend method shows success, but is actually incomplete. The content produced by the two methods is consistent (No Language, No FOD) install.wim, by installing Windows11.0-KB5036910-x64-830.msu, there is a difference in the results.
Unstaged core.wim ，Installation Feature Packs, Language Packs, Seth-Alintel Code: C:\Windows\System32>dism /image:D:\1 /add-package:D:\2\Windows11.0-KB5036910-x64-830.msu 部署映像服务和管理工具 版本: 10.0.26100.1 映像版本: 10.0.25398.1 Processing 1 of 1 - [==========================100.0%==========================] [==========================100.0%==========================] 操作成功完成。 C:\Windows\System32>Dism /image:D:\1 /get-CurrentEdition 部署映像服务和管理工具 版本: 10.0.26100.1 映像版本: 10.0.25398.830 以一种访问权限不允许的方式做了一个访问套接字的尝试。 Current Edition : Enterprise 操作成功完成。 There are so many mistakes, what do you mean? Code: 2024-04-30 21:50:52, Info CheckApplicability: scenario=[desktopUpgrade], minVersion=[*], maxVersion=[*] 2024-04-30 21:50:52, Error CheckScenario: Execution scenario [0x16] not supported. 2024-04-30 21:50:52, Error CMitigationManager::CheckScenario(869): Result = 0x80070032 2024-04-30 21:50:52, Error CMitigationManager::CheckApplicability(636): Result = 0x80070032 2024-04-30 21:50:52, Error CMitigationManager::ProcessMitigation(1748): Result = 0x80070032 2024-04-30 21:50:52, Info Execute: [Setup360] Result=[0x80070032], Applicable=[yes] 2024-04-30 21:50:52, Info Execute: Processing mitigation [1]... 2024-04-30 21:50:52, Info ProcessMitigation: Checking applicability for [ArbiterEditionId]... 2024-04-30 21:50:52, Info CheckApplicability: scenario=[unknown], minVersion=[10.0.15063.*], maxVersion=[10.0.15063.*] 2024-04-30 21:50:52, Error CheckScenario: Execution scenario [0x16] not supported. 2024-04-30 21:50:52, Error CMitigationManager::CheckScenario(869): Result = 0x80070032 2024-04-30 21:50:52, Error CMitigationManager::CheckApplicability(636): Result = 0x80070032 2024-04-30 21:50:52, Error CMitigationManager::ProcessMitigation(1748): Result = 0x80070032 2024-04-30 21:50:52, Info Execute: [ArbiterEditionId] Result=[0x80070032], Applicable=[yes] 2024-04-30 21:50:52, Info Execute: Processing mitigation [2]... 2024-04-30 21:50:52, Info ProcessMitigation: Checking applicability for [CryptcatsvcRebuild]... 2024-04-30 21:50:52, Info CheckApplicability: scenario=[desktopServicing], minVersion=[10.0.16299.*], maxVersion=[10.0.19603.*] 2024-04-30 21:50:52, Error CheckScenario: Execution scenario [0x16] not supported. 2024-04-30 21:50:52, Error CMitigationManager::CheckScenario(869): Result = 0x80070032 2024-04-30 21:50:52, Error CMitigationManager::CheckApplicability(636): Result = 0x80070032 2024-04-30 21:50:52, Error CMitigationManager::ProcessMitigation(1748): Result = 0x80070032 2024-04-30 21:50:52, Info Execute: [CryptcatsvcRebuild] Result=[0x80070032], Applicable=[yes] 2024-04-30 21:50:52, Info GetPackageCategoriesFromString: Found [2] categories. 2024-04-30 21:50:52, Info GetPackageCategoriesFromString: Adding category [LCU]... 2024-04-30 21:50:52, Info GetPackageCategoriesFromString: Adding category [GDR]... 2024-04-30 21:50:52, Info GetOneSettings: Verifying signature of [D:\1\Windows\Temp\D03CC438-0936-4467-A763-55A81CCFB5D4\metadata\UAOneSettings.dll]... 2024-04-30 21:50:52, Info GetOneSettings: Loading [D:\1\Windows\Temp\D03CC438-0936-4467-A763-55A81CCFB5D4\metadata\UAOneSettings.dll]... 2024-04-30 21:50:52, Info GetOneSettings: OneSettings module [D:\1\Windows\Temp\D03CC438-0936-4467-A763-55A81CCFB5D4\metadata\UAOneSettings.dll] verified. 2024-04-30 21:50:52, Info GetOneSettings: Creating OneSettings helper... 2024-04-30 21:50:52, Info GetOneSettings: Initializing settings... 2024-04-30 21:50:52, Info OneSettings: Initializing settings... 2024-04-30 21:50:52, Info OneSettings: Blocked by policy settings. 2024-04-30 21:50:52, Error CMoUpdateOneSettingsHelper::GetSettingsParameters(229): Result = 0x8000000A 2024-04-30 21:50:52, Info GetOneSettings: Initialized -> [No] 2024-04-30 21:50:52, Info ReportEventOneSettingsEnd: result = [0x0] 2024-04-30 21:50:52, Info ReportEventOneSettingsEnd: Count = [0] 2024-04-30 21:50:52, Info ReportEventOneSettingsEnd: Parameters = [] 2024-04-30 21:50:52, Info ReportEventOneSettingsEnd: Values = [] 2024-04-30 21:50:52, Info No callback factory provided for IDeploymentInformationFactory, will not not use deployment information this session 2024-04-30 21:50:52, Error CDeploymentSession::IsRangeRequestSupported(4105): Result = 0x80040154 2024-04-30 21:50:52, Error IsRangeRequestSupported failed with: [80040154 [Error,Facility=FACILITY_ITF,Code=340 (0x0154)]]. Setting RangeRequestSupported to FALSE 2024-04-30 21:50:52, Info Not using servicing for upgrade.
I don't use msu. No idea. This is my reconstructed 25398.1 Enterprise. No such errors. Code: C:\WINDOWS\system32>dism /english /image:K: /add-package:z:\windows11.0-kb5036910-x64.msu /logpath:z:\1.log Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - [==========================100.0%==========================] [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /english /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.830 Current edition is: Current Edition : Enterprise The operation completed successfully. C:\WINDOWS\system32>
I don't know exactly how it happened, but after installing a 23H2 22631.3155 Enterprise G I built onto my laptop it now has an OEM firmware key for "Windows 10 RTM CoreCountrySpecific OEM: DM." I have looked up the key in search engines and it's definitely a unique key. Any idea how I managed to do that? My best guesses are putting [KEY] as the key in autounattend and also blocking autoactivation, or poking around in product policy trying to get defender working. The entire time using the install, well before any changes, the activate part of settings would remain a gray screen, so I doubt poked product policy too hard. I did leave SPP disabled long enough for it to deactivate but remedied that immediately.
25398 EnterpriseG(N) OOBE Getting ready, 830 is taking longer than previous CUs. And the tzsync.exe is frozen for all builds of Licenses at first logon. So, keep looking forward to next official CMGE.
I did not think about looking in the 25398.1_ServerDatacenterCor_to_Client_amd64.7z. I was just researching for what files I might need. Sorry about that..
I did that, but can you explain to me the method xinso explained in detail? https://forums.mydigitallife.net/th...struction-project.80939/page-775#post-1832497
Reconstruct Unstaged 25398.1 - Windows 11 Enterprise multi-session (Retail with Edge with Store with NetFx3) amd64 en-US