latitude 7490 and 3400


When deploying a new image windows 10 1903, after the first reboot I get a black screen with a cursor. If i power off and then reboot it continues to the OS and the rest of the K2000 Tasks. Not sure why it doe's this on certain models.

We use a uefi image, thought it could be a the bootloader, but I would have the problem with all my images...


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Channeler 1 year ago
Red Belt

It seems you are not alone:

Do you use a Sysprepped Image?

What partitions were captured?

I would suggest following this KB to see if Windows is complaining about something:


Do any of those devices have an HDD activity led, to see if it's doing something?

Also, Microsoft released this ISO a couple of weeks ago, named: "Windows 10 (business editions), version 1903 (updated Sept 2019)".
I know you're doing a System Image, but if you could deploy a Vanilla 1903 with this updated ISO with the KACE SDA, and see if the same thing happens... We could point to an incompatibility hardware issue (see DELL Forum Post), or maybe something inside the Image causes this.

A Scripted Install using the September's 1903 ISO, with a Vanilla install should help us to narrow this down.

  • Hi
    yes we use a sysprep image. We capture moth partitions c-d hidden part
    works on desktops. Seems like laptops are the issue - psaussey 1 year ago
    • Hi, it's odd to see a UEFI Image with C: and D:, unless D: was built on purpose to store data...

      Check if your D: drive, has a folder named EFI...

      (You could check this, via Browse Files in the System Image Details Page).

      And see if the SDA is up to date, you will need at least version 6.1.x to use 1903 images. - Channeler 1 year ago
      • when i capture the d is the hidden partition. Kace support said to capture both...
        » D:
        Add File
        Add Directory
        Documents and Settings
        Program Files
        Program Files (x86)

        » C:
        Add File
        Add Directory
        401.4 KBbootmgr
        1 BBOOTNXT
        8.0 KBBOOTSECT.BAK
        Recovery - psaussey 1 year ago
      • Your Image looks to be a Legacy Image, not UEFI....

        Perhaps, Windows Auto Repair is fixing this after your forced reboot?

        An UEFI Image will have only the letter C:\
        OR The letters C:\ and S:\, inside S:\ you should see an folder named EFI.

        If you have C: and D:, probably your Image comes from a Virtual machine, who was configure to use a BIOS Firmware, not an EFI Firmware.

        If you are using Hyper-V probably it comes from a Gen1 Hyper-V VM, instead of Gen2 (EFI).

        You have those partitioned arranged like that, probably because that Windows OS, was installed directly from a mounted .iso, instead of a KACE Scripted Install.

        I would suggest following this guide:

        https://www.itninja.com/blog/view/sda-imaging-best-practices-sda-6-x - Channeler 1 year ago
    • Do these have built in nics or dongle for the network? - SMal.tmcc 1 year ago
      • the 7490 as built in, tried dongle also, I uploaded latest audio,network and video drivers from the dell website - psaussey 1 year ago
      • that structure looks like a legacy boot layout - SMal.tmcc 1 year ago
      • structure works fine since we have a pre install task to re create the uefi partitions. and a mid level task to apply it. never had a problem so far. Not sure why these 2 models are a problem - psaussey 1 year ago
      • Thanks for ALL your help, will create a new VM firmware UEFI and then install the OS. I guess I was showed the wrong way :) - psaussey 1 year ago
      • doing what you are doing was the old quick fix to go from legacy to uefi and not have to start over. With the manufactures going to newer more advanced components they have plugged some of these shortcuts - SMal.tmcc 1 year ago
    • I agree with SMal.tcc, that's a Legacy Image...

      Probably because those newer models are using Intel Kaby Lake or newer CPUs?

      NOTE: This situation applies to any system from the Kaby lake 7th generation processor forward and is not limited to the systems that this article was originally based on.

      Those processors are not capable of booting from Internal legacy imaged Drives. - Channeler 1 year ago
      • ok I will follow the guide and do s cript install of the OS on my VM . or should I change the firmware to efi instead of bios? - psaussey 1 year ago
      • change the firmware to uefi and uefi boot the install dvd also for the golden image creation. - SMal.tmcc 1 year ago
      • Spin up an EFI VM, Sysprep it, and just capture the letter C:\.

        Then go here:

        And start reading from:
        "Setting up Image Deployment" - Channeler 1 year ago
Posted by: SMal.tmcc 1 year ago
Red Belt

Is your kbox up to version 7.0.357 for 1903 support? Did you download the new media manager, newest WSIM and compile and new boot and set that to default.

When I run into this it is has been 9 out of 10 time a bad driver and windows is trying to correct it at that point.  usually video, sound or network drivers are the problem.

The other thing I ran into was slow network negotiation for speed and the windows was trying to continue prior to that being settled. 

I set this policy in my master prior to sysprep to prevent that

Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon

  • latest versions and yes i used the 1903 to build the kbe's. tried uploading older, newer drivers, didnt work. Will try the audio drivers - psaussey 1 year ago

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