$OEM$ Folder no Longer Getting Copied

NickDawg41

New Member
Messages
2
Reaction score
0
Hi everyone,


I’ve created a fresh Windows 25H2 image. I’m running into an issue when using NTLite to copy a folder into C:\Windows\Setup\ before logon and then call a script after logon.


The problem: Windows doesn’t seem to be copying the "$OEM$" folder as expected.


Normally, I manually place the $OEM$ folder and handle everything myself, but after a week of repeated failures I thought I’d give NTLite a try. Unfortunately, I’m still stuck.


Any advice, tips, or solutions would be greatly appreciated!


Thanks in advance.
 
I would first confirm the $OEM$ folders are actually present under \sources on the ISO or USB drive. WinPE Setup has the responsibility of copying those files when starting the image extraction steps.

Is NTLite actually copying your files to the ISO distribution?
 
I would first confirm the $OEM$ folders are actually present under \sources on the ISO or USB drive. WinPE Setup has the responsibility of copying those files when starting the image extraction steps.

Is NTLite actually copying your files to the ISO distribution?
Yup! I confirmed that the OEM folder is present on the installation media and also shows up in the NTLite cache. At first, I suspected NTLite was the culprit, but after some testing I realized the problem came from using Schneegans’ autounattend generator.


When I switch back to my previous autounattend file that I wrote myself, everything works fine. With the generated file, something in the logic seems to interfere — my theory is that setup copies the files correctly, but one of the extracted scripts overwrites the directory afterward. I haven’t been able to pinpoint exactly where that happens.


Since this doesn’t appear to be an NTLite issue, I’ll go ahead and close this thread. I may try using the built‑in autounattend generator instead to see if it works better for my setup.


Thanks again for the responses and support — I really appreciate it!
 
Back
Top