Very much not needed. Not at all. Get aio script or the individual tsf part. If AV giving you problems - add exception or disable the AV. Run it and follow the prompts. Reboot for good measure. End of story.
I tested it more than 10 times with various versions of Windows. WMI has indeed been problematic lately since the release of build 25h2.
The title in cmd window is not as expected you can force not using wmic.exe: search for Code: set _wmic=1 replace all with Code: set _wmic=0 that will not help if WMI itself is not working
Hi, I request legends to make TSForge > ESU available for direct integration in install.wim index. It would be great for deployment. ( I am aware of $OEM$ method but am not comfortable with it ) Thanks.
$OEM$ folder copies stuff to C:\Windows\ . You can just mount the desired install.wim index and manually create the respective folders there, then just insert the proper setupcomplete.cmd in the Scripts folder. Unmount with /commit.