What are you trying to say That I should start a new topic? I don't want to, I would like to keep all the PE enthousiasts in one topic For issues like this, for example: - Does anyone have any idea why the host OS (in which I run the PE builders) would have an impact on SETACL? On my test laptop, I have 3 multibooting 64-bit operating systems (freshly updated last week, all clean installs with the same post install tools) (1) LTSC2016: PhoenixPE builds fine (2) LTSC2021: SETACL is causing trouble: There is an error setting access on the created build target folder. (3) LTSC2024: Build is fine, no problems Why would SETACL behave differently in LTSC2021? This is where the error occurs in LTSC2021: Code: ShellExecute,Hide,%Tools%\%HostArch%\SetAcl.exe," -ot #$qfile#$q -on #$q%Path%#$q -actn ace -actn setprot -op #$qdacl:p_nc#$q -ace #$qn:S-1-1-0;p:full;s:y#$q" @abbodi1406 I know you're not into PE, but do you have any idea on the SETACL issue? Thanks...
I decided to rename this thread to "[DISCUSSION] WinPE Builders" Listed in the OP are Win10XPE, PhoenixPE and LiveSystem pro If anybody knows of other builders they recommend you can post them here and I'll include them
Not really, sorry maybe the target folder current permissions are owned by different user (from other booting system) or it occur on any new folder for the builder?
Thanks for the replies. I just received a tip from Homes32, asking me to test with the "WebClient" services switched to "on" instead of "off". And low and behold: This seems to do the trick!!!! So once again: Only in LTSC2021 it is necessary to have this service running, **not** in LTSC2021 or LTSC2024! @freddie-o Thanks for editing the OP. "LiveSystemPro" is another great PE builder, it was recently updated and it has a very friendly developer as well. It would be great if we heard from ChrisR as well, but I can fully understand that he might be too busy at the moment.
I'm quite pleased with my current custom W10PXE disk (1.3gb) but there's one change i'd like to make if it's possible: Can the program be configured to boot directly into an admin act rather then making it a 2-step process?
I haven't had the need to use the Administrator account. I tried it but this was years ago. The default account is sufficient for the tasks I perform -- formatting, repartitioning, installing Windows, accessing the internet... just the basics. I use Win10XPE boot wim as my default Windows Recovery wim so I can easily login without needing a thumb drive