Is restoremask.xml on your image set to disable the Restore/Changing of the SID?

https://www.novell.com/documentation/zenworks-23.4/zen_cm_preboot_imaging/data/bg4iu9s.html

If not, the imaging restore process will try and alter the devices SID which is quite bad on WIndows 7, Really Bad on WIndows 10, and Really Really Bad on WIndows 11.

The only place left that touches the SID is the Linux Imaging Boot Environment.  ZENworks WInPE has never done it, since that came along after touching SID became a real no-no and all ZENworks Agent code has been stripped of SID Touching.

--

Avoiding SID Change is likely sufficient.....

If that does not help....I recommend creating a fresh image using the latest WIndows 11 Media but w/o any network connection to help ensure no updates are applied to the PC during the Image Creation as that can really mess with restored images as the identity updates itself as part of SYSPREP.  It's generally the store apps that cause the most issues.  If there are specific Windows Updates you want to apply such as the June Cumulative Update....that should be fine but I would download them and apply via a USB stick versus using Windows Update.

Created a new BASE Windows 11 23 H2 image

Process:

1) install Windows 11 EDU

2) Wipe all partitions, then let windows installer create partitions

3) unplugged ethernet cable

4) No Microsoft updates installed, No hardware drives installed

5) Ran cmd (administrator elevated) to disable hibernate powercfg /h off

6) Power off computer, take image

7) Restore image on same hardware, image process freezes at 7 seconds into the restore process on the following directory:

c:\Program Files\WindowsApps\Microsoft.VP9VideoExtentions_1.0.50901.0_x64__8wekyb3d8bbwee\x86

"Yes, I forgot to mention that. Restoremask.xml is in the root of C: and when I finish retore an image I see the message "SIDchanger is disabled"

With that method and the Restore Mask and message.....you SHOULD be good in regards to your issue with needing"CHKDSK".  The Sid Changing breaks the security settings on a number of files all across the computer since the permissions are set to the PCs SID.  Check disk goes through and fixes the invalid ones with the current SID.

--

In regards to the issue around VP9VideoExentions....I don't have any Good Suggestions other than the obvious LAME one....

https://lazyadmin.nl/it/uninstall-microsoft-store-and-default-apps/

Remove the VP9 Windows Store Apps from ALL USERS prior to taking the image.  

I want to say something around making sure you are using the TUXERIA Driver....but that would be a total mess...since enabling it would be a major project.  You could test using WInPE on a one off basis.  There could be something in the file system with that app that the LInux NTFS Drivers are not liking.  But getting that fixed would be a Servicec Request and Dev work that will take a while.

I know folks hate when I say it....But starting on WinPE will save you heart ache in the long run.   Far less Hardware Driver issues and it gives far more imaging options than just Disk Images.  How things work are basically the same with the same imaging commands....just done from a WIndows Boot OS instead of LInux.  When Setting up WinPE you can keep your current setup in place and just and a Boot Menu option to boot WinPE if you select it so you can test and play with it w/o impacting your current designs.

Morning Craig,

I removed the VP9 ... directory. It was not pretty. But the image was able to restore without freezing during the restore process. However the boot issue still remains.

The TUXERIA driver,. I tried both with and without the TUXERIA driver and I did not see a difference. Same issue, stuck at boot.

I am using a USBkey to boot the computer. I have not switched over to PXE. This is in the plan. I am using the bootcd_tntfs.iso and used RUFUS to create the USB key.

After I restore the image, system does not boot. I boot the USB WIn 11 Iso to recovery mode. go to command prompt and do a chkdsk /f. Results are below. After this, system boots.

Does not look like a SID Change issue to me.  I would expect to see errors where it was processing Security Descriptors.  

You could try running CHECKDSK before creating the image...That might help....If something was sort of flakey...before the image was created....it will just not be made correctly...That was suggested above and could help....

Does not look like a SID Change issue to me.  I would expect to see errors where it was processing Security Descriptors.  

You could try running CHECKDSK before creating the image...That might help....If something was sort of flakey...before the image was created....it will just not be made correctly...That was suggested above and could help....