Oh. Then you have to wait if anyone would share the script, because it is "different" to previous builds.
@xinso actually remember @heldigard ???? the broom boy --- he posted his new version, than some hours later deleted his post, only downloads and screenshots --- my memories..............................................................................................................................................................................................................................................[infinity-symbol-here]!!!!!!! You sometimes remind me at him .... your s1ave77 .
Note, that 26120.1330 is a different branch (ge_release_svc_betaflt_upr) and you may have problems with installing LCUs on ge_release image. If you want it to be 26120, first add 10.0.26120.961 (last of ge_release Beta updates), later install LCU of 10.0.26100.1297 (ge_release) and you would have 10.0.26120.1297 I won't recommend installing 26120 unless you know what you are doing
A1: Extract two packages from 26100.1.240331-1435.ge_release_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso. A2. No. A3: 26100.1.240331-1435.ge_release_amd64fre_CLIENT_LOF_PACKAGES_OEM.iso PS: This is 26100.1, NOT 22621.1. The 22621.1 is the author's own usage for EnterpriseG Multi-Build Options. The script will modify it. You don't touch it. unless you know how to. Be a good user, Don't be a trouble-maker heading into dead end and complain.
Just to clarify.. I use a translator (google translate) some things may be to you (demanding, disruptive, etc) when in reality I am not looking to do any of the above. Don't blame me for it, I'm just learning, having doubts is normal. I know the forum rules, 1.2 of "1 - Communication" talks about this. Always trying to be nice. It's a shame that the translator always messes up the conversations.
maybe these can help. Code: uupdump.net/findfiles.php?id=30da46b4-2ff2-4682-a9ae-23b66dd98713&q=FodMetadata Code: uupdump.net/findfiles.php?id=30da46b4-2ff2-4682-a9ae-23b66dd98713&q=ServerCoreFonts Installed ServerCoreFonts: [Windows Server 2025 SERVERSTANDARD] Code: Microsoft-OneCore-Fonts-ServerCoreFonts-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.cat Microsoft-OneCore-Fonts-ServerCoreFonts-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.mum Microsoft-OneCore-Fonts-ServerCoreFonts-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat Microsoft-OneCore-Fonts-ServerCoreFonts-Package~31bf3856ad364e35~amd64~~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-BitmapFonts-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-BitmapFonts-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-BitmapFonts-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-BitmapFonts-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-MinConsoleFonts-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-MinConsoleFonts-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-MinConsoleFonts-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-MinConsoleFonts-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-Support-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-Support-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-Support-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-Support-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-TrueType-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-TrueType-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-TrueType-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-TrueType-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-UAPFonts-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-UAPFonts-FOD-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1.mum Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-UAPFonts-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat Microsoft-Windows-ServerCoreFonts-NonCritical-Fonts-UAPFonts-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1.mum
Q: Server Desktop Experience "Windows Defender". Which package? Windows-Defender-Server-Core-Package~31bf3856ad364e35~amd64~~10.0.26100.1 Windows-Defender. or Windows-Defender-Server-Service-Package~31bf3856ad364e35~amd64~~10.0.26100.1 Windows-Defender-Default-Definitions. (A Child-Package of Windows-Defender.)
If you want to update 26100.1 EnterpriseGN, you have to make its update cat and mum, because CU does not support it. You can use Wuyouzi067's MSU_to_esd_and_Modded_CU tool. Update is one thing, for dism to show correct EditionID is another thing. It needs "trouble-shooting" with error log.
xinso, - do you know about G - other vendor antivirus solutions, which are installed manually (I mean only Windows 11 compatible) - might they appear in Security center? It is empty on install - that is fine. But nothing appears after I install other solutions. Expected?