I'm testing a Windows 11 image right now. 

I'm going to build a Windows 10 image right after this. I want to see If I still have the boot chkdsk issue in Windows 10 as described in the Manual. If this is the case then I think it would be something with the tuxera driver.

I am in the process of my testing and will post in a few.

At this point.....I think we can eliminate the SID Change as your issue.  Also since it is booting to Chckdsk, the issue is not boot order or it would not get to chckdsk and that would not fix it.

--

Maybe try some of the various tools to remove all the junk Windows Store Apps.  Apparently, a few are now required so removing all is not recommended but clearing out much of that junk can give you a cleaner and faster system.  

And I "WinPE" will be far less likely to give your NTFS issues and far less driver issues

While it's a change, it is far simpler LInuxPE, especially for WIndows Admins.  Far less driver issues.  Does not interfere with ongoing LInuxPE.  The learning curve is so small for most, any time spent getting it going will be less than spent on a single LInuxPE issue which will always be far more prevalent than WinPE since Drivers come out for Windows First,

Are you sure the tuxera driver is loaded? Have a look at the message-screen on  CTL+ALT+F4. There have to be a message like:  tfs_linux: tntfs taints kernel. Tuxera NTFS driver version...

Otherwise the tuxera driver is not loadedand your iso file is not modified by downloading the tuxera driver.

I don't see the tfs_linux: tntfs taints message anywhere.

I booted the USB key and got to the /# prompt type "modprobe tntfs" and I get the following error

"Fatal: Module tntfs not found in directory /lib/modules/5.14.21-150500.53-default"

I am not sure If I am running the correct command. I am trying to figure out if the TNTFS is running. I believe this is my main issue.

I did use the bootcd_tntfs.iso file that was created after uploading the tuxera and after bother servers indicated "Available" on the status page of the Tuxera High Performance NTFS Driver Integration Settings.

I did the modprobe tntfs from the USB boot imaging key after it finished loading into maintenance mode.

Additionally, I ran find / -name tntfs.*    and found nothing. This is on the USB boot key.

How can I definitively confirm what driver is running on the system?

On my USB key I do see these files:

1) \addfiles\x86\tntfs.ko    (File Size 620 KB dated 9/14/2022)

2) \addfiles\x86_64\tfs_linux.ko      (File Size 46 KB    dated 9/6/2023)

3) \addfiles\x86_64\tntfs.ko      (File Size 1,017 KB    dated 9/6/2023) 

Hi Joseph,

modify your settings.txt:

# Tuxera treiber laden
insmod /mnt/addfiles/x86_64/tfs_linux.ko
insmod /mnt/addfiles/x86_64/tntfs.ko

Working on adding these to the usb boot key. I noticed the USB drive is not mounted to /mnt, working on fixing that.

I manually mounted /dev/sda1 (USB drive) and insmod the ko drivers. I did a new capture with the drivers and restored. Then I got a blue screen on boot. going to try the following

efibootmgr -b 0000 -B
    efibootmgr -c  -L "Windows Boot Manager" -l "\EFI\Microsoft\Boot\BOOTMGFW.EFI" -d /dev/nvme0n1 -p 3
    efibootmgr -n 0000
    reboot -f

I did get a few errors when trying to put the insmod in the settings file.

I'm working on a few things, I'll post back in a bit.

I don't think the tuxera driver is loading properly. The ZENpreboot/imaging manual states adding files to the "Addfiles" directory will place the files in the root with the exception regarding RAM limitation. The files are not in the root "/" directory as stated in the manual.

When the Tuxera driver was added in the ZCM console it created the Bootcd_Tntfs.iso file, it automatically put the files in the Addfiles directory.

I tried manually adding the driver with the insmod commands, I don't think its working properly.

I'm in the process of getting the client to boot via PXE.

How do I make the USB work?

######## From the Manual #######

4)Copy any other files or drivers that you want included on the CD, DVD or bootable USB to the
addfiles directory in the temporary bootcd.iso image.

Any files or subdirectories that you add under the /addfiles directory are placed at the root
of the client when booting the CD, DVD or bootable USB.

IMPORTANT: When booting from the CD, DVD or bootable USB, the imaging engine is read into
RAM. Because the imaging engine uses some of the RAM that exists on the client device, the
combined size of any files that you add under the addfiles directory cannot exceed the
amount of remaining RAM.

Quick update:

After switching from the USB to PXE boot, I can now take and deploy a Windows 11 computer without issue.

Something is going on with the USB key, I think its related to "remaining RAM" the addfiles are not in the root / drive and as a result the tuxera driver is not loading properly.

PXE boot works perfectly. 

Thanks for the help.