All the XML and JSON commands have disappeared from https://github.com/PhoenixPE/PhoenixPE/wiki/PhoenixAPI

https://github.com/pebakery/pebakery-docs/blob/master/Commands/Branch/Loop.md, https://github.com/pebakery/pebakery-docs/blob/master/Commands/Branch/Run.md, and https://github.com/pebakery ...

?

Yeah, I got the folder wrong, but not the rest. The 1.00 manual comes from the master branch. I clicked on the "2 branches" link and selected the Master. There is no link to 1.0.1 . And those files are indeed missing, and a few others.

The manual at https://github.com/pebakery/pebakery-do ... tag/v1.0.0 is significantly incomplete. For example the Control folder is missing Break, Continue, ForEach, ForRange, and While.

Jans wrote: Tue 09 Jun, 2026 3:03 pm Emeditor is simply present in both drive X and drive Y as a custom portable app.
Win10XPE uses drive Y, PhoenixPE (from RAM) uses drive X

Try the update in message 1.

You really don't want to answer my questions, do you.

I might try something which would satisfy you.

When I boot in VirtualBox it sees both X drive and Y drive. That's standard. How do you get programs from Win10XPE onto PhoenixPE's drives?
Consider changing one of the directory names?

So it searches all X:\Program Files\ subfolders and all Y:\programs\ subfolders to find Emeditor.exe?
Why not simply let the user specify the path to the .exe in the Directory column?

Originally it did. Slow. Now it searches X:\Program Files\<folder>, Y:\programs\<folder>, and X:\Windows\<folder ...

I think I won't change to full path. Which doesn't exist before booting and the local files may not exist when building if the other script hasn't been processed yet. So picking it isn't robust and manual entry adds complexity.

How can you have Win10XPE files in a PhoenixPE build?

I'll think about it.

Thats' common, but not in this case.

Download both 886 and x64 English versions from the FileForum link at https://www.irfanview.com/main_download_engl.htm. You want iview475_x64_setup.exe and iview475_setup.exe.
In PhoenixPE/IrFanview click the magic wand at top right and select "Edit Script Properties".
On the General tab change 4 ...

Ah, I wasn't clear enough. Directory, not path. Use "Emeditor", not "X:\EmedItor". I've updated the original post with a version with more detailed logging and slightly improved interface that would have enabled you to detect that.

Finding the script to detect the full path at build time would be ...

The full AutoIT including an optional debugger. Useful for debugging scripts in the booted build. Components\Additional Files is a good way of imprting scripts into the build.

Whoops, found a bug in using full SciTE

25H2 is old?

Just for grins I build with 26H1. PENetwork didn't work but SetUserFTA did.

The free version of SetUserFTA is working in PhoenixPE.

I think importing associations won't work.
I won’t go into technical details (and I will never publish them publicly), but there’s something quite remarkable about the new hash: it now includes a machine ID. This means file type associations ...

The author of SetUserFTA published ProgIDTool https://kolbi.cz/blog/2024/06/05/progidtool-display-delete-export-and-register-file-type-progids/?sfw=pass1780071350 but it doesn't work in Windows 11 (https://kolbi.cz/blog/2025/07/15/ucpd-sys-userchoice-protection-driver-part-2/). In a Windows 10 VM ...

Nice, but I have no idea how to do it programatically.

RunSetUserFTA.au3 resets that counter to avoid the popup which requires intreraction..

@JonF, thanks for the script.

I'm not quite sure what to insert for ProgID.

see as example .txt:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.txt\UserChoice

The ProgID for .txt is AppX4ztfk9wxr86nxmzzq47px0nh0e58b8fw
How do you find out the right ProgId?

I ...

23H2, 24H2, 25H2.

@JonF, might be you have used a build before February 2024 why it works on Win 10:

"2024 Update: Since the February 2024 Cumulative Update, Windows has included a driver service named UCPD.sys (User Choice Protection Driver) stops users from writing to the “UserChoice ...