FilesU folder is not being created (Post-Setup)

[BKPB]

The FilesU folder is not created. $OEM$\$$\Setup\FilesU.

Earlier, when I used the PostSetup item, after saving install.wim, a FilesU folder was created next to it, which contained files to use when logging in for the first time. Now I decided to make only changes after installation, but after saving Install.wim image the FilesU folder is not created. What am I doing wrong ? Or is such a folder created only when editing the Windows 11 image ?

 

[garlin]

Post-Setup files don't belong to the install.wim, they're added to the ISO folder.

The only part that goes inside the install image is a reg key applied to run (Before logon) tasks thru SetupComplete.cmd, and a RunOnce task to schedule (After logon) commands.

I've noticed NTLite tries to track Post-Setup items it applied once before, so it doesn't repeat itself. This detection sometimes is faulty, and doesn't follow through by adding new changes. In those cases, I give up and just delete the items and add them back again.

 

[BKPB]

Since I use an online translator, I probably can't convey the meaning of the question. The question is not about install.wim, but about the fact that after making changes to it using NTLite and using the "After installation" option, a FilesU folder was automatically created in which files were placed for use after Windows boot. This folder should have been placed in $OEM$. But now this folder is not being created and I don't understand why. I've attached a screenshot where you can see what actions I'm doing.

 

[BKPB]

If the FilesU folder is not created, the files from the "After installation" item are not applied accordingly.

 

[garlin]

Yes. That's the bug, sometimes it doesn't apply them.

 

[BKPB]

When you say that sometimes they don't apply, are you talking about files? And I ask why the FilesU folder is not created after saving the image?

 

[BKPB]

This is your answer in another post.

When Post-Setup commands or files are added, NTLite divides them into two categories:

(Before logon) commands are executed by the SetupComplete.cmd wrapper script, right after OOBE is completed.
1. Files are staged in the folder $OEM$\$$\Setup\Files
2. Copied to \Windows\Setup\Files during install.
3. Removed after SetupComplete is finished.

(After logon) commands are executed by a RunOnceEx scheduled task, right after your first desktop logon.
1. Files are staged in the folder $OEM$\$$\Setup\FilesU
2. Copied to \Windows\Setup\FilesU during install.
3. Removed after RunOnceEx task is finished.

https://www.ntlite.com/community/index.php?threads/parameter-after-installation.4612/

 

[garlin]

If you've been following this forum since the March 2024 redesign, there are still user reports that NTLite may be ignoring some changes to existing Post-Setup items. NTLite will successfully process the image, but the ISO is missing the expected files.

It's hard to track down, because it works for most users but obviously not for everyone. If Post-Setup was broken for everyone, then the problem would be easy to find. This bug has been reported several times, but finding a test case which can be repeated appears to be hard.

 

[BKPB]

RU
Господа, напишите у кого такая же проблема. Десять дней назад я редактировал образ и папка FilesU автоматически создавалась рядом с сохранённым образом, а сейчас этого не происходит. Уже совершил 7 попыток. Может быть это произошло из за того, что я обновил предпоследнюю версию программы до последней ?
EN
Gentlemen, write down who has the same problem. Ten days ago, I edited the image and the FilesU folder was automatically created next to the saved image, but now this does not happen. I have already made 7 attempts. Maybe it happened because I updated the penultimate version of the program to the latest one?

 

[BKPB]

RU
Уважаемый Garlin, Вы в своём сообщении https://www.ntlite.com/community/in...ure-to-my-custom-picture-in-install-wim.4637/ пишите, что Вам удалось заменить изображение учётной записи используя параметр Post-Setup.
Значит у Вас создаётся папка FilesU рядом с install.wim когда Вы сохраняете отредактированный программой NTLite образ. Иначе Вам не удалось бы проверить предложенный Вами способ замены картинки учётной записи. Ответьте, да или нет. Если да, то какую версию программы Вы используете ?
EN
Dear Garin, You are in your message https://www.ntlite.com/community/in...ure-to-my-custom-picture-in-install-wim.4637/ write that you managed to replace the account image using the Post-Setup parameter.
This means that you create a FilesU folder next to install.wim when you save an image edited by the NTLite program. Otherwise, you would not have been able to verify the proposed method of replacing the account image. Answer yes or no. If so, which version of the program are you using?

 

[BKPB]

RU
Откатился до версии 2023.11.9515 (64-bit).
Использовал Post-Setup parameter, произошло следующее, папка \$OEM$\$$\Setup\ создалась, но в ней вместо папки FilesU создалась папка \$OEM$\$$\Setup\Files, насколько я понимаю она должна появляться если используется параметр во время установки. И ещё я заметил, что когда я добавлял файлы в последней версии, то им автоматически присваивались параметры Run и Copy, в версии 2023.11.9515 этого не происходит.
EN
Rolled back to version 2023.11.9515 (64-bit).
I used the Post-Setup parameter, the following happened, the folder \$OEM$\$$\Setup\ was created, but instead of the FilesU folder, the folder \$OEM$\$$\Setup\Files was created, as far as I understand it should appear if the parameter is used during installation. And I also noticed that when I added files in the latest version, they were automatically assigned the Run and Copy parameters, this does not happen in version 2023.11.9515.