ZCM Imaging Windows 11 - no boot after restore

Hello,

We are trying to build a Windows 11 image using ZCM native Linux engine. We can create the image, restore the image but upon the first boot of the Windows 11 operation system the spinning circle stuck at the Manufacture "Lenovo" screen.

I have narrowed the issue down to a chkdsk issue. After the computer image is restored, computer does not boot, I can boot the computer with the Installation ISO key, go into recovery mode, go to command prompt, change drive to c: and run a chkdsk /f on c:. The process completes and I reboot. Windows 11 boots normal.

I made a Windows 10 Image, captured and restored the image and upon first boot of Windows 10 goes into a chkdsk, repairs itself and then boots.

Whats odd is that in both Windows 10 and Windows 11 ZCM image restores it appears there is a need for a chkdsk /f upon first boot in either OS. Windows 10 does a automatic checkdsk on first boot but Windows 11 just hangs. I checked the regkey to see if the autocheck disk was enabled for windows 11 OS and it is. I did a CHKDSK /f on both installs prior to capturing the image and ran a chkntfs to confirm the drive was not dirty.

ZENworks environment

##########################

ZENworks Configuration Management Version: 23.4.0.0
ZENworks Asset Management Version: 23.4.0.88
ZENworks Patch Management Version: 23.4.0.88
ZENworks EndPoint Security Management Version: 23.4.0.88
ZENworks Full Disk Encryption Version: 23.4.0.88
ZENworks Agent Version: 23.4.0.88
ZENworks Updater Service Last Contact Time: 8:55 AM
ZENworks Updater Service Version: 23.4.0.88

Windows Versions 

##########################

Windows 10 Education Version 22H2.19 64 bit

Windows 11 Education Version 23H2 Build (22631.3593) 64 bit

Windows 10/11 base Image creation process

##########################

1) Install Windows 11 from Iso

2) install Windows patches

3) Deploat OS with Windows10DebloaterGUI.ps1

4) Disable Hibernate with Powercfg /h off

5) Capture Image

6) Deploy image on same exact hardware (changed nothing) then we get boot issue in Windows 11.

Few things I have tried.

I have tried sysprep /oobe and non sysprep same results.

I have switched to using the Texera driver. This made no difference.

I have tried different hardware, same results. Windows 11 first boot stuck on Manufacture screen. Chkdsk /f in recovery mode fixes the issue.

I am wondering if the capture or restore process is causing the system partition to be in a dirty state.

Anyone experience this? does anyone know of a workaround?

Thanks,

  • 0 in reply to 

    I booted the USB Tuxera key and the ZENworks Imaging Engine Version is 23.4.0.

    Is this the correct / updated version? Thanks.

  • 0   in reply to 

    There is not much in the way of Imaging Fixes for 23.4.  There is not any update for the LInuxPE which would also involve an updated Tuxera Driver.  The issues you have shown are not known issues per se.

    --

    #1 - The initial chckdsk screenshot indicated it was NOT related to SID, since the errors were not related to security identifiers, despite the symptom being similar.

    #2 - You may want to try running chckdsk as a last step before taking the image.  It may help clear up any anomalies.

    #3 - There are come various "Declutter" scripts for WIn11 to get rid of many useless Windows Apps.  Most of your NTFS errors seem to be around store apps.

    #4 - The effort to upload and learn how to create and restore ZMG Imagines from a WinPE vs LinuxPE environment will be well worth your time.  There is ALWAYS going to be a lag for drivers or other changes in LInux vs WinPE.  Adding Drivers is quick and simple.  Introducing the use of WInPE does not impact the ability to do LInuxPE at the same time.  The only advantage for LinuxPE is inertia.  WinPE will save time and effort in the long run due to improved hardware/software compatibility and enhanced functionality that will never exist in LinuxPE.  I can't say it will help...but if you hare having NTFS file system issues in LinuxPE, they may not exist in WinPE since it is a Native MS NTFS Driver.

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • 0 in reply to 

    Adeckert2, What ZCM version are you on?

    I tried different hardware "HP" and had the same issue with Win11 32H2. No boot until running chkdsk on c: drive in recovery mode.

  • 0   in reply to 

    Did you run CHCKDSK before shutdown?

    You can also set CHCKDSK to run on 1st boot....if you issue command right before reboot.

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • 0 in reply to 

    I use 23.4. But it has always worked, no matter what ZCM Version i used. But you have always as last option to run chkdsk before you take the image. Also never modify the image file with the imaging explorer like adding a file. This will break the "Tuxera option".

  • 0 in reply to   

    Good Morning Craig,

    Yes I tested several different chkdsk commands.

    1) Ran Chkdsk /f, let it run chkdsk run on next reboot, shutdown gracefully, take image

    2) Ran Chkdsk /f /b /r, let it run chkdsk run on next reboot, shutdown gracefully, take image

    3) Ran Chkdsk /f /b /r, shutdown, take image. (deploy image on the same hardware the image was built on), I was expecting the computer to boot into a forced chkdsk and it was stuck at the same Manufacture logo. 

    In all the scenarios, the result was the same, stuck at manufacture logo (Lenovo) and had to boot into recovery mode.

  • 0 in reply to 

    Please change the boot order after pulling down the image to windows boot manager or to the hard disk, depending on the hardware model of the endpoint.

  • 0 in reply to 

    Thanks for the advice on the Image explorer.

    The last several images I made I did not use Image Explorer and still had the same issue with booting.

    I'm going to Out Line my Windows 11 install process again:

    1) Download Windows 11 (SW_DVD9_Win_Pro_11_23H2.5_64BIT_English_Pro_Ent_EDU_N_MLF_X23-73316)

    2) Use Rufus to create the ISO on a Thumb drive

    3) Boot hardware off Installation Media

    4) Chose Windows 11 Education version

    5) Chose custom Install, delete all partitions until I have Unallocated space, let Windows install setup the partitions

    6) Windows installs files, reboots

    7) Unplug the ethernet cable (Prevent Windows Updates)

    8) Copy the restoremask.xml file to c:\

    9) ** Stopped this while working out imaging bug - install Windows patches

    10) ** Stopped this while working out imaging bug - Deploat OS with Windows10DebloaterGUI.ps1

    11) Disable Hibernate with Powercfg /h off

    12) Take Image

    13) Deploy image on same hardware (changed nothing)

    14) Boot Issue

    A few notes:

    When I use the latest ISO for Windows 11, I can take an image with no problem. deploying the image ZEN imaging engine freezes on c:\windows\windowsapp\

    Is it the version of Windows I am using?

    Is it the USB key booting in Zenwork Imaging? (I used Bootcd_tntfs.iso)

    Is it my Windows image creation process?

    I'm stumped at this point. I have tried 3 different versions of Windows 11 installs and got the same results with booting. When I use the first release of Windows 11 Iso version SW_DVD9_Win_Pro_11_21H2_64BIT_English_Pro_Ent_EDU_N_MLF_-3_X22-89962.ISO I can take the image and deploy the image without it locking on the C:\program files\windowsapps\vp9... directory.

    I will be opening a case sometime today with support.

  • 0 in reply to 

    Please change the boot order after pulling down the image to windows boot manager or to the hard disk, depending on the hardware model of the endpoint.

    Have you triied to rewrite the master boot record on the disk?

    Remove the last partition (Recovery) from the imagefile with imageexplorer and restore the modified image file.

  • 0 in reply to 

    I think I found something..

    My ZCM 23.4 is installed on a Windows Server 2019. I found this on page372 of the Preboot_image manual:

    Check Disk might run on a device with Windows 2019
    Explanation: When you take and restore an image of a device with Windows 2019 using a
    Legacy NTFS Driver. After restoring the image, Check Disk might run before
    booting the operating system. However, the device boots to the operating
    system after performing the check disk.
    Action: Take and restore image of a device using Tuxera driver.

    How do I confirm the Tuxera Driver is working?