stagesxs works with 22000 with secure boot disabled my sl7 intel runs 22000 - unfortunately 22000 reached end of life edit:secure boot doesn't matter
will this https://forums.mydigitallife.net/th...struction-project.80939/page-362#post-1728847 be helpful with 22621 construction? (unstaged and sxsstage) and newer version of sxsstage https://forums.mydigitallife.net/th...struction-project.80939/page-366#post-1729131 all by gailium119
with explodesxs no problem, but i'm curious about another way (xinso said many times: when you want to learn construction, that's what stagesxs is for not explodesxs) interesting that in old thread xinso made construction many times by: mounting unstaged.wim then i guess apply-unattend (install in .xml) adding languagepack edit: for example i installed 19100.1051 unstaged iso in hyper-v install.wim has 3 folders: packages (with cat files, mums and manifests), users (with ntuser.dat) and windows (with amd64_installed in servicing, registry files in system32/config, dll files in dism, dll files in downlevel, wcmtypes.xsd in smi/schema, shcema.dat in smi/store/machine, ssshim.dll in system32, wdscore.dll in system32 and servicingstack files in winsxs)
Thanks. After several thinks, I tested preparing the source in two ways. One by hand, one by script. [by hand] About 10 Minutes. [by script] About 3 Seconds.
zhanglin uses two Sessions on WinRE Reconstruction. Registry has residuals usually. Q: Could it work as expected?
Converted 22621.1.ni_release.220506-1250_25SKUs.iso\sources\install.wim\6\Windows\System32\Recovery\Winre.wim to WinPE.wim [by a script] Reconstructed WinPE.wim to Windows 11 22621.1 with scratch space set at 256mb following winosr25 method, installed and seems to work as expected.
This one is made from boot.wim to WinPE.wim [by a script] from 22621.1.ni_release.220506-1250_25SKUs.iso Then reconstructed to Windows 11 22621.1 with scratch space set at 256mb following winosr25 method, [Credit] winosr25
and success Code: ***************************************************** construct 19100.1051 windows 10 professional amd64 en-us ***************************************************** ************************************** mount unstaged image ************************************** Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Mounting image [==========================100.0%==========================] The operation completed successfully. *********************************** construct professional *********************************** Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.19100.1051 [==========================100.0%==========================] The operation completed successfully. ************************************** add en-us client language ************************************** Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.19100.1051 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.19100.1051 [==========================100.0%==========================] The operation completed successfully.
Code: C:\windows\system32>dism /english /logpath:z:\1.log /image:K: /apply-unattend:z:\winsxs\1.xml Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 [==========================100.0%==========================] The operation completed successfully. C:\windows\system32>dism /english /logpath:z:\1.log /image:K: /add-package:z:\Microsoft-Windows-Client-LanguagePack-Package_en-us-amd64-en-us.esd Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1 [==========================100.0%==========================] The operation completed successfully. C:\windows\system32>dism /english /logpath:z:\1.log /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Current edition is: Current Edition : EnterpriseS The operation completed successfully. C:\windows\system32>
i'll try in a while enterpriseeval, which officially is supported (unlike 23h2 professional), won't force buggy 24/25h2 upgrade (unlike 23h2 professional), will automatically activate (unlike enterpriseg) and has not language restriction (unlike enterpriseg)
weird fact: i have battery limit option enabled on my sl7 intel. on 22000 battery is charging to 50%, on different builds (17763, 19041, 22621, 26100, 28000) to 49%. depends on build or secure boot (on 22000 secure boot is disabled)? edit: depends on build - 49% on 26100 with secure boot disabled for example
Weird? Me too in making base image. Same script on Same 19044 System: As of 22000.1: Failure From 22621.1 forward: Success
As of 22000.1, you use "Neutral" WinRE.wim. From 22621.1 forward, you use "Official" WinRE.wim [17763.1] Code: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.17763.1 [==========================100.0%==========================] The operation completed successfully. [19041.1] Code: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 [==========================100.0%==========================] The operation completed successfully. [20348.1] Code: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.20348.1 [==========================100.0%==========================] The operation completed successfully. [22000.1] Code: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. [28000.4] Code: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.28000.4 Applying package servicing unattend [==========================100.0%==========================] The operation completed successfully.