@KleineZiege IoT Enterprise edition(s) only support OEM licenses/keys and setupcomplete.cmd is disabled (don't run) when OEM key is used (except for editions: EnterpriseS, EnterpriseSN, Enterprise, EnterpriseN) you can use unattend.xml answer file instead
I had also tried, no success Online everything goes even massgravel made fit for the 19044 $OEM$ dosent work
Why not install standard LTSC and use FirstRun.cmd to convert to IoT? Code: changepk.exe /ProductKey QPM6N-7J2WJ-P88HH-P3YRH-YY74H
@abbodi1406 Do you think it's possible to also add an option for updating the "Windows Malicious Software Removal Tool (KB890830)" and the "Microsoft Edge (Chromium)" with the W10UI tool?
I use IoT Ent. And I use setupcomlete.cmd settings (post-setup tab) when preparing an image in NTLite. And on the settings tab autounattend.xml there is a special option - OEMSetupComplele (screenshots here) which allows to allow setupcomlete.cmd execution for editions using OEM key . It works.
All updates are eventually update by a scheduled task. The point is to have an up-to-date Windows 10/11 without the need to connect it too the internet to get the rest of the updates.
How it's added to autounattend.xml? p.s. it's fairly easy to run setupcomlete.cmd via autounattend.xml even on OEM images Code: <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <Order>1</Order> <CommandLine>%windir%\Setup\Scripts\setupcomplete.cmd</CommandLine> <Description>setup complete</Description> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> </FirstLogonCommands> </component> </settings>
In my autounattend.xml it looks like this: Code: <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>%WINDIR%\Setup\Scripts\SetupComplete.cmd</Path> <WillReboot>Never</WillReboot> </RunSynchronousCommand> </RunSynchronous> </component> need to enable the "OEMSetupComlete" option at the top (there is a hint there if you hover your cursor): Spoiler
I'n not using NTLite adding the script to specialize phase mean that most of settings will not be implemented in the user account
Like what? What kind of settings exactly? I didn't get into those details. I gave the NTLite example here because I found it convenient for me.
@abbodi1406 Small question about uup-converter-wimlib. for create_virtual_editions.cmd Should it forbid converting 32bit LTSC 2021 to IoT LTSC 2021? I didn't get any info that there's 32bit release of IoT LTSC 2021.
Where did you see info that only x64 IoT is supported? the lack of x86 iso doesn't necessary mean that it's just a virtual SKU anyway
W10UI v10.14 Minor release - Check and exclude unsupported editions for 19041 WindowsExperienceFeaturePack - Fixed: ADK parameter is not enabled when using custom dism.exe
WIM <> ESD v8 - Updated wimlib Spoiler the older one can fail sometimes new one thanks to @mzakho for notifying