Problems with 24H2 autounattend install with config set

Background:
Up through 23H2, I have a tried and true process for 'imaging' PCs. I understand it is antiquated, but for our small shop, it works well.
Install media - USB created using the media creation toolkit
WSIM used to create autounattend.xml file.
AutoUnattend_Files directory in root of USB drive + OS install files

1. Boot from USB, setup auto starts, partitions drive, installs windows, autojoins to my domain in the OU I've designated, various other settings defined in autounattend.xml are set as expected.
2. Files located in AutoUnattend_Files are automatically copied to c:\windows\configsetroot without intervention while install is occurring.
3. during the oobe system pass, Firstlogoncommands processes several synchronous commands using installers and scripts located in c:\windows\configsetroot

Part 2 is failing with 24H2. If I look at setupact.log, I can absolutely see that my use configuration set=true is recognized. For this example, I changed the location of the files to root\$OEM$ upon reading that naming convention in other folders.

2025-02-07 18:02:09, Info MOUPG SetupManager: Copying user-provided private files from [D:\$OEM$] -> [C:\$Windows.~BT\Sources\$OEM$]…

further down, I see:

2025-02-07 18:04:11, Info MOUPG DataMigration: Not requesting data file migration.
2025-02-07 18:04:11, Info MOUPG DataMigration: Not requesting oobe.cmd file migration.
2025-02-07 18:04:11, Info MOUPG DataMigration: Not requesting setupcomplete.cmd file migration.
2025-02-07 18:04:11, Info MOUPG DataMigration: Queue preservation of custom scripts into Target OS...
2025-02-07 18:04:11, Info MOUPG DataMigration: Not requesting migration of ActionList.xml
2025-02-07 18:04:11, Info MOUPG DataMigration: Searching for private files...
2025-02-07 18:04:11, Info MOUPG DataMigration: Queue private files into Target OS...
2025-02-07 18:04:11, Warning MOUPG DataMigration: Not migrating file: [C:\$Windows.~BT\Sources\$OEM$\Acrobat\ABCPY.INI]
and then it proceeds to list each file with the same warning and "not migrating file"

Other than this, everything works fine with the install. I modified the xml slightly based on things I've read such as how the disk partitioning steps work in 24H2, but it is largely the same. I suppose I could try creating a command in an earlier pass to copy those files, but I'm thinking there must be a relatively simple fix.

Any thoughts are welcome.

Try this registry change, which reverts 24H2's boot.wim back to the legacy Setup client.

DISM /Mount-Wim /wimfile:H:\Boot.wim-N\boot.wim /index:1 /mountdir:M:\Mount
reg load HKLM\TEMP C:\Mount\Windows\System32\config\SYSTEM
reg add HKLM\TEMP\Setup /v "CmdLine" /t REG_SZ /d "X:\\sources\\setup.exe" /f
reg unload HKLM\TEMP
DISM /Unmount-Wim /mountdir:M:\Mount /commit

This dummy forgot to read the code it needs to changed from index:1 to index: 2