Software Deployment Question

Problems using K2000 imaging Windows 10v1803

05/15/2018 4572 views
Just got a new installation disk of Windows 10 x64 Enterprise v1803, and was going to get started creating a sysprepped image of it to start pushing it out.

I installed it one of my test machines with no problems.  Ran Sysprep_Executor with no problems (other than having to manually stop the new Windows Defender security software), and sysprep then shut the computer down.  I use a USB key to boot the computers into the KBE.  When I booted into the KBE, I double-checked the partitions before imaging, to make sure they were using the correct drive letters (Created the image on a BIOS machine, so there was S: for System Partition and C for Boot Partition).  The Imaging process gave no errors, but something weird happened. 

I tried deploying the image back to the machine.  It automatically uses diskpart to create the S and C partitions.  When it tries to apply the image, it takes less than 30 seconds.  The image deployment job then gives the dreaded "setup_post_install_tasks.vbs" error.

At this point, I know something is wrong.  I open a command prompt, and see that the two partitions have been created, but there is almost nothing on the C drive!  There is a KACE folder, and then a file called kcleanup.exe

I went through the exact same imaging process with Windows 10 x64 Enterprise v1709 with no problem.  Something has changed between 1709 and 1803 that prevents the imaging process from working.

Here is what I'm using

SDA Model K2100S, Version: 5.1.84
Sysprep Creator

What can I do to get a working WIM file using Sysprep Creator ?


6 Comments   [ + ] Show comments


  • You are supposed to create the initial installation with a K2000 scripted install so that only 1 partition gets created.
    • I believe UEFI boot builds two partitions.
  • I believe I have the same problem that eahelms has. The image process takes about 44 seconds till fail and that is after it supposedly applies the image which cant happen that fast. The fail error is the same too at the "setup_post_install_tasks.vbs" error. The image file is 3.96GB in size. The image capture time seems right for the file size so not sure where the problem occurs. This is my first UEFI image process attempt. Been imaging bios boot for years with Kace.
  • I've created a scripted unattended installation task of Windows 10v1803 x64 Enterprise that I installed on a UEFI machine. Here is the diskpart task I use to create all the partitions needed:

    Select disk 0
    Convert gpt
    Create partition efi size=100
    Format quick fs=FAT32 label="System"
    Assign letter=s
    Create partition msr size=16
    Create partition primary
    Format quick fs=NTFS label="Windows"
    Assign letter=c

    I then have a midinstall task that repairs the BCD

    bcdboot C:\windows
    bcdedit /set {bootmgr} device partition=s:
    bcdedit /set {memdiag} device partition=s:
    bcdedit /set {default} device partition=c:
    bcdedit /set {default} osdevice partition=c:
    Bcdedit /set {FWbootmgr} displayorder {Bootmgr} /addfirst

    The scripted install creates a local user account that is a member of the local Administrators group. I login, and I install the May MS updates on the OS. and then restart.

    At this point, I run sysprep_executor, which I created using sysprep_creator. When it's done, it shuts the computer down. I then boot to the KBE (open a command prompt, to make sure the S drive is mapped to the system partition, and the C drive is mapped to the boot partition) and then capture the image. I tell it to capture both the S drive and C drive as a WIM file.
    • Hi, I'm playing around with our KACE SDA (v6.0.425) and Windows 10/1803, i use the exact same scheme for partitions and drive letters, but i just have success with the desktop systems, the laptop systems always fail with task 82 "apply image". Looking into the logs at \\k2000\petemp just reveals a message like:
      2018-09-16 21:53:48-0800 [info] ...Deleting image dir: C:\K2_2018-09-16_21-33-07\
      2018-09-16 21:53:49-0800 [info] Cannot open WIM file [S:\K2_2018-09-16_21-40-50\S.wim]: The data is invalid.
      Any ideas?
      • I had a guy from Quest Tech Support on the phone and he gave me a hint to use K-IMAGE instead of WIM to capture the image of Windows , which was installed in UEFI-Mode. He also told me, that capturing Windows 1803 as WIM isn't supported by the KACE yet.
        I gave it a try and after some playing around i succeeded with capturing and deploying the K-Image on Laptops and Desktops. The trick was, as mentioned, to use K-Image, AND to capture JUST the OS partition as Drive C: and the EFI-partition as Drive S:.

        In previous capture runs i also captured the "Windows Recovery"-Partition (499MB), i gave it the Letter T:, this never worked well. The Capturing was ok, but deploying partitions C:, S: and T: always failed, although i triple-checked the drive Letter assignments in the scripts and before capturing.

    Yesterday, I finally played with 1803 to update my base images. I initially ran into this exact issue... I could deploy previously created images just fine, but 1803 just would...not...work.

    Creating a brand new KBE with the newest Windows 10 APK fixed things for us.

  • Will try that tomorrow, jguthrie, and see if that works.
  • Worked like a charm - thanks!

All Answers

"(Created the image on a BIOS machine, so there was S: for System Partition and C for Boot Partition)."

Are you sure this is not UEFI?

C is the NTFS Big OS parition
S is the small FAT32 parition

What tasks are you using (Pre and Mid level)

What version of Windows 10 1803?

Sounds like the image wasn't properly captured in the first place.
Answered 05/16/2018 by: Channeler
Red Belt

Created the following pre-install task for UEFI
Select disk  0
Convert gpt
Create partition efi size=200
Assign letter=s
Format quick fs=FAT32
Create partition msr size=128
Create partition primary
Assign letter=c
Format quick fs=NTFS

There is no mid-install task needed.

Imported the Windows 10 (1803) disk into SDA as new source media using Media Manager. Created scripted install using the new source media. Created UEFI boot USB. Later Created the automated deployment. Works great!
Answered 05/18/2018 by: egholm52
Senior White Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ