Couple of anomalies on my first build

[TanyaC]

I've made my first build with ntLite after several attempts I've got an image that installs. There are a couple of strange things though, I'm not sure how to fix.
The builds are experimental as I try to learn how ntLite works. Some of the stuff I've disabled/removed/tweaked is not what I would do for a production system.

1. In the OOBE I see only the Account page (which is what I want). But when I click Next after entering "Who will use this computer" it does not show the "Enter a memorable password page". It seems to be working though because if I click next again the install continues.

2. After install completes, when I do dism /online /cleanup-image /startcomponentcleanup /resetbase it crashes with error 0x8007002 ERROR_FILE_NOT_FOUND.
I looked at cbs.log and dism.log but I couldn't really tell from that what I'd removed that is crashing the clean up.

3. What component/feature/tweak removes the Security and Maintenance page from control panel?

4. Settings > System > About says there is no storage installed in my system. I removed Enhanced storage and Storage Tiers. I have only NVMe SSDs and a Seagate Spinner in the system, and an external NVMe SSD from which I do installs.

5. A couple of components got removed that I didn't intend to remove (VBS, OptionalFeatures), I guess I removed the dependent features. I'll go back and see if I can figure out what trigged the removal.

Windows 10 21H2 LTSC IoT 19044.7725.

Attached are the log files for this sessions.

 

[tistou77]

4. These two components must be kept.

<c>storagespaces 'Storage Spaces'</c>
<c>driver_spaceport.inf</c>

 

[TanyaC]

2. After install completes, when I do dism /online /cleanup-image /startcomponentcleanup /resetbase it crashes with error 0x8007002 ERROR_FILE_NOT_FOUND.

This is caused by the \windows\servicing\sessions folder being empty after the fresh install.
I copied session.xml and some other files from the same folder on another WIndows 10 install and DISM then works fine, removing all files exception the session.xml file.

Apparently these files are created by the WIndows Module Installer. So for now, I've added some files to the folder in the image so it doesn't crash. Probably not the right solution, but for now a workaround at least.