Please read back on the forum, al lot already has been discussed, the appx stuff still doesn't seem to be used.
how do they get integrated into an ISO, or are they not? like if i take a MS iso, mount it and dism the MSU... i guess i should just try it if they are integrated, does it differentiate during installation to add them to the system if it sees an NPU, or does it add them regardless? again i should test this
We have some traces of this "AI" microsoftwindows.client.aix or microsoftwindows.client.coreai for example
They are not added, some already tested like @Enthousiast it could be ment for online installation only (to properly detect NPU machine) you can try to fool the msu by adding this registry to the mounted image registry (untested) Code: set "rk=HKEY_LOCAL_MACHINE\Offline_Software\Microsoft\Windows NT\CurrentVersion\UnattendSettings\WaaS\Device\Detect\Hardware\NPU" reg add "%rk%" /v "A6EEA85C-3D59-4FF8-A673-F88D85107D0C" /d "1"
is possible to keep W10ui_temp folder , delete MSIX then apply to another system ? because 4 GB msu over Wi-Fi 50 Mbits/s is quite slow , I don't understand Microsoft
Using 7-zip, extract all non-msix files from msu file to a new folder use PSFX MSU Maker to create new msu
Code: mkdir new_folder dism.exe /Apply-Image /ImageFile:Windows11.0-KB5058411-x64.msu /Index:1 /ApplyDir:new_folder /NoAcl:all