@Paul Mercer 1. It would be integrated even if already exist 2. Yes, and it's best to also add latest W10UI.cmd script LCU is enough, if the source ISO already contain other updates SafeOS can be multilingual (e.g. for 19041), in that case add it too 3. UUPdump changes are not pleasant indeed when you get two or more cab files, always download the biggest one You are welcome
@Paul Mercer Probably because N editions are officially available for certain languages N edition is a bug, not a feature it should be avoided
@abbodi1406 I've tried ru-RU language pack integration into fully updated en-US 19044.1387 build and I can't find any big problems with Enterprise N ru-RU edition. Only People app was in English and it can't download ru-RU language through Microsoft Store, other apps downloaded corresponded languages without an issue. It would be very helpful if you could investigate (on your spare time of course) what's wrong with localized N editions on 22000 build. I understand that Windows 11 is new, and it could be Microsoft's fault afterall, but I hope workaround could be possible. It's just really weird, and the most funny part is that I see a lot of homebrew Windows 11 ISOs online with a ton of languages/editions combined with the same broken network adapter on ru-RU N editions.
@abbodi1406 Theoretically I could try to integrate all Ethernet and Wifi FOD cabs into N index and it should work, right? If that's it, I hope W10MUI can be updated for Ethernet/WiFi FOD integration support for 22000+ builds I'll try it tommorow, thank you
Trying to fix something that is "intentionally" broken. Not using N editions would be the better choice. The presence of the particular components doesn't make Windows run "infinitely slower" or something of the sort.
Yeah I got it, N editions are the same garbage as new SE edition, but I'm just want to fix broken network adapter purely out of curiosity @abbodi1406 I took a look at the W10MUI.cmd script and made some changes No idea if it's correct or not, I was trying to not break things first, but I don't have time to test it, but I will later today Spoiler new line 286 Code: set _ODinternet64= new lines 295 and 296 Code: set _ODethernet64= set _ODwifi64= new lines 318 and 319 Code: findstr /i /m Microsoft-Windows-Ethernet-Client update.mum %_Nul3% && (set _ODinternet64=1&call set _ODethernet64=!_ODethernet64! /PackagePath:OBFILE%%j\update.mum) findstr /i /m Microsoft-Windows-Wifi-Client update.mum %_Nul3% && (set _ODinternet64=1&call set _ODwifi64=!_ODwifi64! /PackagePath:OBFILE%%j\update.mum) new line 548 Code: if defined _ODinternet64 !_dism2!:"!TMPDISM!" /Image:"%INSTALLMOUNTDIR%" /LogPath:"%_dLog%\MUIinstallFOD64.log" /Add-Package !_ODethernet64! !_ODwifi64!
@Paul Mercer Thanks for verifying and testing 1. apparently, MSPaint-FoD packs are for EnterpriseS and Server editions (none available for Windows 11 yet) i will update the instructions 2. FoD language packs are already included within the UUP edition file (professional_en-us_84f32e55.esd) e.g. Microsoft-Windows-Notepad-System-FoD-Package~31bf3856ad364e35~amd64~en-us~_0300512e.cab Microsoft-Windows-Notepad-System-FoD-Package~31bf3856ad364e35~wow64~en-us~_91e0f6fd.cab when adding new language, those packs are needed to be added separately e.g. Microsoft-Windows-Notepad-System-FoD-Package~31bf3856ad364e35~amd64~ru-ru~_1b25c0cf.cab Microsoft-Windows-Notepad-System-FoD-Package~31bf3856ad364e35~wow64~ru-ru~_727e0321.cab
W10MUI 19u - Support to add Network FoD packs for Windows 11 (build 21382 or later) - Updated 22000-OnDemand.txt
@abbodi1406 Sorry for so many questions, but how I can check which FoD language packs are already included in ESD? Thank you
Any FoD pack appear in the UUP list, mean the associated FoD lang pack is included in the ESD they probably didn't hydrate it because it's usually too small to check it with hand with 7-zip, open the UUP edition file > index 3 \Windows\servicing\Packages any package that have none zero size means it's included within
I want to clarify one more thing, I promise that's the last one How to enable .net35 correctly? There's three places I can enable it (UUP->ISO converter, W10MUI.cmd and W10UI.ini) I have refreshed 22000.348 ISO from UUPdump with .net35 enabled. All updates placed into .\Updates folder. ReadMe says I can enable NET35 in W10MUI.cmd, but netfx3-ondemand-package will be removed from ISO. It confuses me because UUP->ISO converter don't remove it, so why W10MUI removes it? Wil it be removed at the last stage after updates integration with W10UI and I should enable it in W10MUI.cmd and W10UI.ini? Or it will be removed after language packs integration but before updates integration with W10UI? For now I set "NetFx3=1" in UUP->ISO converter, "NET35=0" in W10MUI.cmd and "Net35=1" in W10UI.ini. In that scenario W10UI enables .net35 at the last stage, but netfx3-ondemand-package still present in sxs folder If netfx3-ondemand-package removes before W10UI then I don't knoiw how W10UI can reenable .net35 without requred FOD Maybe I'm over complicated it and I just need to enable it in W10MUI.cmd and don't touch W10UI.ini at all (Net35 is 1 by default there)
W10MUI remove netfx3 cab at the last phase, after Rebuild install.wim the reason to remove it is just to save space, since it's already enabled
@abbodi1406 Are the Windows 11 (22000-OnDemand) "microsoft-windows-mspaint-fod-package-amd64-XX-XX" cabs not needed anymore? They not in the list anymore.