i've noticed that 4096 ram value is in amd64 and x86 defaultppd-csvlk also (and csvlk is in spp\tokens\skus folder). i'll try to change that too.
i activated gn this way https://forums.mydigitallife.net/th...dows-pre-activation-method-all-versions.88772. now ram is not 4096 finally
Q: Could we use WinPE\WinRE as Reconstruction base? A: Code: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Create EnterpriseSN image :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.26100.1 Applying package servicing unattend [==========================100.0%==========================] Error: 0x80188309 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
It's likely, but in my case using the same files created by bedi and also the lcu modified by ModLCU I managed to integrate the ssu and lcu without problems.. I used an old script that I published here and adapted it using bedi's sxs to then start the build. Code: Creating Windows 11 IoTEnterpriseS x64 es-ES Mounting image Deployment Image Servicing and Management tool Version: 10.0.19041.746 Mounting image [==========================100.0%==========================] The operation completed successfully. Current Edition Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Current edition is: Current Edition : Professional The operation completed successfully. Creating IoTEnterpriseS Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Integrating Language Pack Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~es-ES~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Settings Channel Edition Current Edition : EnterpriseS (Retail) Set edition IoTEnterpriseS Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Starting to install product key... Finished installing product key. The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Starting to update components... Starting to install product key... Finished installing product key. Starting to apply edition-specific settings... Finished applying edition-specific settings. The operation completed successfully. Removing appx Adding PhotoViewer Cleaning up image Restore Health Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 [===========================84.9%================= ] [===========================87.3%================== ] [===========================89.9%==================== ] [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. Reset Base Image. Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Updating image Integrating SSU - "updates\SSU-22000.3196-x64.esd" Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3196~31bf3856ad364e35~amd64~~22000.3196.1.0 [==========================100.0%==========================] The operation completed successfully. Integrating LCU - "updates\Windows10.0-KB5043067-x64.esd" Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22000.3197.1.7 [==========================100.0%==========================] The operation completed successfully. Unmounting image Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image File : C:\22000.1_EnterpriseS_x64_with_modLCU\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. "install.wim" original size: 5819287 KiB Using LZX compression with 2 threads Archiving file data: 11 GiB of 11 GiB (100%) done "install.wim" optimized size: 5346721 KiB Space saved: 472566 KiB Setting the NAME property of image 1 to "". Setting the DESCRIPTION property of image 1 to "". Setting the FLAGS property of image 1 to "". Setting the DISPLAYNAME property of image 1 to "". Setting the DISPLAYDESCRIPTION property of image 1 to "". Setting the NAME property of image 1 to "Windows 11 IoT Enterprise LTSC 2021". Setting the DESCRIPTION property of image 1 to "Windows 11 IoT Enterprise LTSC 2021". Setting the FLAGS property of image 1 to "IoTEnterpriseS". Setting the DISPLAYNAME property of image 1 to "Windows 11 IoT Enterprise LTSC 2021". Setting the DISPLAYDESCRIPTION property of image 1 to "Windows 11 IoT Enterprise LTSC 2021". Windows 11 Enterprise IoT Enterprise LTSC 2021 x64 es-ES has been successfully created Presione una tecla para continuar . . .
Weird. Bedi does not support multi language, only single language. If you want to implement other client language package, you must remove the en-US first. That way no more errors will occur when updating it.
I think you can adjust your script to other languages, just leaving enterprise G in the en-US language and that's it. Your script does its job, maybe it just needs more adjustments in upmod.cmd, nothing is perfect, we are always constantly improving.
You're right. I have updated my script. Code: :: Not support multi languages, but Bedi will use the client language package that you want if /i not %_lang% == %_clang% ( echo - Remove old client language package %DISM% /Logpath:%_log%\remlp.log %DismFmt% /Remove-Package /PackageName:Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~%_arc%~%_lang%~%_version% Call :_Teet 2 echo - Implement desired client language package ) %DISM% /Logpath:%_log%\lp.log %DismFmt% /add-package:"%ROOT%\%_lp%" || Call :_Warn "Failed add language pack."
not bad, I'll wait for this update. another thing I've noticed using bedi sxs files was that after creating and updating it now installs, but when it reaches 100% it shows an error saying "could not update boot configuration" maybe this has to do with BCD in the build I see that the "BCD-Template" is included but I don't understand the reason for the error.