@xinso I am enjoy to show my success after some research : Code: C:\Windows\system32>dism /image:c:\mount /get-currentedition Outil Gestion et maintenance des images de déploiement Version : 10.0.19041.844 Version de l’image : 10.0.19044.3086 Édition actuelle : Édition actuelle : EnterpriseS L’opération a réussi. I have replace win32calc files and use a restorehealth
Code: <Session version="8.0" id="6904_36384765" client="DISM Package Manager Provider" options="262144" currentPhase="1" lastSuccessfulState="Complete" pendingFollower="false" retry="false" operationCovered="0" correlationVector="YEG3hp0EGkWfU375.0" Queued="2023/06/17/21:46:37" Started="2023/06/17/21:46:37" Complete="2023/06/17/21:46:38" status="0x0"> <Tasks> <Phase seq="1"> <package id="Microsoft-Windows-Branding-Enterprise-Package~31bf3856ad364e35~amd64~~10.0.25387.1" name="Microsoft-Windows-Branding-Enterprise-Package" targetState="Staged" options="4"/> <package id="Microsoft-Windows-Editions-Professional-Package~31bf3856ad364e35~amd64~~10.0.25387.1" name="Microsoft-Windows-Editions-Professional-Package" targetState="Staged" options="4"/> </Phase> </Tasks> <Actions> <Phase seq="1" rebootRequired="false" Resolved="2023/06/17/21:46:38" Staged="2023/06/17/21:46:38"> <Resolve package="Microsoft-Windows-Branding-Enterprise-Package~31bf3856ad364e35~amd64~~10.0.25387.1" update="Microsoft-Windows-Branding-Enterprise-Deployment"/> <Resolve package="Microsoft-Windows-Editions-Professional-Package~31bf3856ad364e35~amd64~~10.0.25387.1" update="Microsoft-Windows-Editions-Professional-Deployment"/> <Stage package="Microsoft-Windows-Branding-Enterprise-Package~31bf3856ad364e35~amd64~~10.0.25387.1" update="Microsoft-Windows-Branding-Enterprise-Deployment"/> <Stage package="Microsoft-Windows-Editions-Professional-Package~31bf3856ad364e35~amd64~~10.0.25387.1" update="Microsoft-Windows-Editions-Professional-Deployment"/> </Phase> </Actions> </Session> </Sessions>
[the pot calling the kettle black] Black, naturally. What about pot bottom leakage? PS: This is reminder for myself.
Have you noticed that: In <Tasks>, it shows "Capability". In <Actions>, it installs not only "Package" but also "Language pack(s)", if available.
Yes, sir, I feel that it uses /Add-Capability, and by adding a OnDemand, it will install the language pack and the subpackage wow64 at the same time, but I can't do it anyway. e.g Add-Capability/CapabilityName:Media.WindowsMediaPlayer~~~~0.0.12.0, Microsoft-Windows-MediaPlayer-Package-amd64, Language Pack, Microsoft-Windows-MediaPlayer-Package-wow64 are all installed together.
/add-package:Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~10.0.25387.1.mum, display： <package id="Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~10.0.25387.1" name="KB777778" targetState="Installed" options="4"/> Add-Capability/CapabilityName:Media.WindowsMediaPlayer~~~~0.0.12.0 display：<capability id="Media.WindowsMediaPlayer~~~~0.0.12.0" displayName="Windows Media Player Legacy" Now the question is: I use Add-Capability/CapabilityName:Media.WindowsMediaPlayer~~~~0.0.12.0 /Source:2 The source file could not be found. Code: <Session version="8.0" id="792_4848562" client="DISM Package Manager Provider" options="262144" currentPhase="1" lastSuccessfulState="Started" pendingFollower="false" retry="false" onDemandFeatureList="Media.WindowsMediaPlayer~~12.0" operationCovered="1088" correlationVector="wPJ+Ie7MJEir1Zcb.2" Queued="2023/06/18/10:41:49" Started="2023/06/18/10:41:49" Complete="2023/06/18/10:41:49" status="0x800f081f"> <Tasks> <Phase seq="1"> <capability id="Media.WindowsMediaPlayer~~~~0.0.12.0" displayName="Windows Media Player Legacy" description="Play audio and video files on your local machine and on the Internet." targetState="Installed" options="12"/> </Phase> </Tasks> <Actions> <Phase seq="1" rebootRequired="false"> </Phase> </Actions> </Session>
Different to official. OK. x86 does not know amd64, so, amd64 is not able to be constructed on x86 OS platform x86 does not know arm64, yet, arm64 is able to be constructed on x86 OS platform. Q: 1. Why? 2. How to construct amd64 on x86 OS platform?
There's a script link named "tiny11builder-main" somewhere at other thread. It needs a new script for each and every build. e.g. tiny11 creator 22621.525.bat, tiny11 creato 22621.1265.bat, tiny11 creator 25300.bat. Q: Why? A: It specifies "build" of App and Package. e.g. 22621.1265. App: Clipchamp.Clipchamp_2.2.8.0_neutral_~_yxz26nhyzhsrt Package: Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~11.0.22621.1265 Universal script: I want lite Specified script: I want lite build 0 I want lite build 1 I want lite build 2 . . . PS: "This tiny11" is "full system" with most provisioned Apps and some FODs removed, different to "another tiny11" on the web which is "chop-down" running in memory.