25H2 boot.wim new wizard setup, same old bug for $OEM$ folder.

Mamukata said:

I notice that the new boot.wim not totall solved the $OEM$ folder bug.....
With 25H2 now it right copy only the data inside the $$ but not if a folder is empy (it isn't create) and not copy nothing inside the $1 folder.
Moreover, it continue to create the Windows.old folder.

With 25H2 boot.wim forced with old setup, all work right.

Click to expand...

pseymour said:

It copies the files in $1 just fine in my testing. It doesn't create an empty folder in the Windows folder, but you can easily do that with SetupComplete.cmd or running a SynchronousCommand in the OOBE phase via an unattend.

Add a Custom Script to Windows Setup

Add a Custom Script to Windows Setup

learn.microsoft.com

Click to expand...

Deploy push-button reset features with auto-apply folders

Push-button reset features are included with Windows 10 for desktop editions (Home, Pro, Enterprise, and Education), though you'll need to perform additional steps to deploy PCs with the following customizations. (deploy-pbr-features-using-auto-apply)

learn.microsoft.com

pseymour said:

Directly in $1, I have two folders. One has files in it, the other has files and folders.

Spoiler

Code:

> tree /f "D:\Windows ISO Build\$OEM$\$1"

D:\WINDOWS ISO BUILD\$OEM$\$1
├───PSTools
│       Eula.txt
│       PsExec.exe
│       PsExec64.exe
|       etc., etc.
│
└───scripts
    │   Create-Local-Users.ps1
    │   Create-Test-Users.ps1
    │   Remove-Reparse-Points.ps1
    │   Set-Drive-Security.ps1
    │
    └───winget
            Install-Applications.ps1

Click to expand...

pseymour said:

I wouldn't be surprised if that doesn't work. There may be something special about the folder name Recovery, since that comes into play if you don't have a recovery partition.

Click to expand...