There is no such version, I got the w11 iso already in pt-br and made the modifications directly to it
Update Bedi 6.31 Changelog: Code: + Add some lite options. (Exclusive only for image with build number 22000.1 and 22621.1 It's permanently remover because upmod.cmd will keep it like that if you update with that tool. + Change and add update image tools (upmod.cmd) + Some vaccine packages + Update ModLCU.cmd and upmod.cmd + Update Specific Edition for 22000 and 22621, move SecHealthUI to the general uwp apps. + Several fixs to improve script performance - Remove language packages, so it reduce Bedi sizes. But you must have it in each build number folder.
I modifed Bedi EnterpriseG package to allow multilanguage for whom wants to test. Bedi can have its own check not to allow other language then en-us at below code. You can modify code or create en-us EnterpriseG and add another language later. As you wish. For 26100 Code: Findstr /i "\"%_version%\"" update.mum %_Nol% || (Del /f /q update.mum & call :_Warn "Wrong language package version!!") if /i %_targSKU% == EnterpriseG (Findstr /i /c:"capabilityIdentity language=\"en-US\"" update.mum %_Nol% || (Del /f /q update.mum & call :_Warn "Only language package for en-US")) Del /f /q update.mum && Echo ready.
hash error: crypt_e_not_found Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseG-License-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat has wrong signature
Hello @Javac75 an alternative Code: @Echo Off Set "_iw=install.wim" if not exist "%_iw%" (Call :_Warn "There is no %_iw% in the directory") ::# self-elevate passing args and preventing loop by AveYo
Ahh...well that's it. I always felt like something was forgotten, and it turned out to be true. I've wanted to put it there for a long time, but I keep forgetting. Thank you for reminding.
that's not where the problem lies. creating and signing cat files is not difficult - you have to have cdf file and certificate (windows adk installed). problem is reconstructed image with other language than en-us or zh-cn - license files are not correct then
as iamahun wrote: to get hash - PowerShell 7 can do this: [System.Convert]::ToBase64String([System.Convert]::FromHexString((Get-FileHash -LiteralPath "path to file" -algorithm SHA256).Hash)) To create cat file you'll need makecat.exe from Windows ADK - it will require a .cdf file (which can be edited using Notepad): [CatalogHeader] Name=Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseG-License-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat PublicVersion=0x00000001 EncodingType=0x00010001 CatalogVersion=2 HashAlgorithms=SHA256 ResultDir=.\ CATATTR1=0x00010001:OSAttr:2:5.1,2:5.2,2:6.0,2:6.1,2:6.2,2:6.3,2:10.0 [CatalogFiles] <hash>=C:\enterpriseg\Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseG-License-Package~31bf3856ad364e35~amd64~~10.0.26100.1.mum <hash>=C:\enterpriseg\amd64_microsoft-windows-s..nterpriseg-license_31bf3856ad364e35_10.0.26100.1_none_19cc52cfef2ccce8.manifest To generate the .cat file: "C:\Program Files (x86)\Windows Kits\10\tools\bin\i386\makecat.exe" -v "C:\enterpriseg\Microsoft-Windows-Security-SPP-Component-SKU-Enterprise G-License-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cdf" If ANY other file is part of the package that is installed by manifest files, it must be on the hash list above, not just the .mum and .manifest files (for example Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseG-License-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cdf hash list contains about 118 files) And the last part is signing the cat file - you need signtool.exe (it's also part of Windows ADK): "C:\Program Files (x86)\Windows Kits\10\tools\bin\i386\signtool.exe" sign /a /f "path to .pfx file" /fd SHA256 /p "password to .pfx file" "path to .cat file to sign"